Hello Mauro Carvalho Chehab,
This is a semi-automatic email about new static checker warnings.
The patch 4a83b0115066: [media] tm6000: rewrite IR support from Nov
29, 2011, leads to the following Smatch complaint:
drivers/media/video/tm6000/tm6000-input.c +327 __tm6000_ir_int_start()
The function v4l2_device_register() is called too late in vpif_probe().
This meant that vpif_obj.v4l2_dev is accessed before it is initialized
which caused a crash.
This used to work in the past, but video_register_device() is now actually
using the v4l2_dev pointer.
Note that vpif_display.c
On Tue, Dec 13, 2011 at 01:40, Laurent Pinchart
laurent.pinch...@ideasonboard.com wrote:
I think you also want to do something with red, green, blue, transp when
entering FOURCC mode, at least setting them to zero or maybe even requiring
that they are zero to enter FOURCC mode (as additional
remove inclusion of header files from vpif.h and vpif_dispaly.c
and add appropriate header file for building.
Signed-off-by: Manjunath Hadli manjunath.ha...@ti.com
Cc: Mauro Carvalho Chehab mche...@infradead.org
Cc: LMML linux-media@vger.kernel.org
---
drivers/media/video/davinci/vpif.h
Hi Geert,
On Tuesday 13 December 2011 11:47:02 Geert Uytterhoeven wrote:
On Tue, Dec 13, 2011 at 01:40, Laurent Pinchart wrote:
I think you also want to do something with red, green, blue, transp when
entering FOURCC mode, at least setting them to zero or maybe even
requiring that they are
On Thursday 08 December 2011 10:30:58 Sylwester Nawrocki wrote:
On 11/29/2011 07:58 PM, Laurent Pinchart wrote:
On Tuesday 29 November 2011 19:30:25 Hans Verkuil wrote:
On Tuesday, November 29, 2011 19:10:39 Laurent Pinchart wrote:
On Tuesday 29 November 2011 17:40:10 Sylwester Nawrocki
Hans,
On Tue, Dec 13, 2011 at 15:14:42, Hans Verkuil wrote:
The function v4l2_device_register() is called too late in vpif_probe().
This meant that vpif_obj.v4l2_dev is accessed before it is initialized which
caused a crash.
This used to work in the past, but video_register_device() is now
Hi everybody,
fbdev: Add FOURCC-based format configuration API
Here's the fifth version of the fbdev FOURCC-based format configuration API.
Compared to the fourth version,
- fb_set_var() now checks that the red, green, blue and transp fields are all
set to 0 when using the FOURCC-based API and
This API will be used to support YUV frame buffer formats in a standard
way.
Last but not least, create a much needed fbdev API documentation and
document the format setting APIs.
Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
---
Documentation/fb/api.txt | 306
Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
---
arch/arm/mach-shmobile/board-ag5evm.c |2 +-
arch/arm/mach-shmobile/board-ap4evb.c |4 +-
arch/arm/mach-shmobile/board-mackerel.c |4 +-
arch/sh/boards/mach-ap325rxa/setup.c|2 +-
(I've been away for the past two weeks, so I'm only now catching up)
On Thursday 08 December 2011 22:44:08 Daniel Vetter wrote:
On Wed, Dec 7, 2011 at 14:40, Arnd Bergmann a...@arndb.de wrote:
On Wednesday 07 December 2011, Semwal, Sumit wrote:
Thanks for the excellent discussion - it
Marko Ristola, on 13.12.2011 08:31:
Here is a patch that went into Linus GIT this year.
It reduces the number of DMA transfer interrupts into one third.
Linus released 2.6.38.8 doesn't seem to have this patch yet.
Thank you very much. I did see this patch mentioned in my quest for more
Yan Seiner wrote:
Yan Seiner wrote:
Andy Walls wrote:
800 MB for 320x420 frames? It sounds like your app has gooned its
requested buffer size.
That's an understatement. :-)
wild speculation
This might be due to endianess differences between MIPS abd x86 and
your app only being written
On Monday 12 December 2011, Robert Morell wrote:
Doing a buffer sharing with something that is not GPL is not fun, as, if any
issue rises there, it would be impossible to discover if the problem is
either
at the closed-source driver or at the open source one. At the time I was
using
On 10/14/2011 08:32 PM, Oliver Neukum wrote:
Am Mittwoch, 5. Oktober 2011, 10:16:06 schrieb Oliver Neukum:
Am Mittwoch, 5. Oktober 2011, 08:19:10 schrieb Antti Palosaari:
On 10/05/2011 09:15 AM, Oliver Neukum wrote:
But, Greg, Antti makes a very valid point here. The generic code assumes
(sorry for breaking the threading, the reply came faster than my
subscription to the list :)
From Ninja Ninja15@xx,
Hi, I noticed some SMP problems with the mantis driver as well (see my
post Mantis CAM not SMP safe / Activating CAM on Technisat Skystar HD2
(DVB-S2)). One workaround for me
Anyhow, I would like now ask how to proceed. Should I export four new
functions as replacement of those leaving old functionality as
currently. Or should I change existing ones like adding new pointer for
struct usb_serial and use it instead of struct usb_interface when not NULL.
I think I
13.12.2011 08:31, Marko Ristola:
Hi
Here is a patch that went into Linus GIT this year.
It reduces the number of DMA transfer interrupts into one third.
Linus released 2.6.38.8 doesn't seem to have this patch yet
Good news, combining this patch with IRQ management fixes the problem for
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 Dec 13 19:00:14 CET 2011
git hash:bcc072756e4467dc30e502a311b1c3adec96a0e4
gcc version: i686-linux-gcc
Forgot to CC the list, here it goes...
Hi Jef,
Am 13.12.2011 11:32, schrieb Jean-Francois Moine:
So, I added controls to modify these registers in the version 2.14.5
I've just uploaded.
The values may be modified by programs as 'v4l2ucp' (control only),
'vlc' or my program 'svv'. Note
Am 12.12.2011 12:08, schrieb Marko Ristola:
On 12/10/2011 01:57 AM, Ninja wrote:
Hi,
has anyone an idea how the SMP problems could be fixed?
You could turn on Mantis Kernel module's debug messages.
It could tell you the emitted interrupts.
One risky thing with the Interrupt handler code is
13.12.2011 20:11, Vidar Tyldum kirjoitti:
13.12.2011 08:31, Marko Ristola:
Hi
Here is a patch that went into Linus GIT this year.
It reduces the number of DMA transfer interrupts into one third.
Linus released 2.6.38.8 doesn't seem to have this patch yet
Good news, combining this patch with
The MT9M032 is a parallel 1.6MP sensor from Micron controlled through I2C.
The driver creates a V4L2 subdevice. It currently supports cropping, gain,
exposure and v/h flipping controls in monochrome mode with an
external pixel clock.
Signed-off-by: Martin Hostettler mar...@neutronstar.dyndns.org
Adds board support for an MT9M032 based camera to omap3evm.
Signed-off-by: Martin Hostettler mar...@neutronstar.dyndns.org
---
arch/arm/mach-omap2/Makefile|3 +-
arch/arm/mach-omap2/board-omap3evm-camera.c | 155 +++
Dear Martin Hostettler,
The MT9M032 is a parallel 1.6MP sensor from Micron controlled through I2C.
The driver creates a V4L2 subdevice. It currently supports cropping, gain,
exposure and v/h flipping controls in monochrome mode with an
external pixel clock.
Signed-off-by: Martin
dprintk() dereferences ir. I'm not sure why gcc doesn't complain
about this.
Signed-off-by: Dan Carpenter dan.carpen...@oracle.com
diff --git a/drivers/media/video/tm6000/tm6000-input.c
b/drivers/media/video/tm6000/tm6000-input.c
index 8d92527..7844607 100644
---
On Wed, Dec 14, 2011 at 02:55:31AM +0100, Marek Vasut wrote:
Dear Martin Hostettler,
The MT9M032 is a parallel 1.6MP sensor from Micron controlled through I2C.
The driver creates a V4L2 subdevice. It currently supports cropping, gain,
exposure and v/h flipping controls in monochrome
27 matches
Mail list logo
