cron job: media_tree daily build: ERRORS

2015-10-04 Thread Hans Verkuil
This message is generated daily by a cron job that builds media_tree for the kernels and architectures in the list below. Results of the daily build of media_tree: date: Mon Oct 5 04:00:17 CEST 2015 git branch: test git hash: f4f24d1fd0803e8b5de5da373276f5046bef7463 gcc versi

Re: Hauppauge WinTV-HVR2205 driver feedback

2015-10-04 Thread Richard Tresidder
Hi Steven Nope standard x86_64 kernel 3.10.0-229.14.1.el7.x86_64 Was rather surprised as all my quick reading indicates that the kernel should quite happily do this... Though looks like its the largest chunk you can request? I'm not well enough up to speed with the nitty gritty.. There is

Re: v4l2 api: supported resolution negotiation

2015-10-04 Thread Nicolas Dufresne
Le dimanche 04 octobre 2015 à 21:49 +0300, Sakari Ailus a écrit : > I think the GStreamer > v4lsrc tries very small and very large values. The driver will clamp > them to > a supported values which are passed to the application from the > IOCTL. In GStreamer we try ENUM_FRAMESIZE, and when no supp

drivers/media/pci/netup_unidvb/netup_unidvb_core.c:417:18: error: too many arguments to function 'horus3a_attach'

2015-10-04 Thread kbuild test robot
Hi Kozlov, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 049e6dde7e57f0054fdc49102e7ef4830c698b46 commit: 52b1eaf4c59a3bbd07afbb4ab4f43418a807d02e [media] netup_unidvb: NetUP Universal DVB-S/S2/T/T2/C PCI-E card d

Re: v4l2 api: supported resolution negotiation

2015-10-04 Thread Sakari Ailus
On Sun, Oct 04, 2015 at 12:23:08PM +0300, Matwey V. Kornilov wrote: > Hello, > > I learned from V2L2 API how to detect all supported formats using > VIDIOC_ENUM_FMT. > When I perform VIDIOC_S_FMT I don't know how to fill fmt.pix.width and > fmt.pix.height, since I know only format. > How should I

Re: [PATCH 1/5] media: atmel-isi: correct yuv swap according to different sensor outputs

2015-10-04 Thread Guennadi Liakhovetski
Even simpler: On Sun, 4 Oct 2015, Guennadi Liakhovetski wrote: > Hi Josh, > > On Tue, 22 Sep 2015, Josh Wu wrote: > > > we need to configure the YCC_SWAP bits in ISI_CFG2 according to current > > sensor output and Atmel ISI output format. > > > > Current there are two cases Atmel ISI supported

Re: [PATCH 5/5] media: atmel-isi: support RGB565 output when sensor output YUV formats

2015-10-04 Thread Guennadi Liakhovetski
On Tue, 22 Sep 2015, Josh Wu wrote: > This patch enable Atmel ISI preview path to convert the YUV to RGB format. > > Signed-off-by: Josh Wu > --- > > drivers/media/platform/soc_camera/atmel-isi.c | 38 > --- > 1 file changed, 29 insertions(+), 9 deletions(-) > > diff

Re: [PATCH] [media] media-entity: Don't use var length arrays

2015-10-04 Thread Sakari Ailus
Hi Mauro, Mauro Carvalho Chehab wrote: > The graph traversal algorithm currently uses two variable-length > arrays that are dynamically allocated at the stack: > > drivers/media/media-entity.c:238:17: warning: Variable length array is > used. > drivers/media/media-entity.c:239:17: wa

Re: [PATCH 4/5] media: atmel-isi: setup YCC_SWAP correctly when using preview path

2015-10-04 Thread Guennadi Liakhovetski
On Tue, 22 Sep 2015, Josh Wu wrote: > The preview path only can convert UYVY format to RGB data. > > To make preview path work correctly, we need to set up YCC_SWAP > according to sensor output and convert them to UYVY. > > Signed-off-by: Josh Wu > --- > > drivers/media/platform/soc_camera/at

Re: [PATCH 1/5] media: atmel-isi: correct yuv swap according to different sensor outputs

2015-10-04 Thread Guennadi Liakhovetski
Hi Josh, On Tue, 22 Sep 2015, Josh Wu wrote: > we need to configure the YCC_SWAP bits in ISI_CFG2 according to current > sensor output and Atmel ISI output format. > > Current there are two cases Atmel ISI supported: > 1. Atmel ISI outputs YUYV format. > This case we need to setup YCC_SWA

[RFC] ADV7604: VGA support

2015-10-04 Thread Jean-Michel Hautbois
Hi, I had another look into the ADV7604 HW manual, and I understand that in automatic mode, there is 4 AIN_SEL values possible, determining the connection on AIN pins. Now, having a look at the current ADV76xx files, I can see that two pads are there : ADV7604_PAD_VGA_RGB and ADV7604_PAD_VGA_COMP.

drivers/media/dvb-core/dvbdev.h:157:18: error: too many arguments to function '__a'

2015-10-04 Thread kbuild test robot
Hi Kozlov, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 15ecf9a986e2678f5de36ead23b89235612fc03f commit: 52b1eaf4c59a3bbd07afbb4ab4f43418a807d02e [media] netup_unidvb: NetUP Universal DVB-S/S2/T/T2/C PCI-E card d

Re: Hauppauge WinTV-HVR2205 driver feedback

2015-10-04 Thread Steven Toth
> Seems the kzalloc(4 * 1048576, GFP_KERNEL) in saa7164-fw.c was failing.. > kept getting: kernel: modprobe: page allocation failure: order:10, > mode:0x10c0d0 I don't think I've ever seen or heard of that in the entire history of the driver. Are you running on traditional x86/x86 hardware, or

Re: [PATCH 15/15] dma: remove external references to dma_supported

2015-10-04 Thread Greg KH
On Sat, Oct 03, 2015 at 05:19:39PM +0200, Christoph Hellwig wrote: > Signed-off-by: Christoph Hellwig > --- > Documentation/DMA-API.txt | 13 - > drivers/usb/host/ehci-hcd.c | 2 +- > drivers/usb/host/fotg210-hcd.c | 2 +- > drivers/usb/host/fusbh200-hcd.c | 2 +- > driv

v4l2 api: supported resolution negotiation

2015-10-04 Thread Matwey V. Kornilov
Hello, I learned from V2L2 API how to detect all supported formats using VIDIOC_ENUM_FMT. When I perform VIDIOC_S_FMT I don't know how to fill fmt.pix.width and fmt.pix.height, since I know only format. How should I negotiate device resolution? Could you point me? -- To unsubscribe from this list