From: Helge Hafting <helge.hafting@aitel.hist.no>
To: Valdis.Kletnieks@vt.edu
Cc: rep stsb <repstsb@yahoo.ca>,
linux-kernel@vger.kernel.org, 06020051@lums.edu.pk
Subject: Re: In-kernel graphics subsystem
Date: Thu, 22 Sep 2005 08:51:58 +0200 [thread overview]
Message-ID: <4332548E.9050602@aitel.hist.no> (raw)
In-Reply-To: <200509220606.j8M66u8d010990@turing-police.cc.vt.edu>
Valdis.Kletnieks@vt.edu wrote:
>On Thu, 22 Sep 2005 01:51:20 EDT, rep stsb said:
>
>
>
>>1. Convert svgalib drivers into kernel modules to get
>>v-sync interrupts.
>>
>>2. Write a windowing program on svgalib.
>>
>>
>
>Wouldn't it make more sense to extend the current framebuffer driver
>support to support v-sync? (framebuffers are already in the kernel, and
>there were so many security holes with svgalib-based programs that it left
>a bad taste in a lot of people's mouths)
>
>And having gotten a v-sync interrupt, what would you *do* with it?
>You'll need an API here....
>
>
Simple. What we want from such interrupts, is to wait for them, no?
So lets use one of the existing structures made for waiting. One example
is a file descriptor. Do a blocking read, which the kernel unblocks when
the interrupt comes in. A file descriptor also supports things like
select() if need be.
Helge Hafting
next prev parent reply other threads:[~2005-09-22 6:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-22 5:51 In-kernel graphics subsystem rep stsb
2005-09-22 6:06 ` Valdis.Kletnieks
2005-09-22 6:51 ` Helge Hafting [this message]
2005-09-22 8:35 ` rep stsb
2005-09-22 6:55 ` Ian Romanick
[not found] <AcW+QBo8uJ+XV7vHTZWR1mo7M5VcNg==>
2005-09-21 0:05 ` Athar Hameed
2005-09-21 0:30 ` Kyle Moffett
2005-09-22 10:12 ` Marek W
2005-09-21 0:42 ` Matheus Izvekov
2005-09-21 2:55 ` Christopher Prest
2005-09-21 10:32 ` Dave Airlie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4332548E.9050602@aitel.hist.no \
--to=helge.hafting@aitel.hist.no \
--cc=06020051@lums.edu.pk \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=repstsb@yahoo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).