Re: [Linux-fbdev-devel] Add three new IOCTLs to FB API

[Geert U. <ge...@li...>]

On Sun, 21 Sep 2003, Jon Smirl wrote:
> I'd like to add three new IOCTLs to the FB API to help support standalone Mesa.
> The idea is to eliminate the need for config files. Xfree might even use these
> in the future.

For 2.4.x or 2.6.0?

> In order to load DRM 3D support I need two pieces of information. The name of
> the 3D DRM driver and the bus:dev:func of the hardware. DRM does not implement
> PCI ID probing, instead you need to it what hardware to use. 
> 
> By adding these to the FB API you can start standalone Mesa just by specifying
> the name of the FB device to use. I can pick up mode and resolution from the
> existing FB API.
> 
> 1) Get location of card that is associated with this fb device. It would return
> bus,dev,func of hardware. There may be more than one piece of the same hardware
> installed.
> 
> 3) Get vendor and card PCI ID

In 2.6.0, you should be able to get them from sysfs, once fbdev does full
sysfs.

Note that both are PCI-specific, for whatever that matters (no DRM for non-PCI
chips anyway, right?).

> 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
> 15 fb ones.

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

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li...

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds