On Friday, June 10, 2005 8:52 am, Jon Smirl wrote: > On 6/10/05, Adam Jackson <[EMAIL PROTECTED]> wrote: > > > My solution to this is to make radeon DRM depend on radeonfb. > > > radeonfb properly attaches to the device and marks everything in > > > use. I chose this method because Xegl wants radeonfb loaded and > > > this scheme has minimal code impact. > > > > This seems like an odd solution. Why wouldn't you just enable > > multiple drivers to attach to the device? > > Attaching multiple drivers to hardware resources is not supported in > Linux. There would all kinds of issues with ref counting resource > reservations, allowing multiple interrupts handlers (who acks the > interrupt), etc. What about loading/unload in different orders? > > In Linux you attach a primary driver to the hardware and then > secondary drivers can attach to the primary one.
And isn't really advisable in general--if multiple drivers want to talk to a device, they have to co-ordinate anyway, so you either end up with a loosely coupled driver group (like DRM/DRI/DDX) or a more tightly coupled driver subsystem/subdriver type setup. Your approach is the latter, and I think it's probably best. Jesse ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
