On Wednesday, April 06, 2011 18:19:18 Guennadi Liakhovetski wrote:
On Tue, 5 Apr 2011, Hans Verkuil wrote:
On Tuesday, April 05, 2011 14:21:03 Laurent Pinchart wrote:
On Friday 01 April 2011 10:13:02 Guennadi Liakhovetski wrote:
[snip]
* I O C T L C O D E S F O R V I D
On Thu, 7 Apr 2011, Hans Verkuil wrote:
On Wednesday, April 06, 2011 18:19:18 Guennadi Liakhovetski wrote:
On Tue, 5 Apr 2011, Hans Verkuil wrote:
On Tuesday, April 05, 2011 14:21:03 Laurent Pinchart wrote:
On Friday 01 April 2011 10:13:02 Guennadi Liakhovetski wrote:
[snip]
On Thu, 7 Apr 2011, Hans Verkuil wrote:
On Wednesday, April 06, 2011 18:19:18 Guennadi Liakhovetski wrote:
On Tue, 5 Apr 2011, Hans Verkuil wrote:
On Tuesday, April 05, 2011 14:21:03 Laurent Pinchart wrote:
On Friday 01 April 2011 10:13:02 Guennadi Liakhovetski wrote:
[snip]
On Wed, Apr 06, 2011 at 11:38:54AM -0700, Greg KH wrote:
On Wed, Apr 06, 2011 at 11:25:57AM -0700, Andres Salomon wrote:
We've been faced with the problem of being able to pass both MFD
related data and a platform_data pointer to some of those drivers.
Squeezing the MFD bits in the
Hi,
On Wed, Apr 06, 2011 at 03:09:00PM -0700, Greg KH wrote:
On Wed, Apr 06, 2011 at 09:59:02PM +0300, Felipe Balbi wrote:
Hi,
On Wed, Apr 06, 2011 at 08:47:34PM +0200, Samuel Ortiz wrote:
What is a MFD cell pointer and why is it needed in struct device?
An MFD cell is an MFD
Since commit
379fa5d ([media] V4L: mx3_camera: convert to videobuf2)
mx3_camera uses videobuf2, but that commit didn't upgrade the select
resulting in the following build failure:
drivers/built-in.o: In function `mx3_camera_init_videobuf':
clkdev.c:(.text+0x86580):
On Thu, 7 Apr 2011, Hans Verkuil wrote:
On Thu, 7 Apr 2011, Hans Verkuil wrote:
On Wednesday, April 06, 2011 18:19:18 Guennadi Liakhovetski wrote:
On Tue, 5 Apr 2011, Hans Verkuil wrote:
On Tuesday, April 05, 2011 14:21:03 Laurent Pinchart wrote:
On Friday 01 April 2011
On Thursday, April 07, 2011 10:53:32 Guennadi Liakhovetski wrote:
On Thu, 7 Apr 2011, Hans Verkuil wrote:
On Thu, 7 Apr 2011, Hans Verkuil wrote:
On Wednesday, April 06, 2011 18:19:18 Guennadi Liakhovetski wrote:
On Tue, 5 Apr 2011, Hans Verkuil wrote:
On Tuesday, April
Hi Hans,
On Thursday 07 April 2011 09:50:13 Hans Verkuil wrote:
On Thu, 7 Apr 2011, Hans Verkuil wrote:
[snip]
Regarding DESTROY_BUFS: perhaps we should just skip this for now and wait
for the first use-case. That way we don't need to care about holes. I
don't like artificial
Hi Hans,
On Thursday 07 April 2011 09:50:13 Hans Verkuil wrote:
On Thu, 7 Apr 2011, Hans Verkuil wrote:
[snip]
Regarding DESTROY_BUFS: perhaps we should just skip this for now and
wait
for the first use-case. That way we don't need to care about holes. I
don't like artificial
On Wed, 6 Apr 2011, Teresa Gámez wrote:
Measurements show that the setup of the pixel clock is not correct.
The 'Invert Pixel Clock' bit has to be set to 1 for falling edge
and not for rising.
Doesn't seem correct to me. The mt9v022 datasheet says:
quote
Invert pixel clock. When set,
On Wed, 6 Apr 2011, Teresa Gámez wrote:
This camera driver supports only rising edge, which is the default
setting of the device. The function mt9m111_setup_pixfmt() overwrites
this setting. So the driver actually uses falling edge.
This patch corrects that.
Ok, this does indeed look like a
Hi Laurent
On Fri, 1 Apr 2011, Laurent Pinchart wrote:
[snip]
- Cache management (ISP and DSS)
Cache needs to be synchronized between userspace applications, kernel space
and hardware. Synchronizing the cache is an expensive operation and should be
avoided when possible. Userspace
Hi Manjunath,
On Saturday 02 April 2011 11:40:49 Manjunath Hadli wrote:
This is the display driver for Texas Instruments's DM644X family
SoC. This patch contains the main implementation of the driver with the
V4L2 interface. The driver implements the streaming model with
support for both
Hello Guennadi,
Sorry for the first mail...
The datasheet also says (see table 3):
quote
Pixel clock out. DOUT is valid on rising edge of this
clock.
/quote
There is a difference between DOUT beeing vaild and DOUT beeing set up.
So does SOCAM_PCLK_SAMPLE_RISING mean that the data is valid at
Hello Teresa
On Thu, 7 Apr 2011, Teresa Gamez wrote:
Hello Guennadi,
the datasheet also says (see table 3):
quote
Pixel clock out. DOUT is valid on rising edge of this
clock.
/quote
There is a difference between DOUT beeing vaild and DOUT beeing set up.
So does
On Thu, Apr 07, 2011 at 03:40:23PM +0200, Samuel Ortiz wrote:
Hi Felipe,
On Wed, Apr 06, 2011 at 09:59:02PM +0300, Felipe Balbi wrote:
Hi,
On Wed, Apr 06, 2011 at 08:47:34PM +0200, Samuel Ortiz wrote:
What is a MFD cell pointer and why is it needed in struct device?
An MFD
On Thu, Apr 07, 2011 at 07:35:15AM -0700, Grant Likely wrote:
Below is a patch for the Xilinx SPI example. Although this would fix the
issue, we'd still have to do that on device per device basis. I had a
similar
solution where MFD drivers would set a flag for sub drivers that don't need
Add a 10 bits per pixel greyscale format in a bit-packed array representation,
naming it Y10B. Such pixel format is supplied for instance by the Kinect
sensor device.
Cc: Steven Toth st...@kernellabs.com
Signed-off-by: Antonio Ospite osp...@studenti.unina.it
---
Hi,
This patchset adds support for using the Kinect[1] sensor device as a
regular Webcam or as a IR camera.
[1] http://en.wikipedia.org/wiki/Kinect
The first patch adds a new Y10B pixelformat used to expose the raw IR
data the sensor can provide, the second patch adds a gspca subdriver for
The Kinect sensor is a device used by Microsoft for its Kinect project,
which is a system for controller-less Human-Computer interaction
targeted for Xbox 360.
In the Kinect device, RGBD data is captured from two distinct sensors: a
regular RGB sensor and a monochrome sensor which, with the aid
Indent wrapped lines with tabs, just like it is done for the other
functions in the same file.
Signed-off-by: Antonio Ospite osp...@studenti.unina.it
---
lib/libv4lconvert/libv4lconvert-priv.h |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git
Y10B is a 10 bits per pixel greyscale format in a bit-packed array
representation. Such pixel format is supplied for instance by the Kinect
sensor device.
Signed-off-by: Antonio Ospite osp...@studenti.unina.it
---
Hi,
this is a very first attempt about supporting Y10B in libv4lconvert, the
Hi Mauro
The following changes since commit 6221f222c0ebf1acdf7abcf927178f40e1a65e2a:
Linux 2.6.39-rc2 (2011-04-05 18:30:43 -0700)
are available in the git repository at:
git://linuxtv.org/gliakhovetski/v4l-dvb.git 2.6.39-rc1-fixes
Guennadi Liakhovetski (8):
V4L: fix videobuf2 to
On Mon, Apr 4, 2011 at 8:04 PM, Grant Likely grant.lik...@secretlab.ca wrote:
On Mon, Apr 04, 2011 at 12:03:15PM +0200, Samuel Ortiz wrote:
diff --git a/include/linux/platform_device.h
b/include/linux/platform_device.h
index d96db98..734d254 100644
--- a/include/linux/platform_device.h
+++
ehem, let's try again (forgot one more patch):
The following changes since commit 6221f222c0ebf1acdf7abcf927178f40e1a65e2a:
Linux 2.6.39-rc2 (2011-04-05 18:30:43 -0700)
are available in the git repository at:
git://linuxtv.org/gliakhovetski/v4l-dvb.git 2.6.39-rc1-fixes
Guennadi
Hello,
the following is a v4l2 subdev driver for MIPI-CSI2 receivers
available in S5PVx10 and EXYNOS4 SoCs. The MIPI-CSIS module
(MIPI CSI Slave) works closely with the FIMC IP, i.e. it is its
frontend for the MIPI CSI serial bus.
Other than that the following patch set moves the s5p-fimc
s5p-fimc now also implements a camera capture video node so move
it under the Video capture devices Kconfig menu. Also update
the entry to reflect the driver's coverage of EXYNOS4 SoCs.
Signed-off-by: Sylwester Nawrocki s.nawro...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
Add V4L2_MBUS_FMT_JPEG_1X8 format and the corresponding Docbook
documentation.
Signed-off-by: Sylwester Nawrocki s.nawro...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
Acked-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
---
Add the subdev driver for the MIPI CSIS units available in
S5P and Exynos4 SoC series. This driver supports both CSIS0
and CSIS1 MIPI-CSI2 receivers. The corresponding PHYs are
controlled through the platform data callback. The driver
requires Runtime PM to be enabled for proper operation.
Hi all,
I have a question about the following videobuf_dma_contig_user_get()
fix to 2.6.33:
This message is generated daily by a cron job that builds v4l-dvb for
the kernels and architectures in the list below.
Results of the daily build of v4l-dvb:
date:Thu Apr 7 19:00:20 CEST 2011
git hash:d9954d8547181f9a6a23f835cc1413732700b785
gcc version: i686-linux-gcc (GCC)
On Thu, Apr 07, 2011 at 05:03:23PM +0200, Samuel Ortiz wrote:
On Thu, Apr 07, 2011 at 07:35:15AM -0700, Grant Likely wrote:
Below is a patch for the Xilinx SPI example. Although this would fix the
issue, we'd still have to do that on device per device basis. I had a
similar
solution
We leak the memory allocated to 'fw' (the firmware) when the variable goes
out of scope.
Fix the leak by calling release_firmware(fw) before 'fw' goes out of
scope.
Signed-off-by: Jesper Juhl j...@chaosbits.net
---
cx23885-cards.c |1 +
1 file changed, 1 insertion(+)
compile tested
If the second memory allocation in dib9000_attach() fails, we'll leak the
memory allocated by the first.
Signed-off-by: Jesper Juhl j...@chaosbits.net
---
dib9000.c |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
compile tested only...
diff --git
This message is generated daily by a cron job that builds v4l-dvb for
the kernels and architectures in the list below.
Results of the daily build of v4l-dvb:
date:Thu Apr 7 20:09:52 CEST 2011
git hash:d9954d8547181f9a6a23f835cc1413732700b785
gcc version: i686-linux-gcc (GCC)
Don't leak 'fw' in
drivers/media/dvb/dvb-usb/lmedm04.c::lme_firmware_switch() by failing to
call release_firmware().
Signed-off-by: Jesper Juhl j...@chaosbits.net
---
lmedm04.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
compile tested only
diff --git
On Thu, 2011-04-07 at 21:46 +0200, Jesper Juhl wrote:
Don't leak 'fw' in
drivers/media/dvb/dvb-usb/lmedm04.c::lme_firmware_switch() by failing to
call release_firmware().
Signed-off-by: Jesper Juhl j...@chaosbits.net
---
lmedm04.c |2 +-
1 file changed, 1 insertion(+), 1
On Thu, 7 Apr 2011, Malcolm Priestley wrote:
On Thu, 2011-04-07 at 21:46 +0200, Jesper Juhl wrote:
Don't leak 'fw' in
drivers/media/dvb/dvb-usb/lmedm04.c::lme_firmware_switch() by failing to
call release_firmware().
Signed-off-by: Jesper Juhl j...@chaosbits.net
---
lmedm04.c |
Hello Steve at all,
Here it is, feel free to test:
http://git.linuxtv.org/anttip/media_tree.git?a=shortlog;h=refs/heads/pctv_290e
Now I *need* help for adding proper DVB-T2 support for the API. I added
fe_delivery_system_t SYS_DVBT2, but there is no app knowing that yet.
Since there is also
I wrote a scan program that steps through all the frequencies in a given
range and tries to tune them in a for loop. This is my first C program so be
nice,
http://chinesebob.net/dvb/blindscan-s2/blindscan-s2-201104070153.tgz
I'm using it with my Prof 7500, which uses the dvb-usb-dw2102 and
41 matches
Mail list logo
