Re: [Q] v4l buffer format inside isoc

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 20 Mar 2012 21:05:13 -0300
Ezequiel García <elezegarcia@xxxxxxxxx> wrote:

> I'm a little lost while writing a driver for an easycap device
> (saa7113 capture device).
> I have my isoc handler, and the isoc urb flying OK.
> I also have the videobuf2 queue setup (or at least I think so), and I understand
> I need to call vb2_buffer_done() with a filled buffer.
> 
> What I DON'T understand is how should I fill such buffer?
> I mean, what *format* comes inside the isoc buffer?
> 
> Should I look at saa7113 datasheet?
> Should I base in em28xx?
> 
> I'm sorry to ask such a generic question.
> Perhaps, someone cares enough to give me a hint.

Hi Ezequiel,

The saa7113 chip is (also?) handled by the gspca spca506 subdriver
which may be a base for your device.

In the gspca test tarball (see my site), I merged the spca506 code into
the spca505 for a webcam which may also do analog video capture. The
webcam works, but the analog video capture has never been tested.
Also, the gspca_main <-> subdriver interface for vidioc_s_input and
vidioc_s_std is not very clean.

So, you might include your device in this new spca505 subdriver,
forgetting about urb, isoc, videobuf.., and just concentrating on the
device management (image format, video controls, USB exchanges..). I am
ready to cleanup and extend the gspca subdriver interface to handle any
specific need.

-- 
Ken ar c'hentañ	|	      ** Breizh ha Linux atav! **
Jef		|		http://moinejf.free.fr/
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Input]     [Video for Linux]     [Gstreamer Embedded]     [Mplayer Users]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]
  Powered by Linux