From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jon Smirl Subject: Re: waitforVBlank, how does this even work? Date: Wed, 2 Mar 2005 12:09:12 -0500 Message-ID: <9e473391050302090926854d95@mail.gmail.com> References: <9e473391050301215019081bce@mail.gmail.com> Reply-To: Jon Smirl Mime-Version: 1.0 Content-Transfer-Encoding: 7bit In-Reply-To: Sender: dri-devel-admin@lists.sourceforge.net Errors-To: dri-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , List-Archive: Content-Type: text/plain; charset="us-ascii" To: Vladimir Dergachev Cc: fbdev , DRI developer's list On Wed, 2 Mar 2005 11:32:44 -0500 (EST), Vladimir Dergachev wrote: > What about isolating interrupt-handling code into a small driver ? > Something simple to respond to interrupts and call all handlers with a > certain mask. My current plan is that fbdev is the base driver and I will modify the other drivers to bind to it. It is possible to split about 50K out of the fbdev driver into another module and make a smaller base driver but I'm not working on size isssues. Right now all I want to do is get a combined fbdev/DRM on the radeon with enough features to support mesa-solo. XGL needs most of both DRM and fbdev features. After that I have to spend a bunch of time getting it into Linus' tree. I would find it useful if someone came up with a standard kernel space V4L radeon driver instead of the Gatos stuff. -- Jon Smirl jonsmirl@gmail.com ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click --