I think that the wisest approach is, instead of suggesting a kernel module to the XFree86 folks, you do two things. First, suggest a kernel module to the Linux folks that implements a protocol for accessing the resource you are trying to use. Then you go to the XFree86 folks and suggest a module to utilize that protocol in the X server.

Raymond Jennings wrote:
Oh my!

Judging from the large number of *flames* I got for suggesting it, I guess a kernel module for X is not such a good idea after all.

Oh well, I hope it was at least worth brainstorming.

XFree86 *might* wish to consider a "modulette" to cover things that userland CAN'T do, like AGP, DMA, IRQ, and so on. Or maybe the modulette could grant I/O privileges on behalf of an X server that opens it (thus the X server doesn't require root privileges)? Perhaps some extensions to /dev/framebuffer? A smaller module may involve less overhead.

Does the notion of a kernel module have ANY merit at all? Or was the idea complete garbage?

PLEASE: Don't flame me, and if there are serious flaws with my ideas, please be specific so I know what to fix.

_________________________________________________________________
Surf and talk on the phone at the same time with broadband Internet access. Get high-speed for as low as $29.95/month (depending on the local service providers in your area). https://broadband.msn.com


_______________________________________________
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel


_______________________________________________
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel

Reply via email to