From: Steven Toth <stoth@kernellabs.com>
To: Manu Abraham <abraham.manu@gmail.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: buffer management
Date: Wed, 23 Jun 2010 08:43:17 -0400 [thread overview]
Message-ID: <4C220165.50809@kernellabs.com> (raw)
In-Reply-To: <AANLkTikuPBKre8wjkGZ-fXhQc5ad_OmNtERvFslpPXvR@mail.gmail.com>
> Now, on each video interrupt, I know which SG list i need to read
> from. At this stage i do need to copy the
> buffers associated with each of the SG lists at once. In this
> scenario, I don't see how videobuf could be used,
> while I keep getting this feeling that a simple copy_to_user of the
> entire buffer could do the whole job in a
> better way, since the buffers themselves are already managed and
> initialized already. Am I correct in thinking
> so, or is it that I am overlooking something ?
Manu,
SAA7164 suffers from this. If you find a solution I'd love to hear it.
Regards,
- Steve
--
Steven Toth - Kernel Labs
http://www.kernellabs.com
next prev parent reply other threads:[~2010-06-23 12:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-22 17:02 buffer management Manu Abraham
2010-06-23 12:43 ` Steven Toth [this message]
2010-06-23 16:09 ` Marko Ristola
2010-06-30 18:42 ` Marko Ristola
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=4C220165.50809@kernellabs.com \
--to=stoth@kernellabs.com \
--cc=abraham.manu@gmail.com \
--cc=linux-media@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox