Re: [PATCH 3/3] I don`t know for what, but there`s dublicate item.

On Wed, May 30, 2012 at 05:05:47PM -0300, Ezequiel Garcia wrote: > On Wed, May 30, 2012 at 4:43 PM, Ezequiel Garcia > wrote: > > But the subject is *very* wrong. You should set it to something like: > > "[bt8xx] Remove duplicated pixel format entry". > > > Sorry this should be, "[PATCH]

Re: OMAP 3 ISP

Hi Laurent, For me even ISP revision print log is not displaying and moreover when I am checking the interrupts using cat /proc/interrupts Only iommu interrupt is showing for interrupt line 24 Seems ISP probe function is not at all getting called Right now board is not available for me so that I

Re: [PATCH] [media] em28xx: Show a warning if the board does not support remote controls

Hi, > When sending new versions of a patch you should mark them as [PATCH > v2], [PATCH v3], etc in the subject. > This way maintainers can follow the patch evolution. Thanks for the hint. I just noticed that I spammed the patchwork system with my patch-mess too. I should probably also always rep

Re: [PATCH] [media] em28xx: Show a warning if the board does not support remote controls

Hi Martin, On Wed, May 30, 2012 at 4:50 PM, Martin Blumenstingl wrote: > Hello, > > thanks to Fabio and Ezequiel for the suggestions. > This is the latest version of my patch. > > It basically shows this when connecting my stick > (of course only if I remove my other patch): > [ 1597.796028] em28

Re: [PATCH 3/3] I don`t know for what, but there`s dublicate item.

On Wed, May 30, 2012 at 4:43 PM, Ezequiel Garcia wrote: > But the subject is *very* wrong. You should set it to something like: > "[bt8xx] Remove duplicated pixel format entry". Sorry this should be, "[PATCH] bt8xx: Remove duplicated pixel format entry". -- To unsubscribe from this list:

Re: [PATCH] [media] em28xx: Show a warning if the board does not support remote controls

Hello, thanks to Fabio and Ezequiel for the suggestions. This is the latest version of my patch. It basically shows this when connecting my stick (of course only if I remove my other patch): [ 1597.796028] em28xx #0: chip ID is em2884 [ 1597.849321] em28xx #0: Identified as Terratec Cinergy HTC S

[PATCH] [media] em28xx: Show a warning if the board does not support remote controls

This simply shows a little warning if the board does not have remote control support. This should make it easier for users to see if they have misconfigured their system or if the driver simply does not have rc-support for their card (yet). Signed-off-by: Martin Blumenstingl --- drivers/media/vi

Re: [PATCH 3/3] I don`t know for what, but there`s dublicate item.

Hi, On Sat, May 26, 2012 at 4:18 PM, Volokh Konstantin wrote: > Signed-off-by: Volokh Konstantin > --- >  drivers/media/video/bt8xx/bttv-driver.c |    6 -- >  1 files changed, 0 insertions(+), 6 deletions(-) > > diff --git a/drivers/media/video/bt8xx/bttv-driver.c > b/drivers/media/video/bt

cron job: media_tree daily build: WARNINGS

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:Wed May 30 19:00:21 CEST 2012 git hash:5472d3f17845c4398c6a510b46855820920c2181 gcc version: i686-linux-gcc (GC

Re: [PATCHv6 00/13] Integration of videobuf2 with dmabuf

On Tue, May 29, 2012 at 6:25 AM, Laurent Pinchart wrote: > Hi Tomasz, Hi Tomasz, Laurent, Mauro, > > On Wednesday 23 May 2012 14:10:14 Tomasz Stanislawski wrote: >> Hello everyone, >> This patchset adds support for DMABUF [2] importing to V4L2 stack. >> The support for DMABUF exporting was moved t

[v4l-utils] Add configure option to allow qv4l2 disable

This patch could ease the job of a few people, by providing an option they actually need. OpenWRT [1] and Openembedded [2] are already disabling qv4l2 by applying ugly patches. [1] https://dev.openwrt.org/browser/packages/libs/libv4l/patches/004-disable-qv4l2.patch [2] http://patches.openembed

Re: [PATCH] [media] em28xx: Show a warning if the board does not support remote controls

Hi Martin, On Tue, May 29, 2012 at 7:24 PM, Martin Blumenstingl wrote: > What would you use as the first (dev) argument for dev_*? > I simply tried using the USB-device (&dev->udev->dev) there, and I > think it's less > descriptive if one removes the driver name and the board number: > usb 1-1.2:

Re: Preliminary proposal, new APIs for HDMI and DVI control in v4l2

On Wed 30 May 2012 13:13:27 Martin Bugge (marbugge) wrote: > Hi Soby > > On 05/27/2012 07:30 PM, Soby Mathew wrote: > > Martin Bugge (marbugge cisco.com> writes: > > > >> > >> This is a preliminary proposal for an extension to the v4l2 api. > >> To be discussed at the V4L2 'brainstorming' meeti

Re: Preliminary proposal, new APIs for HDMI and DVI control in v4l2

Hi Soby On 05/27/2012 07:30 PM, Soby Mathew wrote: Martin Bugge (marbugge cisco.com> writes: This is a preliminary proposal for an extension to the v4l2 api. To be discussed at the V4L2 'brainstorming' meeting in Warsaw, March 2011 Purpose: Provide basic controls for HDMI and DVI devices.

Re: [PATCH] cxd2820r: Fix an incorrect modulation type bitmask.

On 30.05.2012 12:28, Janne Huttunen wrote: Fix an incorrect modulation type bitmask. This allows QAM256 also to be correctly reported. Signed-off-by: Janne Huttunen Acked-by: Antti Palosaari Thank you! t. Antti -- http://palosaari.fi/ -- To unsubscribe from this list: send the line "unsub

[PATCH] cxd2820r: Fix an incorrect modulation type bitmask.

Fix an incorrect modulation type bitmask. This allows QAM256 also to be correctly reported. Signed-off-by: Janne Huttunen --- drivers/media/dvb/frontends/cxd2820r_c.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/media/dvb/frontends/cxd2820r_c.c b/drivers/media