Alan Cox writes:
> On Iau, 2004-05-06 at 09:39, Egbert Eich wrote:
> > Furthermore I'd argue that as little as necessary should live in the
> > kernel space. One thing that - in my opinion - should *not* live in
> > there is mode detection and initialization.
>
> There is a need to handle some mode setup/init in the kernel (think
> about non-text mode hardware) but the hotplug interface allows most
> cards to do that in userspace, and all the discussion so far seems
> keen on that [Kernel folk believe lots should be done in user space
> too!]
Alan,
That sounds good! (But we never had problems agreeing on things ;-) )
Whatever code we decide to put into the kernel, we should provide
an abstraction layer to not expose the driver writer to arbitrary
kernel interfaces. This aids portability, helps to keep things stable
and makes this code independent of changes in other parts of the
kernel.
My experience at least with video driver code is that it is 'expensive'
compared to most other software. So people working on such code have a
different focus than the rest of the world.
Cheers,
Egbert.
-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to
deliver higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
--
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
