Re: gstreamer and v4l2

On Tue, Mar 15, 2016 at 9:18 AM, Hans Verkuil wrote: > On 03/15/2016 08:10 AM, Ran Shalit wrote: >> Hello, >> >> This is a bit offtopic, so I will understand if you rather not discuss >> that... >> >> I am trying to use gstreamer with v4l2 vivi device,

gstreamer and v4l2

Hello, This is a bit offtopic, so I will understand if you rather not discuss that... I am trying to use gstreamer with v4l2 vivi device, I first check the capabilities with gst-launch-1.0 --gst-debug=v4l2src:5 v4l2src device="/dev/video0" ! fakesink 2>&1 and it gives many capabilities such as

Multiple open and read of vivi device

Hello, Does anyone knows why vivi is limited to one open ? Is there some way to patch it for multiple opens and reading ? Regards, Ran -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vge

Re: CMA usage in driver

On Sat, Jan 2, 2016 at 11:23 PM, Ran Shalit wrote: > Hello, > > I made some reading on CMA usage with device driver, nut not quite sure yet. > Do we need to call dma_declare_contiguous or does it get called from > within videobuf2 ? > > Is there any example how to use CMA

CMA usage in driver

Hello, I made some reading on CMA usage with device driver, nut not quite sure yet. Do we need to call dma_declare_contiguous or does it get called from within videobuf2 ? Is there any example how to use CMA memory in v4l2 driver ? Best Regards, Ran -- To unsubscribe from this list: send the lin

PCIe sg dma device used as dma-contig

Hello, The following question is not totally in the scope of v4l2, but more about your advise concering dma alternatives for non-expreciened v4l2 device writer. We intend to use the fpga for concurrent 3xHD and 3xSD. We have some dillema regadring the fpga to choose from: ALTERA fpga which use co

Re: dt3155 as a reference

On Wed, Dec 23, 2015 at 3:09 PM, hverkuil wrote: > On 2015-12-23 13:55, Ran Shalit wrote: >> >> Hello, >> >> I think to use dt3155 as a reference for new pci express driver , >> becuase it is highly simple as a starting point, and contains only >> single

dt3155 as a reference

Hello, I think to use dt3155 as a reference for new pci express driver , becuase it is highly simple as a starting point, and contains only single file :) The driver I'll develop will eventually be used for multiple video capture and single video output. I just wanted to ask if you recommend it a

Re: v4l2 kernel module debugging methods

On Fri, Dec 11, 2015 at 10:50 AM, Fabien DESSENNE wrote: > Hi Ran, > > On 12/10/2015 10:46 PM, Ran Shalit wrote: >> On Sun, Dec 6, 2015 at 2:23 AM, Nicolas Dufresne >> wrote: >>> Le dimanche 06 décembre 2015 à 00:00 +0200, Ran Shalit a écrit : >>>> Hell

Re: v4l2 kernel module debugging methods

On Sun, Dec 6, 2015 at 2:23 AM, Nicolas Dufresne wrote: > Le dimanche 06 décembre 2015 à 00:00 +0200, Ran Shalit a écrit : >> Hello, >> >> I would like to ask a general question regarding methods to debug a >> v4l2 device driver. >> Since I assume that the kerne

fbdev - wipe screen (dd) with ioctl ?

Hello, I use the following to wipe a screen: dd if=/dev/zero of=/dev/fb0 code Is there a way to do the same thing in code (using ioctl I suppose) ? Regards, Ran -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More ma

v4l2 kernel module debugging methods

Hello, I would like to ask a general question regarding methods to debug a v4l2 device driver. Since I assume that the kernel driver will probably won't work in first try after coding everything inside the device driver... 1. Do you think qemu/kgdb debugger is a good method for the device driver

Interrupt handler responsibility

Hello, I am trying to understand the interrupt handler responsibility in v4l2, also with respect to dma usage. I see that it is not defined as part of the videobuf2 API. This is what I understand this far: 1. start_streaming is responsible for getting into "streaming" state. dma start should be t

Re: cobalt & dma

>> >> 1. I tried to understand the code implementation of videobuf2 with >> regards to read(): >> read() -> >> vb2_read() -> >> __vb2_perform_fileio()-> >> vb2_internal_dqbuf() & copy_to_user() >> >> Where is the actual allocation of dma contiguous memory ? Is done with

Re: cobalt & dma

Hello, > > No. All video capture/output devices all use DMA since it would be > prohibitively > expensive for the CPU to do otherwise. So just dig in and implement it. I am trying to better understand how read() operation actually use the dma, but I can't yet understand it from code. > > No.

Re: cobalt & dma

On Tue, Nov 17, 2015 at 3:54 PM, Hans Verkuil wrote: > On 11/17/15 14:15, Ran Shalit wrote: >> On Tue, Nov 17, 2015 at 9:53 AM, Hans Verkuil wrote: >>> On 11/17/2015 08:39 AM, Ran Shalit wrote: >>>> Hello, >>>> >>>> I intend to use cobalt d

Re: cobalt & dma

On Tue, Nov 17, 2015 at 9:53 AM, Hans Verkuil wrote: > On 11/17/2015 08:39 AM, Ran Shalit wrote: >> Hello, >> >> I intend to use cobalt driver as a refence for new pci v4l2 driver, >> which is required to use several input simultaneously. for this cobalt >>

