From: "Ville Syrjälä" <syrjala@sci.fi>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [patch] radeonfb: FB_WAITFORVSYNC implementation
Date: Sat, 12 Mar 2005 17:51:39 +0200 [thread overview]
Message-ID: <20050312155139.GA28135@sci.fi> (raw)
In-Reply-To: <9e473391050312073314dcb39f@mail.gmail.com>
On Sat, Mar 12, 2005 at 10:33:45AM -0500, Jon Smirl wrote:
> You can't do this without coordination from X and DRM. If either of
> those are in use you will lock the machine with this patch. DRM also
> implements WAITFORVSYNC as well as other interrupts. If you clear the
> ISR DRM is going to stop working.
>
> X is a bigger problem. If the radeonfb adapter is not the primary X
> adapter, X is going to disable its IO/MEM access at the PCI level on
> VT switch. Your radeonfb will then take an interrupt and not be able
> to acknowledge it. This results in an interrupt loop and you rebooting
> your machine.
>
> See the "Who is stomping PCI config space?" thread in the x.org xserver list.
>
> Because of these issues WAITFORVSYNC in radeondb has to wait for
> merged DRM/fbdev to be implemented.
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.
--
Ville Syrjälä
syrjala@sci.fi
http://www.sci.fi/~syrjala/
-------------------------------------------------------
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
next prev parent reply other threads:[~2005-03-12 15:51 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ä [this message]
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
[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=20050312155139.GA28135@sci.fi \
--to=syrjala@sci.fi \
--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).