linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
* videobuf
@ 2007-10-30 15:28 Robert Woodworth
  2007-10-30 16:19 ` videobuf Grant Likely
  2007-10-30 16:43 ` videobuf Laurent Pinchart
  0 siblings, 2 replies; 4+ messages in thread
From: Robert Woodworth @ 2007-10-30 15:28 UTC (permalink / raw)
  To: linuxppc-embedded

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?




Rob.

 

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: videobuf
  2007-10-30 15:28 videobuf Robert Woodworth
@ 2007-10-30 16:19 ` Grant Likely
  2007-10-30 17:14   ` videobuf Robert Woodworth
  2007-10-30 16:43 ` videobuf Laurent Pinchart
  1 sibling, 1 reply; 4+ messages in thread
From: Grant Likely @ 2007-10-30 16:19 UTC (permalink / raw)
  To: Robert Woodworth; +Cc: linuxppc-embedded

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: videobuf
  2007-10-30 15:28 videobuf Robert Woodworth
  2007-10-30 16:19 ` videobuf Grant Likely
@ 2007-10-30 16:43 ` Laurent Pinchart
  1 sibling, 0 replies; 4+ messages in thread
From: Laurent Pinchart @ 2007-10-30 16:43 UTC (permalink / raw)
  To: linuxppc-embedded

[-- 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 --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: videobuf
  2007-10-30 16:19 ` videobuf Grant Likely
@ 2007-10-30 17:14   ` Robert Woodworth
  0 siblings, 0 replies; 4+ messages in thread
From: Robert Woodworth @ 2007-10-30 17:14 UTC (permalink / raw)
  To: Grant Likely; +Cc: linuxppc-embedded

That does work and nothing seams to be broken just yet.
I also removed the dependency from the vivi (virtual video) module and
that modules works fine.




However, I tried to enable PCI support and that failed with undefined
PCI addresses.  (duh. I have no PCI on the board)



RJW.




On Tue, 2007-10-30 at 10:19 -0600, Grant Likely wrote:
> 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.
> 

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2007-10-30 17:14 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 ` videobuf Laurent Pinchart

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).