What about the fundamental question? We have several pairs of device drivers that want to control the same hardware. One example would be radeon DRM and radeon Framebuffer. How should these drivers coordinate probing and claiming resources?
What should be the policy for multiple drivers? 1) try new probe first and fall back to old scheme. First driver that loads gets the new probe, second gets the old. First driver reserves resources. 2) Require a mini driver that handles probing. Then both drivers attach to the mini driver. 3) Declare it illegal and make the drivers merge. 4) Declare it illegal and only allow first one loaded to run. Right now radeonfb handles probing and resource reservation. DRM works in stealth mode. DRM uses all of the resources and never tells the kernel, that's how it avoids conflicting with framebuffer. DRM and framebuffer trade off control at VT switch. 2D state is save and restored. There is an assumption that framebuffer won't mess with the 3D state. I'm not sure that suspend/resume are coordinated in any way. ===== 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/ _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
