linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [patch] radeonfb: FB_WAITFORVSYNC implementation
Date: Sun, 13 Mar 2005 10:23:31 +1100	[thread overview]
Message-ID: <1110669811.19810.46.camel@gaston> (raw)
In-Reply-To: <9e4733910503120821469e9b61@mail.gmail.com>

On Sat, 2005-03-12 at 11:21 -0500, Jon Smirl wrote:
> On Sat, 12 Mar 2005 18:10:40 +0200, Ville Syrjälä <syrjala@sci.fi> wrote:
> > On Sat, Mar 12, 2005 at 11:00:56AM -0500, Jon Smirl wrote:
> > > On Sat, 12 Mar 2005 17:51:39 +0200, Ville Syrjälä <syrjala@sci.fi> wrote:
> > > > It's not a problem if one doesn't use X.Org/XFree86. Also this patch
> > > > should not affect X.Org/XFree86 users unless they manage to call the
> > > > FBIO_WAITFORVSYNC ioctl. matroxfb and atyfb both have similar interrupt
> > > > support and X can still be used with both.
> > >
> > > Almost all PPC Linux boxes are running radeonfb with Xorg.
> > 
> > What's your point? I doubt X.Org uses FBIO_WAITFORSYNC so the patch
> > should not interfere with anything.
> 
> Run something on one VT that uses radeonfb with FBIO_WAITFORSYNC.
> Switch to VT with xorg.
> Reboot box.

Not necessarily. We have the concept of active VT. FBIO_WAITFORSYNC only
need to enable interrupts during the ioctl execution, and mail stop
waiting and return an error if blank/set_var is called (and thus a VT
switch happens).

Ben.




-------------------------------------------------------
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_ide95&alloc_id\x14396&op=click

  reply	other threads:[~2005-03-12 23:24 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 [this message]
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
     [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=1110669811.19810.46.camel@gaston \
    --to=benh@kernel.crashing.org \
    --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).