Message-ID: <4332548E.9050602@aitel.hist.no>
Date: Thu, 22 Sep 2005 08:51:58 +0200
From: Helge Hafting <helge.hafting@aitel.hist.no>
User-Agent: Debian Thunderbird 1.0.2 (X11/20050602)
MIME-Version: 1.0
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
References: <20050922055120.23356.qmail@web33203.mail.mud.yahoo.com> <200509220606.j8M66u8d010990@turing-police.cc.vt.edu>
In-Reply-To: <200509220606.j8M66u8d010990@turing-police.cc.vt.edu>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1158
Lines: 34

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/