Re: Kernel video driver (was: Boot problem @ /hurd/ext2fs.static)
On Mon, 2002-06-17 at 09:42, Niels Möller wrote:
> > The idea seems to be to use memory mapping and a translator so
> > applications can just write to this translator to access the video
> > memory. The kernel would than directly talk to the
> > hardware, for example through a VESA driver. Is that correct?
>
> More or less. One alternative is to have the *translator* talk
> directly to the hardware, so that you don't have to hack the kernel
> (you'd still need to run the translator as root, though). Moving
> device drivers in general out from the kernel and into userspace
> programs is a long term plan.
That sounds like a good plan. Any thoughts how this should work in
detail? I mean, should the translator just be something like a "pipe" to
the video memory or should it already provide drawing functions? Should
it allow access from every application? I apologize for writing more
questionmarks than fullstops and include this sentence to make it look
less dumb. I just had the idea to look how svgalib is realized, maybe
this would be a good starting point? I would be glad for any pointers to
what I should try to learn first or next.
- Daniel
--
To UNSUBSCRIBE, email to debian-hurd-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: