All of lore.kernel.org
 help / color / mirror / Atom feed
From: Antonino Daplas <adaplas@pol.net>
To: "Michel Dänzer" <michel@daenzer.net>
Cc: James Simmons <jsimmons@infradead.org>,
	Fredrik Noring <noring@nocrew.org>,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Vertical retrace interrupts?
Date: 31 Jan 2003 07:22:16 +0800	[thread overview]
Message-ID: <1043968889.1002.40.camel@localhost.localdomain> (raw)
In-Reply-To: <1043927116.7576.40.camel@thor>

On Thu, 2003-01-30 at 19:45, Michel Dänzer wrote:
> On Don, 2003-01-30 at 03:34, Antonino Daplas wrote:
> > On Wed, 2003-01-29 at 03:21, James Simmons wrote:
> > > 
> > > > Are there any plans on merging DirectFB features? Stuff like vertical
> > > > retrace interrupts etc.?
> > 
> > I wholeheartedly agree with this.  There are a lot of applications out
> > there (especially video players) where vtrace signal delivery is
> > critical for optimum operation.  Polling for VGA registers is not
> > totally correct for newer cards and is too inefficient, so this has to
> > be done at a per driver level.
> 
> Let me point out that the DRM in XFree86 4.3.0 and 2.5 kernels has a
> generic ioctl which can block or send a signal on vertical blank
> interrupts.
> 
> 

Yes, I've seen the dri list archives, and adding support for this in
fbdev will result in code dupliation :-(.

However, at least 3 people have mailed me that they are using their
somewhat old pc as a set top box with mplayer, DirectFB and i810fb. No
X.  The image instability is noticeable because they are driving
big-screen TV's, especially because DirecFB is double-buffered, with
triple-buffering in the TODO list.  It's because of this that I have to
hack in vretrace signal delivary to i810fb.  There's also a similar
patch for matroxfb.


Tony




-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com

  reply	other threads:[~2003-01-30 23:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-26  1:51 Vertical retrace interrupts? Fredrik Noring
2003-01-28 19:21 ` James Simmons
2003-01-30  2:34   ` Antonino Daplas
2003-01-30 11:45     ` Michel Dänzer
2003-01-30 23:22       ` Antonino Daplas [this message]
2003-01-31  0:16         ` Fredrik Noring
2003-01-31  1:35           ` Antonino Daplas
2003-01-31 11:24         ` Michel Dänzer
2003-01-31 11:55           ` Ville Syrjälä
2003-01-31 18:35           ` Antonino Daplas
2003-01-31 19:12             ` Michel Dänzer
2003-01-31 21:32               ` Sven Luther
2003-01-31 23:34                 ` Antonino Daplas
2003-02-01 15:45                   ` Michel Dänzer
2003-02-01 16:50                     ` Antonino Daplas
2003-02-12 20:21                       ` James Simmons
2003-02-12 20:08       ` James Simmons

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=1043968889.1002.40.camel@localhost.localdomain \
    --to=adaplas@pol.net \
    --cc=jsimmons@infradead.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=michel@daenzer.net \
    --cc=noring@nocrew.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.