> > Overall, I don't think its a good idea to bring graphics stuff into the ELKS
>kernel, yet.
> > Especially since the plan is there'll be only one graphics server running per
> > ELKS system, ever.
> >
>
> Okay, we can rely on the ioctl made to initially request graphics access to
> lock the graphics hardware, and keep the actual hardware access in user space.
Well - for the first version, there's nothing from preventing a program
from issuing the int10 without making the ioctl(). A better problem is the redrawing
of the VC text after the exit back to text mode... Should the driver do this or ELKS?
>
> Al
>
- RE: NanoX version 0.3 released Greg Haerr
- RE: NanoX version 0.3 released Shane Kerr
- RE: NanoX version 0.3 released David Murn
- RE: NanoX version 0.3 released Riley Williams
- RE: NanoX version 0.3 released Greg Haerr
- Re: NanoX version 0.3 released Ansel
- Re: NanoX version 0.3 released David Murn
- Re: NanoX version 0.3 released Alistair Riddoch
- Re: NanoX version 0.3 released Dan Olson
- Re: NanoX version 0.3 released Jakob Eriksson
- Re: NanoX version 0.3 released Greg Haerr
- Re: NanoX version 0.3 released Alistair Riddoch
- Re: NanoX version 0.3 released Eric J. Korpela
- RE: NanoX version 0.3 released Greg Haerr
- RE: NanoX version 0.3 released Gray, David W.
