All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Smirl <jonsmirl@gmail.com>
To: Eric Sellers <sellers-eric@rogers.com>
Cc: Vladimir Dergachev <volodya@mindspring.com>,
	fbdev <linux-fbdev-devel@lists.sourceforge.net>,
	DRI developer's list <dri-devel@lists.sourceforge.net>
Subject: Re: waitforVBlank, how does this even work?
Date: Wed, 2 Mar 2005 14:06:08 -0500	[thread overview]
Message-ID: <9e473391050302110615272990@mail.gmail.com> (raw)
In-Reply-To: <200503021308.23110.sellers-eric@rogers.com>

On Wed, 2 Mar 2005 13:08:23 -0500, Eric Sellers <sellers-eric@rogers.com> wrote:
> You can use my module with or without X
> (right now it only supports the older mach64 cards)
> 
> The only problem is there is no way of telling X where
> the capture buffers are. So you might get some corruption on screen when X
> uses that memory and it gets overwritten by a frame and then copied back.
> 
> The more memory you have the less you will notice this.
> (so if you have a 4 meg card, you might want to keep your resolution and bit
> depth down)
> 
> If there was a userspace program that could allocate the end of video memory
> there would be no problem.

I'm working on the radeon fbdev and DRM drivers currently. I can fix
the memory management for V4L if there is a radeon driver available.


> 
> Eric
> 


-- 
Jon Smirl
jonsmirl@gmail.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

  reply	other threads:[~2005-03-02 19:06 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-02  5:50 waitforVBlank, how does this even work? Jon Smirl
2005-03-02  5:55 ` Jon Smirl
2005-03-02  7:10 ` Benjamin Herrenschmidt
2005-03-02  7:30   ` [Linux-fbdev-devel] " Ville Syrjälä
2005-03-02  7:53     ` Benjamin Herrenschmidt
2005-03-02 14:42       ` Torgeir Veimo
2005-03-02 16:32 ` Vladimir Dergachev
2005-03-02 17:09   ` Jon Smirl
2005-03-02 17:15     ` Vladimir Dergachev
2005-03-02 17:30       ` Jon Smirl
2005-03-02 17:45         ` Vladimir Dergachev
2005-03-02 17:51           ` Jon Smirl
2005-03-02 19:45             ` Vladimir Dergachev
2005-03-02 18:08           ` Eric Sellers
2005-03-02 19:06             ` Jon Smirl [this message]
2005-03-02 17:29   ` James Simmons
2005-03-02 22:38     ` Benjamin Herrenschmidt
2005-03-03  0:04       ` James Simmons
2005-03-02 23:42   ` Benjamin Herrenschmidt
2005-03-03  1:03     ` Vladimir Dergachev
2005-03-03  2:23       ` Benjamin Herrenschmidt
2005-03-03  3:01         ` Vladimir Dergachev
2005-03-03  7:55           ` Ville Syrjälä
2005-03-03 15:12             ` Vladimir Dergachev
2005-03-03 22:47               ` Benjamin Herrenschmidt
2005-03-03 22:08             ` Benjamin Herrenschmidt
2005-03-04 13:18               ` Ville Syrjälä
2005-03-04 22:35                 ` Benjamin Herrenschmidt
2005-03-05  6:30                   ` Ville Syrjälä

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=9e473391050302110615272990@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=sellers-eric@rogers.com \
    --cc=volodya@mindspring.com \
    /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.