Frank Schäfer writes:
> This patch series adds support for USB bulk transfers to the em28xx driver.
I tried these patches on my Raspberry Pi, 3.6.1 kernel, Nanostick 290e
options em28xx prefer_bulk=1 core_debug=1 usb_debug=1
options em28xx_dvb debug=1
[5.469510] em28xx: New device PCTV Sys
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:Tue Oct 30 19:00:22 CET 2012
git hash:8f7e91a31fb95c50880c76505b416630c0326d93
gcc version: i686-linux-gcc (GCC
On Tue, 30 Oct 2012 17:04:23 +0100
Javier Martin wrote:
> 4x gain ceiling is not enough to capture a decent image in conditions
> of total darkness and only a LED light source. Allow a maximum gain
> of 32x instead.
The initial number surely came from OmniVision and was never really
thought abou
Just to let you know that you don't have to take any actions: Last 3 spammers
have been reported and stopped.
Love
Jens
--
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://vger.kernel.org/m
Am 30.10.2012 15:08, schrieb Devin Heitmueller:
> On Tue, Oct 30, 2012 at 12:06 AM, Mauro Carvalho Chehab
> wrote:
>> Did a git bisect. The last patch where the bug doesn't occur is this
>> changeset:
>> em28xx: add module parameter for selection of the preferred USB
>> transfer type
>>
>
Am 30.10.2012 06:06, schrieb Mauro Carvalho Chehab:
> Did a git bisect. The last patch where the bug doesn't occur is this
> changeset:
> em28xx: add module parameter for selection of the preferred USB
> transfer type
>
> That means that this changeset broke it:
>
> em28xx: use comm
Hi Zhou,
On Tuesday 04 September 2012 16:20:38 Zhou Zhu wrote:
> Hi Laurent,
>
> Basically I agree that we need a common panel framework. I just have
> some questions:
> 1. I think we should add color format in videomode - if we use such
> common video mode structure shared across subsystems.
>
* Tony Lindgren [121026 11:02]:
> * Ohad Ben-Cohen [121026 02:56]:
> > Hi Laurent,
> >
> > On Fri, Oct 26, 2012 at 11:35 AM, Laurent Pinchart
> > wrote:
> > > That's on my to-do list, as well as porting the OMAP3 ISP driver to
> > > videobuf2,
> > > adding DT support, moving to the common cloc
Hi Jun,
I've finally been able to resume my work on the panel framework (I hope to
post a v2 at the end of the week).
On Thursday 23 August 2012 14:23:01 Jun Nie wrote:
> Hi Laurent,
> Do you plan to add an API to get and parse EDID to mode list?
An API to get the raw EDID data is likely ne
4x gain ceiling is not enough to capture a decent image in conditions
of total darkness and only a LED light source. Allow a maximum gain
of 32x instead.
This doesn't have any drawback since the image quality in 'normal'
light conditions is the same.
Signed-off-by: Javier Martin
---
drivers/med
On 30 October 2012 15:57, Guennadi Liakhovetski wrote:
> On Tue, 30 Oct 2012, javier Martin wrote:
>
>> Hi Guennadi, Fabio,
>>
>> On 30 October 2012 13:29, Guennadi Liakhovetski
>> wrote:
>> > On Tue, 30 Oct 2012, Fabio Estevam wrote:
>> >
>> >> Javier,
>> >>
>> >> On Tue, Oct 30, 2012 at 10:16
Default value should be 'debugging disabled'.
Signed-off-by: Javier Martin
---
drivers/media/platform/m2m-deinterlace.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/platform/m2m-deinterlace.c
b/drivers/media/platform/m2m-deinterlace.c
index 1107167..931d5
On Mon, 29 Oct 2012, Simon Farnsworth wrote:
> On Monday 29 October 2012 13:44:45 Mauro Carvalho Chehab wrote:
> > Thanks for digging into it and getting more data. Do you know if this change
> > it also needed with USB devices that do DMA (isoc and/or bulk)? Or the USB
> > core already handles th
Based on commit: e66131cee501ee720b7b58a4b87073b8fbaaaba6
Not testing videobuf_dvb_get_frontend output may cause OOPS if it return
NULL. This patch fixes this issue.
The semantic patch that found this issue is(http://coccinelle.lip6.fr/):
//
@@
identifier i,a,b;
statement S, S2;
@@
i = videobuf_
On Tue, 30 Oct 2012, javier Martin wrote:
> Hi Guennadi, Fabio,
>
> On 30 October 2012 13:29, Guennadi Liakhovetski wrote:
> > On Tue, 30 Oct 2012, Fabio Estevam wrote:
> >
> >> Javier,
> >>
> >> On Tue, Oct 30, 2012 at 10:16 AM, Javier Martin
> >> wrote:
> >> > i.MX25 support has been broken f
After removing i.mx25 support and buf_cleanup() callback,
buffer states are not used in the code any longer.
Signed-off-by: Javier Martin
---
drivers/media/platform/soc_camera/mx2_camera.c | 11 ---
1 file changed, 11 deletions(-)
diff --git a/drivers/media/platform/soc_camera/mx2_cam
All necessary tasks to end the streaming properly are
already implemented in mx2_stop_streaming() and nothing
remains to be done in this callback.
Furthermore, it only included debug messages so it can
be removed.
Signed-off-by: Javier Martin
---
drivers/media/platform/soc_camera/mx2_camera.c |
The CSI has some constraints regarding image with.
This patch makes sure those requirements are met
in try_fmt().
Signed-off-by: Javier Martin
---
drivers/media/platform/soc_camera/mx2_camera.c |6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/media/platform/soc
i.MX25 support has been broken for several releases
now and nobody seems to care about it.
Signed-off-by: Javier Martin
---
drivers/media/platform/soc_camera/Kconfig |7 +-
drivers/media/platform/soc_camera/mx2_camera.c | 405 ++--
2 files changed, 103 insertions(+)
Changes since v1:
- Remove i.MX25 support in the Kconfig file too in patch 1.
[PATCH v2 1/4] media: mx2_camera: Remove i.mx25 support.
[PATCH v2 2/4] media: mx2_camera: Add image size HW limits.
[PATCH v2 3/4] media: mx2_camera: Remove 'buf_cleanup' callback.
[PATCH v2 4/4] media: mx2_camera: Rem
Typical video devices like camera sensors require an external clock source.
Many such devices cannot even access their hardware registers without a
running clock. These clock sources should be controlled by their consumers.
This should be performed, using the generic clock framework. Unfortunately
Hi Guennadi, Fabio,
On 30 October 2012 13:29, Guennadi Liakhovetski wrote:
> On Tue, 30 Oct 2012, Fabio Estevam wrote:
>
>> Javier,
>>
>> On Tue, Oct 30, 2012 at 10:16 AM, Javier Martin
>> wrote:
>> > i.MX25 support has been broken for several releases
>> > now and nobody seems to care about it.
Em Tue, 30 Oct 2012 09:08:15 -0400
Devin Heitmueller escreveu:
> On Tue, Oct 30, 2012 at 12:06 AM, Mauro Carvalho Chehab
> wrote:
> > Did a git bisect. The last patch where the bug doesn't occur is this
> > changeset:
> > em28xx: add module parameter for selection of the preferred USB
>
From: Wei Yongjun
The pattern E == C1 && E == C2 is always false. This patch
fix this according to the assumption that && should be ||.
dpatch engine is used to auto generate this patch.
(https://github.com/weiyj/dpatch)
Signed-off-by: Wei Yongjun
---
drivers/media/platform/davinci/vpif_displ
From: Wei Yongjun
The pattern E == C1 && E == C2 is always false. This patch
fix this according to the assumption that && should be ||.
dpatch engine is used to auto generate this patch.
(https://github.com/weiyj/dpatch)
Signed-off-by: Wei Yongjun
---
drivers/media/platform/davinci/vpif_captu
From: Wei Yongjun
The pattern E == C1 && E == C2 is always false. This patch
fix this according to the assumption that && should be ||.
dpatch engine is used to auto generate this patch.
(https://github.com/weiyj/dpatch)
Signed-off-by: Wei Yongjun
---
drivers/media/platform/davinci/vpif_captu
On Tue, Oct 30, 2012 at 12:06 AM, Mauro Carvalho Chehab
wrote:
> Did a git bisect. The last patch where the bug doesn't occur is this
> changeset:
> em28xx: add module parameter for selection of the preferred USB
> transfer type
>
> That means that this changeset broke it:
>
> em2
On Tue, 30 Oct 2012, Fabio Estevam wrote:
> Javier,
>
> On Tue, Oct 30, 2012 at 10:16 AM, Javier Martin
> wrote:
> > i.MX25 support has been broken for several releases
> > now and nobody seems to care about it.
>
> I will work on fixing camera support for mx25. Please do not remove its
> supp
Javier,
On Tue, Oct 30, 2012 at 10:16 AM, Javier Martin
wrote:
> i.MX25 support has been broken for several releases
> now and nobody seems to care about it.
I will work on fixing camera support for mx25. Please do not remove its support.
Thanks,
Fabio Estevam
--
To unsubscribe from this list:
After removing i.mx25 support and buf_cleanup() callback,
buffer states are not used in the code any longer.
Signed-off-by: Javier Martin
---
drivers/media/platform/soc_camera/mx2_camera.c | 11 ---
1 file changed, 11 deletions(-)
diff --git a/drivers/media/platform/soc_camera/mx2_cam
All necessary tasks to end the streaming properly are
already implemented in mx2_stop_streaming() and nothing
remains to be done in this callback.
Furthermore, it only included debug messages so it can
be removed.
Signed-off-by: Javier Martin
---
drivers/media/platform/soc_camera/mx2_camera.c |
The CSI has some constraints regarding image with.
This patch makes sure those requirements are met
in try_fmt().
Signed-off-by: Javier Martin
---
drivers/media/platform/soc_camera/mx2_camera.c |6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/media/platform/soc
i.MX25 support has been broken for several releases
now and nobody seems to care about it.
Signed-off-by: Javier Martin
---
drivers/media/platform/soc_camera/mx2_camera.c | 405 ++--
1 file changed, 100 insertions(+), 305 deletions(-)
diff --git a/drivers/media/platform/soc
[PATCH 1/4] media: mx2_camera: Remove i.mx25 support.
[PATCH 2/4] media: mx2_camera: Add image size HW limits.
[PATCH 3/4] media: mx2_camera: Remove 'buf_cleanup' callback.
[PATCH 4/4] media: mx2_camera: Remove buffer states.
--
To unsubscribe from this list: send the line "unsubscribe linux-media"
During the clock conversion for mx27 the "per4_gate" clock was missed to get
registered as a dependency of mx2-camera driver.
In the old mx27 clock driver we used to have:
DEFINE_CLOCK1(csi_clk, 0, NULL, 0, parent, &csi_clk1, &per4_clk);
,so does the same in the new clock driver
Signed-off-by:
Since mx27 transitioned to the commmon clock framework in 3.5, the correct way
to acquire the csi clock is to get csi_ahb and csi_per clocks separately.
By not doing so the camera sensor does not probe correctly:
soc-camera-pdrv soc-camera-pdrv.0: Probing soc-camera-pdrv.0
mx2-camera mx2-camera.0
On 29-10-12 02:09, Antti Palosaari wrote:
su 28.10.2012 22:07 Mauro Carvalho Chehab kirjoitti:
Em Mon, 22 Oct 2012 10:17:26 +0200
Oliver Schinagl escreveu:
diff --git a/drivers/media/tuners/fc2580.c
b/drivers/media/tuners/fc2580.c
index aff39ae..102d942 100644
I found a fellow Asus U3100+ use
diff --git a/drivers/media/tuners/fc2580.c b/drivers/media/tuners/fc2580.c
index aff39ae..102d942 100644
I found a fellow Asus U3100+ user (mentioned him before with the
firmware issue) that even when using the latest firmware, still see's
0xff as the chipID.
Signed-off-by: Oliver Schinagl
Hi Fabio
Sorry for a late review, but
On Tue, 9 Oct 2012, Fabio Estevam wrote:
> Since mx27 transitioned to the commmon clock framework in 3.5, the correct way
> to acquire the csi clock is to get csi_ahb and csi_per clocks separately.
>
> By not doing so the camera sensor does not probe correc
39 matches
Mail list logo
