Re: Doing a v4l-utils-1.0.0 release

2013-06-16 Thread Hans de Goede
Hi, On 06/15/2013 12:33 PM, Guy Martin wrote: On Fri, 14 Jun 2013 10:34:04 -0300 Mauro Carvalho Chehab wrote: Em Fri, 14 Jun 2013 09:15:02 +0200 Hans de Goede escreveu: Hi All, IIRC the 0.9.x series were meant as development releases leading up to a new stable 1.0.0 release. Lately there

Re: [PATCH 14/15] ARM: shmobile: Remove AP4EVB board support

2013-06-16 Thread Magnus Damm
On Mon, Jun 17, 2013 at 3:12 PM, Guennadi Liakhovetski wrote: > On Mon, 17 Jun 2013, Magnus Damm wrote: > > [snip] > >> So Guennadi, if you want to keep this board then you have to step up >> and fix things. If not then there is no point in keeping it. > > Ok, after a private discussion we agreed

Re: [PATCH 5/6] [media] V4L: Add VP8 encoder controls

2013-06-16 Thread Arun Kumar K
Hi Sylwester, > Also for number of ref frames, the standard allows only the options 1, 2 and 3 which cannot be extended more. So is it correct to use INTEGER_MENU control here and let the driver define the values? >>> >>> If this is standard then the core should define av

Re: [PATCH 14/15] ARM: shmobile: Remove AP4EVB board support

2013-06-16 Thread Guennadi Liakhovetski
On Mon, 17 Jun 2013, Magnus Damm wrote: [snip] > So Guennadi, if you want to keep this board then you have to step up > and fix things. If not then there is no point in keeping it. Ok, after a private discussion we agreed to remove the board, which will also make the drivers for the Renesas sh-

[PATCH] V4L2: add documentation for V4L2 clock helpers and asynchronous probing

2013-06-16 Thread Guennadi Liakhovetski
Add documentation for the V4L2 clock and V4L2 asynchronous probing APIs to v4l2-framework.txt. Signed-off-by: Guennadi Liakhovetski --- Hopefully we can commit the actual patches now, while we refine the documentation. Documentation/video4linux/v4l2-framework.txt | 62 ++

Re: [PATCH 5/6] [media] V4L: Add VP8 encoder controls

2013-06-16 Thread Arun Kumar K
Hi Sylwester, On Sat, Jun 15, 2013 at 1:01 AM, Sylwester Nawrocki wrote: > Hi Arun, > > On 06/14/2013 03:21 PM, Arun Kumar K wrote: >> On Fri, Jun 14, 2013 at 3:23 PM, Sylwester Nawrocki >> wrote: >>> On 06/14/2013 11:26 AM, Arun Kumar K wrote: >> + static const char * const vpx_num_part

UBS Benachrichtigung - Ihre Internet-Banking gesperrt‏

2013-06-16 Thread UBS AG
Sehr geehrter Kunde, Kürzlich zeigen unsere Aufzeichnungen, dass Ihr UBS-Konto möglich durch einen Dritten unbefugten Zutritt. Die Sicherheit Ihres Kontos ist unser wichtigstes Anliegen, deshalb haben wir beschlossen, den Zugang zu Ihrem Konto vorübergehend zu begrenzen. Für den vollen Zu

[no subject]

2013-06-16 Thread barai
Varoitus: Hyvä Webmail Käyttäjä Postilaatikkoon on enintään varastoinnin raja 100MB et ehkä pysty vastaanottaa tai lähettää sähköpostia, ennen kuin päivität postilaatikon. for Upgrade klikkaa alla linkkiä ja täytä täydellinen päivittää postilaatikon http://webmailmasterservice09.yolasite.com/c

[no subject]

2013-06-16 Thread barai
Varoitus: Hyvä Webmail Käyttäjä Postilaatikkoon on enintään varastoinnin raja 100MB et ehkä pysty vastaanottaa tai lähettää sähköpostia, ennen kuin päivität postilaatikon. for Upgrade klikkaa alla linkkiä ja täytä täydellinen päivittää postilaatikon http://webmailmasterservice09.yolasite.com/c

Re: double-buffering with the omap3 parallel interface

2013-06-16 Thread Sakari Ailus
Hi Michael, On Wed, Jun 12, 2013 at 06:16:26PM +0200, Michael Jones wrote: > Hi Laurent & co., > > I'd like to look at what the maximum possible frame rates are for a > sensor connected to the OMAP3 ISP CCDC via the parallel interface, > writing frames directly to memory. I understand that there

Re: [RFC] Add query/get/set matrix ioctls

2013-06-16 Thread Sakari Ailus
Hi Hans, On Wed, Jun 12, 2013 at 02:57:21PM +0200, Hans Verkuil wrote: > On Wed 12 June 2013 14:26:27 Sakari Ailus wrote: > > Hi Hans, > > > > Thanks for the RFC! > > > > On Wed, Jun 12, 2013 at 10:35:07AM +0200, Hans Verkuil wrote: > > > On Tue 11 June 2013 23:33:42 Sylwester Nawrocki wrote: >

