On Mon, 4 Oct 1999, Jos Hulzink wrote:
> On Fri, 1 Oct 1999, [iso-8859-1] Rubén wrote:
>
> > Ah, ok, well, it does what I want, its enough for me. Anyway, I will
> > continue reading docs and learning how to include vertical retrace support
> > into KGIcon, it's best (I have readed the GGI tech. docs, and it seems to be
> > a bit difficult).
>
> Actually, most code is already in the KGIcon ViRGE driver to support that.
> The ViRGE has completely functional vertical retrace interrupt code, but
> at the moment, nothing is done with it. Reason: I have not seen a
> mechanism to get the sync to userspace neatly. (Maybe some
> CHIP_WAITFORRECTRACE ioctl ? We never intended to be real-time, so some
> while not in retrace schedule (); can do the job here)
Perhaps we need a new class of exportable KGI data structures, which
can in turn be exported by fbcon-kgi.c's procfs code so that userspace can
select() on a file to wait for any interrupt the chip can generate?
Jon
---
'Cloning and the reprogramming of DNA is the first serious step in
becoming one with God.'
- Scientist G. Richard Seed
