From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Robert Woodworth" <rwoodworth@securics.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: videobuf
Date: Tue, 30 Oct 2007 10:19:49 -0600 [thread overview]
Message-ID: <fa686aa40710300919y4f231eb4w4ba4bc0c8d9260ff@mail.gmail.com> (raw)
In-Reply-To: <1193758138.4606.7.camel@PisteOff>
On 10/30/07, Robert Woodworth <rwoodworth@securics.com> 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?
You could try dropping the dependency from Kconfig and see what breaks
when you compile the core v4l2 stuff.
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
next prev parent reply other threads:[~2007-10-30 16:19 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 ` Grant Likely [this message]
2007-10-30 17:14 ` videobuf Robert Woodworth
2007-10-30 16:43 ` videobuf Laurent Pinchart
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=fa686aa40710300919y4f231eb4w4ba4bc0c8d9260ff@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=linuxppc-embedded@ozlabs.org \
--cc=rwoodworth@securics.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 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).