From: "Michel Dänzer" <michel@daenzer.net>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [patch] radeonfb: FB_WAITFORVSYNC implementation
Date: Sat, 12 Mar 2005 14:20:24 -0500 [thread overview]
Message-ID: <1110655224.4010.469.camel@localhost> (raw)
In-Reply-To: <1110647557.5997.98.camel@atlantis.netenviron.com>
On Sat, 2005-03-12 at 17:12 +0000, Torgeir Veimo wrote:
> On Sat, 2005-03-12 at 12:10 -0500, Michel D채nzer wrote:
> > On Sat, 2005-03-12 at 17:13 +0200, Ville Syrj채l채 wrote:
> > >
> > > Also adding support for FB_ACTIVATE_VBL should be quite simple now.
> >
> > You don't need an interrupt for that. You can choose via the
> > CRTC_OFFSET_CNTL:CRTC_OFFSET_FLIP_CNTL bit whether the update of the
> > CRTC offset should take effect immediately or on the next vertical
> > blank.
> >
> > Personally, I'm not sure why something that needs this functionality
> > can't use the DRM...
>
> My interest for adding this is video playback. It's kind of hard to do
> through the DRM.
You don't have to use the DRM for anything but the wait for vsync; I can
see the effort of initializing the DRM to the point where this is
possible being prohibitive though.
The real point is that the usage of the interrupt needs to be
coordinated between the framebuffer device and the DRM. Something like
the first one to request the IRQ setting up a callback mechanism where
the other can hook into might be a possibility? Or the shared
mini-driver that has been proposed for years, but isn't liked by some...
--
Earthling Michel D채nzer | Debian (powerpc), X and DRI developer
Libre software enthusiast | http://svcs.affero.net/rm.php?r=daenzer
-------------------------------------------------------
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 19:20 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 [this message]
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
[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=1110655224.4010.469.camel@localhost \
--to=michel@daenzer.net \
--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).