From: Torgeir Veimo <torgeir@pobox.com>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [patch] radeonfb: FB_WAITFORVSYNC implementation
Date: Wed, 16 Mar 2005 01:28:53 +0000 [thread overview]
Message-ID: <1110936533.5511.22.camel@africa.netenviron.com> (raw)
In-Reply-To: <1110670230.19810.51.camel@gaston>
On Sun, 2005-03-13 at 10:30 +1100, Benjamin Herrenschmidt wrote:
> On Sat, 2005-03-12 at 14:06 +0000, Torgeir Veimo wrote:
> > This is an implementation of the FB_WAITFORVSYNC ioctl for the radeonfb.
> > A small test application is attached at the end. This patch is against
> > vanilla 2.6.11.
> The patch definitely needs a lot of cleanups. A few things are wrong
> too, like using test_and_set_* as a mean of locking. This doesn't work
> on relaxed ordering architectures.
>
> Besides, the entire fbdev subsystem is protected by the console
> semaphore, so you shouldn't need anything else. You need to acquire it
> yourself in the driver ioctl() routine though.
>
> In order to avoid conflicting with other apps, you should probably
> "abort" the operation if a console switch happens while you are waiting.
> That is, a set_var() and/or a blank(). Return -EINTR or something like
> that.
Do you have any example code I can look at for this? From what I can see
neither the atyfb or matroxfb drivers do this. Not that I'm claiming
they're correct, I guess the current vanilla kernel source is a bit
behind the latest and greatest fb development.
--
Torgeir Veimo <torgeir@pobox.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
next prev parent reply other threads:[~2005-03-16 1:28 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-12 14:06 [patch] radeonfb: FB_WAITFORVSYNC implementation Torgeir Veimo
2005-03-12 15:13 ` Ville Syrjälä
2005-03-12 16:59 ` Torgeir Veimo
2005-03-12 17:10 ` Michel Dänzer
2005-03-12 17:12 ` Torgeir Veimo
2005-03-12 19:20 ` Michel Dänzer
2005-03-12 19:35 ` Jon Smirl
2005-03-12 23:33 ` Benjamin Herrenschmidt
2005-03-12 17:33 ` Ville Syrjälä
2005-03-16 1:28 ` Torgeir Veimo
2005-03-16 1:59 ` Ville Syrjälä
2005-03-16 6:19 ` Michel Dänzer
2005-03-12 15:33 ` Jon Smirl
2005-03-12 15:51 ` Ville Syrjälä
2005-03-12 16:00 ` Jon Smirl
2005-03-12 16:10 ` Ville Syrjälä
2005-03-12 16:21 ` Jon Smirl
2005-03-12 23:23 ` Benjamin Herrenschmidt
2005-03-12 17:03 ` Torgeir Veimo
2005-03-12 17:21 ` Torgeir Veimo
2005-03-12 17:56 ` Jon Smirl
2005-03-12 23:21 ` Benjamin Herrenschmidt
2005-03-12 23:14 ` Benjamin Herrenschmidt
2005-03-13 3:15 ` Torgeir Veimo
2005-03-12 23:30 ` Benjamin Herrenschmidt
2005-03-16 1:28 ` Torgeir Veimo [this message]
[not found] <20050313012923.60373.qmail@web14926.mail.yahoo.com>
2005-03-13 1:37 ` Benjamin Herrenschmidt
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=1110936533.5511.22.camel@africa.netenviron.com \
--to=torgeir@pobox.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).