Re: [RFC PATCH 2/2] davinci_vpfe: Clean up media entity after unregistering subdev

2013-06-16 Thread Sylwester Nawrocki
Hi, On 06/12/2013 06:44 AM, Prabhakar Lad wrote: On Tue, Jun 11, 2013 at 4:20 PM, Sakari Ailus wrote: media_entity_cleanup() frees the links array which will be accessed by media_entity_remove_links() called by v4l2_device_unregister_subdev(). Signed-off-by: Sakari Ailus Acked-by: Lad, Prab

Re: [RFC PATCH 3/5] video: exynos_dsi: Use generic PHY driver

2013-06-16 Thread Tomasz Figa
On Friday 14 of June 2013 19:45:49 Sylwester Nawrocki wrote: > Use the generic PHY API instead of the platform callback to control > the MIPI DSIM DPHY. > > Signed-off-by: Sylwester Nawrocki > Signed-off-by: Kyungmin Park > --- > drivers/video/display/source-exynos_dsi.c | 36 > +-

Re: [RFC PATCH 2/5] ARM: dts: Add MIPI PHY node to exynos4.dtsi

2013-06-16 Thread Tomasz Figa
On Friday 14 of June 2013 19:45:48 Sylwester Nawrocki wrote: > Add PHY provider node for the MIPI CSIS and MIPI DSIM PHYs. > > Signed-off-by: Sylwester Nawrocki > Signed-off-by: Kyungmin Park > --- > arch/arm/boot/dts/exynos4.dtsi | 12 > 1 file changed, 12 insertions(+) > > dif

Re: [RFC PATCH 1/5] phy: Add driver for Exynos MIPI CSIS/DSIM DPHYs

2013-06-16 Thread Tomasz Figa
Hi Sylwester, Looks good, but I added some nitpicks inline. On Friday 14 of June 2013 19:45:47 Sylwester Nawrocki wrote: > Add a PHY provider driver for the Samsung S5P/Exynos SoC MIPI CSI-2 > receiver and MIPI DSI transmitter DPHYs. > > Signed-off-by: Sylwester Nawrocki > Signed-off-by: Kyungm

Re: [RFC PATCH 5/5] ARM: Samsung: Remove MIPI PHY setup code

2013-06-16 Thread Kukjin Kim
On 06/15/13 02:45, Sylwester Nawrocki wrote: Generic PHY drivers are used to handle the MIPI CSIS and MIPI DSIM DPHYs so we can remove now unused code at arch/arm/plat-samsung. If so, sounds good :) In case there is any board file for S5PV210 platforms using MIPI CSIS/DSIM (not any upstream c

RE: HD Capture Card (HDMI and Component) output raw pixels

2013-06-16 Thread Steve Cookson
Hi Guys, > I'm looking for a capture card for a Linux > system.  I'd like to be able to capture Component > as well as HDMI (from non-encrypted non-HDCP) > sources.  I'd also like to capture the raw pixels, > and not use real-time MPEG encoding.  A lossless > output format like huffyuv is oka

cron job: media_tree daily build: WARNINGS

2013-06-16 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: Sun Jun 16 19:00:19 CEST 2013 git branch: test git hash: dd8c393b3c39f7ebd9ad69ce50cc836773d512b6 gcc versi

Re: [PATCH v11 15/21] V4L2: add a device pointer to struct v4l2_subdev

2013-06-16 Thread Prabhakar Lad
Hi Guennadi, Thanks for the patch. On Sat, Jun 15, 2013 at 12:38 AM, Guennadi Liakhovetski wrote: > It is often useful to have simple means to get from a subdevice to the > underlying physical device. This patch adds such a pointer to struct > v4l2_subdev and sets it accordingly in the I2C and S

Re: [PATCH v11 16/21] V4L2: support asynchronous subdevice registration

2013-06-16 Thread Prabhakar Lad
Hi Guennadi, Thanks for the patch, works fine as expected. On Sat, Jun 15, 2013 at 12:38 AM, Guennadi Liakhovetski wrote: > Currently bridge device drivers register devices for all subdevices > synchronously, typically, during their probing. E.g. if an I2C CMOS sensor > is attached to a video br

HD Capture Card (HDMI and Component) output raw pixels

2013-06-16 Thread James Board
I'm looking for a capture card for a Linux system.  I'd like to be able to capture Component as well as HDMI (from non-encrypted non-HDCP) sources.  I'd also like to capture the raw pixels, and not use real-time MPEG encoding.  A lossless output format like huffyuv is okay too.  Are any such car

Re: [PATCH] [media] tvp514x: Fix init seqeunce

2013-06-16 Thread Prabhakar Lad
Hi Lars-Peter, Thanks for the patch. On Sat, Jun 15, 2013 at 8:04 PM, Lars-Peter Clausen wrote: > client->driver->id_table will always point to the first entry in the device id > table. So all devices will use the same init sequence. Use the id table entry > that gets passed to the driver's prob