Re: legacy DRM UMS vs. "options DRM_LEGACY"

["John D. Baker" <jdbaker%consolidated.net@localhost>]

On Sun, 4 Sep 2022, Robert Swindells wrote:

> Your RACKMOUNT config builds fine for me (apart from plip but I will fix
> that), are you sure that the link errors you are seeing are from the
> kernel and not from a module?

I'm not sure what you mean.  Any modules were built a long time ago
(with the "distribution" target).  My command line is:

./build.sh -U -m i386 -T /r0/build/current/tools/amd64 -O /r0/build/current/obj/i386 -D /r0/build/current/DEST/i386 -R /r0/build/current/REL -X ../xsrc -x -u -j 5 -V MAKECONF=/x/current/src/../mk.conf kernel.gdb=RACKMOUNT releasekernel=RACKMOUNT

When I comment-out the "mach64drm" and "radeondrm" lines, it builds.
When I uncomment either one or both, it fails.

I think there was something stale lying around.  I deleted all "drm*"
and "agp*" files from the ".../compile/RACKMOUNT" directory and it built
with the old DRM drivers enabled.

Thanks for the pointers.

-- 
|/"\ John D. Baker, KN5UKS               NetBSD     Darwin/MacOS X
|\ / jdbaker[snail]consolidated[flyspeck]net  OpenBSD            FreeBSD
| X  No HTML/proprietary data in email.   BSD just sits there and works!
|/ \ GPGkeyID:  D703 4A7E 479F 63F8 D3F4  BD99 9572 8F23 E4AD 1645