From: Laurent Pinchart <laurentp@cse-semaphore.com>
To: linuxppc-embedded@ozlabs.org
Subject: Re: videobuf
Date: Tue, 30 Oct 2007 17:43:16 +0100 [thread overview]
Message-ID: <200710301743.18580.laurentp@cse-semaphore.com> (raw)
In-Reply-To: <1193758138.4606.7.camel@PisteOff>
[-- Attachment #1: Type: text/plain, Size: 760 bytes --]
On Tuesday 30 October 2007 16:28, Robert Woodworth wrote:
> I'm working on building a v4l2 driver for an FPGA module on a Xilinx
> Virtex4 PPC.
>
> Question:
> Why does the v4l2 videobuf *depend* on PCI?
Historical reasons I guess. The videobuf module has been designed for PCI
hardware (bttv if I'm not mistaken). Now that other, non-PCI devices would
benefit from videobuf, PCI-specific support is being moved to a separate
module.
Search the video4linux mailing list archive for discussions about videobuf
cleanup. You can get the latest source tree at www.linuxtv.org.
Best regards,
--
Laurent Pinchart
CSE Semaphore Belgium
Chaussée de Bruxelles, 732A
B-1410 Waterloo
Belgium
T +32 (2) 387 42 59
F +32 (2) 387 42 75
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2007-10-30 16:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-30 15:28 videobuf Robert Woodworth
2007-10-30 16:19 ` videobuf Grant Likely
2007-10-30 17:14 ` videobuf Robert Woodworth
2007-10-30 16:43 ` Laurent Pinchart [this message]
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=200710301743.18580.laurentp@cse-semaphore.com \
--to=laurentp@cse-semaphore.com \
--cc=linuxppc-embedded@ozlabs.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.