On Mon, 2003-07-14 at 19:55, Jon Smirl wrote: > -- Michel Dnzer <[EMAIL PROTECTED]> wrote: > > The problem is direct register writes while the CP > > is running. Even > > radeonfb ioctls can cause lockups, the XFree86 > > radeon driver at least > > grabs the DRM lock and idles the CP around them, it > > even stops the CP > > for some. > > > > What about merging radeonfb and radeon drm in 2.7? The > current radeonfb hardly does anything but init the > card and handle mode changes. Unifying the device > drivers will allow a unified lock. It would also allow > for a lot of code cleanup.
I don't see much overlap except maybe some register definitions, and there are valid reasons why someone would want a framebuffer device but not a DRM and vice versa. Cooperation would be great where it makes sense (e.g. for vsync), but I'm still not convinced that a merger would be a good idea. That being said, it's always better to discuss actual proposals instead of speculations. :) -- Earthling Michel D�nzer \ Debian (powerpc), XFree86 and DRI developer Software libre enthusiast \ http://svcs.affero.net/rm.php?r=daenzer -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe directfb-dev" as subject.
