Hey all, I've been following the discussion on driver simplification, and I'm not quite sure I understand everything that has been said. As I understand it, you are trying to make kernel drivers just init the hardware, and provide hooks for userspace software to drive the hardware themselves?
(ie, fbcon and dri get merged, and the kernel driver just provides video mode switching, video memory management, state management, and enough access for dri-userland to do everything else) If this is right, is there any way to provide an easy and well thoughtout framework? Like, fbcon drivers have the bad habit of not having the same method of telling them what modes to use. (Some only work with vga=, some only work with mode=, and some (correctly) use modedb (like they should)); and X does a lot of hardware poking when it shouldn't, and X drives a lot of the 2D stuff itself, when it really should be using the fbcon driver's abilities as much as possible (which probably arn't properly exposed (which I bet is pissing off a lot of directfb devs)) Thanks in advance -- Patrick "Diablo-D3" McFarland || [EMAIL PROTECTED] "Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd all be running around in darkened rooms, munching magic pills and listening to repetitive electronic music." -- Kristian Wilson, Nintendo, Inc, 1989
signature.asc
Description: Digital signature
