DRM and Framebuffer conflicts
A message that is not in the archive (sent off-list or not yet received): 1066889583.643.2.camel@leguin
Quoted 5 lines · --- Eric Anholt
I've converted the DRM to old-style attachment. I haven't tested with radeonfb to see if it actually fixed it (netboot linux kernels are annoying to prepare), but my radeon and sis cards continued to work. If someone could test with radeonfb and the latest DRM, that would be great.
I think we need to implement both the old and new schemes and fallback to the old one if radeonfb is present. DRM also needs to add code marking resources in use which will also conflict with framebuffer. DRM needs to mark the resources when framebuffer isn't around to be compatible with hotplug.
It would flow something like this:
new style probe
if (new probe has device)
mark resources in use
else
do old style probe
The framebuffer drivers that have DRM parallels need to implement the same code. That way it won't matter what order things get loaded.
A second possibility would be to implement a tiny stub for just attaching to the PCI ID and resources. Then framebuffer and DRM could both share the stub.
=====
Jon Smirl
[email protected]
__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com
-------------------------------------------------------
This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/