> So why do you want it in kernel.... security is not the sensible answer
> here.
I'm not proposing the KGI solution where every device driver presents
the same API. That model does require a lot of code in the kernel.
The existing DRM model where each driver provides it's own API is a
good one. The user space DRI driver then takes this API and turns it
into a standard one. Applying the DRM style model to fbdev may allow
parts of fbdev to be moved out to user space.
What I don't want is a permanent root priv process hanging around in
the system. It simply isn't needed and I have prototyped a system that
runs without root so I know it can be done. With minor mods DRI can
run without the need for root, with more major mods the X server can
run without the need for root. Most of the mods to the X server are to
remove things like PCI bus probing, mode setting and VBIOS support.
--
Jon Smirl
[email protected]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
