Subject: Re: DRI in XF86?
To: Rasputin <firstname.lastname@example.org>
From: Eric Anholt <email@example.com>
Date: 10/29/2002 19:33:07
On Tue, 2002-10-29 at 08:10, Rasputin wrote:
> * Lars Nordlund <firstname.lastname@example.org> [1042 10:42]:
> > On Sun, Oct 27, 2002 at 03:24:44AM -0600, Peter Seebach wrote:
> > > It appears that XF86 has some hooks for hardware rendering support,
> > > but they're turned off by default in the NetBSD build. Is there
> > > something horribly broken about the DRI support?
> > We need a DRM kernel module. I am not sure if this is layered in such a
> > way that we can use it together with the pieces written for each and
> > every graphics chip supported by Linux DRI. Basically, each graphics
> > chip we want to support needs its own kernel module. According to the
> > documents I have read so far this module is then loaded by the X server.
> > Or something.. I think FreeBSD loaded this module at boot time though.
> It used to, although I've had XF86 loading it on demand when X started
> before now.
> On FreeBSD, I hasten to add - this would be *really* useful, but I've
> no idea how KLDs work, unfortunately.
X loads it automatically if the module is available in a directory in
your kern.module_path sysctl. This is the case for FreeBSD-current,
which has the 4.2 DRM distributed with the kernel. On -stable the DRM
is distributed through ports (drm-kmod), so they aren't in the sysctl
and the startup script has to load them all.
Eric Anholt <email@example.com>