Re: Add three new IOCTLs to FB API

[Ian Romanick <idr@us.ibm.com>]

Geert Uytterhoeven wrote:
> On Sun, 21 Sep 2003, Jon Smirl wrote:
> 
>>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?).

Right.  Just PCI and AGP (which looks like PCI).  Presumably PCI Express 
will look the same.  I can't imagine ISA or VLB cards being supported. 
Ever.  At some point someone *may* support Sun's UPA or some other 
proprietary graphics interface, but I wouldn't lose too much sleep over 
it. :)

>>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.

I'm not that familiar with how sysfs works.  How would this look? 
There'd be a tree like:

     /sys/
         card0/
             dri.so (link to client-side driver)
             DRM_device (link to DRM device that will load kernel module)
             PCI_INFO (file containing PCI device information)

Or something roughly similar?  If so, I think this would be a 
*wonderful* way to handle it. :)




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