The situation *is* really quite simple. Video drivers belong in
the kernel.
Jon
* end quote *
I disagree with you here. But only partially. My understanding of KGI
may be very flawed, but I will refer to my understanding of it here.
The Kernel is not necessarily responsible to have drivers for every
device in it. But, in a true OS desing such as Linux or Unix, its job
is to arbitrate, control access to, and provide a consistent interface
to all devices of same type.
It is my understanding that KGI/GGI (together here, because I think it
is both in this case) provides just the absolutely needed parts in the
kernel to provide safety, security, and stability. The rest I believe
is user space. (No, I am not educating you on a project you take more
part in than myself... I take none, just try to stay up on
design/technical issues of it.)
The argument: I think in the case of video that the kernel interface
should be the absolutely smallest possible. I believe it was either
Einstein or Edison that said, "Things should be made as simple as
possible and no simpler." Put enough (Very small amount) of the code to
allow mode changing, register access, console stuff, etc, in the kernel
and leave the rest for user space libs etc to twiddle through some
interface (syscalls?).
Now, just like SCSI cards, this may mean what is in the kernel changes
depending on how much support (generic VGA) or the type of card
(Permedia 2) you want to support, but the interface to programs should
remain the same.
I will admit, when I mispoke and frustrated GGI people, Linux, and I
believe Alan and Dave as well when this debate last raged (8 mos ago), I
promised myself I wouldn't get involved in this debate ever again. I
just needed to speak my small part, especially the quote from whoever it
was that said it (I know it was one of the two). I think it is some
good words to live by in any software development project: be it kernel;
monolithic or microkernel, database, office suite, whatever.
Trever Adams
highlander@teleteam.net
P.S. Please do not CC anyone directly with any text from my message
unless they responded directly to it in the first place. I do not like
flame wars and do not want to help keep this one going.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html