On Mon, 2003-09-22 at 22:25, Jon Smirl wrote:

quoted

quoted

2) Get 3D driver name. Return the name of the DRM driver that is associated
with this fb device. For example aty128fb would return r128, radeonfb would
return radeon. Empty string if there is none. There are eight DRM drivers

and

quoted

15 fb ones.

I think this should be done using sysfs, too. I.e. symbolic links between the
fbdev and drm drivers in /sys.

Initially the fb device will need to provide strings for the name of the 3D
driver. A user app is going to read these strings and load the DRM driver.

So the app will map from 3D driver to DRM?

After the DRM driver is loaded it can make links.

The framebuffer device could do it just as well, the link target doesn't
have to exist.

Another solution would be for the fb driver to reference a symbol in the
appropriate DRM driver. This would make modprobe load them both.

This doesn't work because the framebuffer device is needed for console
on boot and hence built into the kernel. :)


-- 
Earthling Michel Dänzer   \  Debian (powerpc), XFree86 and DRI developer
Software libre enthusiast  \     http://svcs.affero.net/rm.php?r=daenzer



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf