On Thu, Jun 16, 2005 at 11:49:41AM -0400, Jon Smirl wrote: > Another proposal is to write a third stub driver. This driver would > hook to the ints, suspend, etc. Then DRM and fbdev would register with > it. This would work but nobody wants to fix 67 fbdev drivers to use > it.
If a new architecture gets buy-in from the assorted developers, then the conversion can be done incrementally (ie one driver at a time) can't it? There shouldn't be a need for a flag day. Please enlighten me if there's some reason why converting the radeon fbdev / drm drivers might depend on whether the rest of fbdev has been converted or not! > There is also kickback from the BSD people. There is a bunch of code > duplicated between fbdev and DRM. The copy in DRM can be removed and > fbdev called, but BSD doesn't have fbdev. Can that code not be moved into the BSD-specific drm directory as part of the above refactoring? ISTR that you'd done some of this already Jon. Is that code actually available anywhere? Phil -- http://www.kantaka.co.uk/ .oOo. public key: http://www.kantaka.co.uk/gpg.txt ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click -- _______________________________________________ Dri-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dri-devel