cobalt & dma

Hello, I intend to use cobalt driver as a refence for new pci v4l2 driver, which is required to use several input simultaneously. for this cobalt seems like a best starting point. read/write streaming will probably be suffecient (at least for the dirst debugging). The configuration in my cast is i

Re: ivtv: PVR family datasheet ?

On Sun, Nov 15, 2015 at 4:29 PM, Ran Shalit wrote: > Hello, > > I was seaching for datasheet of Hauppauge PVR-150 (or other), but can't find > it. > Does anyone know where it can be found ? Hi, I actually refer to CX23418 chip, which I don't find its datasheet (I saw i

ivtv: PVR family datasheet ?

Hello, I was seaching for datasheet of Hauppauge PVR-150 (or other), but can't find it. Does anyone know where it can be found ? Best Regards, Ran -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at

v4l vs. dpdk

Hello, I hope you can assist me on the following debate. I need to develop a driver/application which capture and output video frames from PCIe device , and is using Intel cpu (i7), and Intel's media sdk server framework for the video compression. I am not sure what will be a better choice betwe

Re: PCIe capture driver

On Wed, Oct 28, 2015 at 12:50 AM, Hans Verkuil wrote: > > > On 10/27/2015 22:56, Ran Shalit wrote: >> On Tue, Oct 27, 2015 at 12:21 AM, Hans Verkuil wrote: >>> >>> >>> On 10/27/2015 02:04, Ran Shalit wrote: >>>> On Mon, Oct 26, 2015 at 1:46

Re: videobuf & read/write operation

> Don't use videobuf! Use videobuf2, just like the skeleton driver. > > The old videobuf framework is deprecated and you shouldn't use it as it is > horrible. > > Why on earth are you trying to use videobuf if the skeleton driver clearly > uses vb2? > Right, I now see that I was examining code whi

videobuf & read/write operation

Hello, I'm trying to understand how to imeplement v4l driver using videobuf. The videobuf documentation if very helpful. When the documentation refers to " I/O stream" , does it also include the read/write operation or only streaming I/O method ? In case I am using only read/write, do I need to i

Re: PCIe capture driver

On Wed, Oct 28, 2015 at 12:50 AM, Hans Verkuil wrote: > > > On 10/27/2015 22:56, Ran Shalit wrote: >> On Tue, Oct 27, 2015 at 12:21 AM, Hans Verkuil wrote: >>> >>> >>> On 10/27/2015 02:04, Ran Shalit wrote: >>>> On Mon, Oct 26, 2015 at 1:46

Re: PCIe capture driver

On Tue, Oct 27, 2015 at 12:21 AM, Hans Verkuil wrote: > > > On 10/27/2015 02:04, Ran Shalit wrote: >> On Mon, Oct 26, 2015 at 1:46 PM, Steven Toth wrote: >>>> No, use V4L2. What you do with the frame after it has been captured >>>> into memory has no relev

Re: PCIe capture driver

On Mon, Oct 26, 2015 at 1:46 PM, Steven Toth wrote: >> No, use V4L2. What you do with the frame after it has been captured >> into memory has no relevance to the API you use to capture into memory. > > Ran, I've built many open and closed source Linux drivers over the > last 10 years - so I can sp

Re: PCIe capture driver

On Sat, Oct 24, 2015 at 11:38 AM, Hans Verkuil wrote: > > > On 10/23/2015 23:57, Ran Shalit wrote: >> On Tue, Oct 20, 2015 at 9:23 AM, Hans Verkuil wrote: >>> On 10/19/2015 10:26 PM, Ran Shalit wrote: >>>> Hello, >>>> >>>> When w

Re: PCIe capture driver

On Tue, Oct 20, 2015 at 9:23 AM, Hans Verkuil wrote: > On 10/19/2015 10:26 PM, Ran Shalit wrote: >> Hello, >> >> When writing a device driver for capturing video coming from PCIe, >> does it need to be used as v4l device (video for linux) , ? > > Yes. If you don

Re: PCIe capture driver

On Tue, Oct 20, 2015 at 9:23 AM, Hans Verkuil wrote: > On 10/19/2015 10:26 PM, Ran Shalit wrote: >> Hello, >> >> When writing a device driver for capturing video coming from PCIe, >> does it need to be used as v4l device (video for linux) , ? > > Yes. If you don

PCIe capture driver

Hello, When writing a device driver for capturing video coming from PCIe, does it need to be used as v4l device (video for linux) , ? Regards, Ran -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info a

OpenCaster

Hello, I would like to ask if OpenCaster is still active ? Is it still recommended to be used with new design which requires mpeg-ts streaming ? How it is comarted to ffmpeg ? it seems much more simpler to use :) Thank you, Ran -- To unsubscribe from this list: send the line "unsubscribe linux-m

muxing ES to mpeg-ts

Hello, I would please like to ask what is a good choice for muxing ES to mpeg transport stream. It is required to do this in application (muxing the encoder output into mpeg-ts which is transffered in ethernet udp). I know that both ffmpeg and opencaster can support this. What do you think will