When digitizing composite video from a analog videotape source using the
TVP5150's first composite input channel, the captured stream exhibits
tearing and synchronization problems[1].
It turns out that commit c0477ad9feca01bd8eff95d7482c33753d05c700 caused
"TV mode" (as opposed to "VCR mode" o
On Fri, Oct 8, 2010 at 6:32 PM, Douglas Schilling Landgraf
wrote:
> Hello everyone,
>
> Most of you should asking yourself why the hg commit are very slow.
> Unfortunately, I had a business trip (out of my country) in the last 3
> weeks. Now, I am back
> and I will restart the commits and r
Hello everyone,
Most of you should asking yourself why the hg commit are very slow.
Unfortunately, I had a business trip (out of my country) in the last 3
weeks. Now, I am back
and I will restart the commits and read all my emails. If you guys
want to help me or
have free time to do this,
Hey Mauro,
I've queued up some lirc fixes and a couple of patches that add a new
ir-core driver for the Nuvoton w836x7hg Super I/O integrated CIR
functionality. All but the Kconfig re-sorting patch have been posted to
linux-media for review, but I'm hoping they can all get merged in time for
the 2
On 8 October 2010 22:13, Jonathan Corbet wrote:
> A problem like that will be at the controller level, not the sensor
> level. Given that this is an XO-1 report, I'd assume something
> requires tweaking in the cafe_ccic driver. I wasn't aware of this; I
> know it worked once upon a time.
I repo
Signed-off-by: Jarod Wilson
---
drivers/staging/lirc/lirc_it87.c | 17 -
drivers/staging/lirc/lirc_ite8709.c |6 +++---
drivers/staging/lirc/lirc_parallel.c | 32
drivers/staging/lirc/lirc_serial.c | 21 ++---
driv
On 8 October 2010 22:11, Jonathan Corbet wrote:
> I'm certainly not attached to this mode, but...does it harm anybody if
> it's there?
Yes. Applications like gstreamer will pick this resolution if its the
closest resolution to the target file resolution. On XO-1 we always
pick a low res so gstrea
On Fri, 8 Oct 2010 22:04:32 +0100 (BST)
Daniel Drake wrote:
> Add a module parameter so that the user can specify this information.
> And add DMI detection for appropriate clock speeds on the OLPC XO-1 and
> XO-1.5 laptops. If specified, the module parameter wins over whatever we
> might have se
On Fri, 8 Oct 2010 22:04:18 +0100 (BST)
Daniel Drake wrote:
> Capturing at this resolution results in an ugly green horizontal line
> at the left side of the image. Disable until fixed.
A problem like that will be at the controller level, not the sensor
level. Given that this is an XO-1 report
From: Joris van Rantwijk
8<
I tested lirc_serial and found that it works fine.
Except the LIRC ioctls do not work in my 64-bit-kernel/32-bit-user
setup. I added compat_ioctl entries in the drivers to fix this.
While doing so, I noticed inconsistencies in the argument type of
the LIRC ioc
On Fri, 8 Oct 2010 22:04:12 +0100 (BST)
Daniel Drake wrote:
> This super-low-resolution mode only captures from a small portion of
> the sensor FOV, making it a bit useless.
I'm certainly not attached to this mode, but...does it harm anybody if
it's there?
ov7670 sensors appear in settings oth
Hi,
The cafe_ccic + ov7670 combination is currently broken in mainstream
on the OLPC XO-1 laptop because of it's move to i2c (2bf7de4), in
order to work on the new XO-1.5 laptop. The smbus IO code was brought
back in 467142093 but this code is never triggered - CONFIG_OLPC_XO_1
doesn't exist.
I w
For accurate frame rate limiting, we need to know the speed of the external
clock wired into the ov7670 chip.
Add a module parameter so that the user can specify this information.
And add DMI detection for appropriate clock speeds on the OLPC XO-1 and
XO-1.5 laptops. If specified, the module param
This super-low-resolution mode only captures from a small portion of
the sensor FOV, making it a bit useless.
Signed-off-by: Daniel Drake
---
drivers/media/video/ov7670.c |6 +-
1 files changed, 5 insertions(+), 1 deletions(-)
diff --git a/drivers/media/video/ov7670.c b/drivers/media/vi
Capturing at this resolution results in an ugly green horizontal line
at the left side of the image. Disable until fixed.
http://dev.laptop.org/ticket/10231
Signed-off-by: Daniel Drake
---
drivers/media/video/ov7670.c |5 -
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/
Per discussion with Andy Walls on irc, rx fifo overruns are not all that
uncommon on a busy system, and the initial posting of the nuvoton-cir
driver doesn't handle them well enough. With this addition, we'll drain
the hw fifo, attempt to process any ir pulse trains completed with that
flush, then
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:Fri Oct 8 19:00:24 CEST 2010
path:http://www.linuxtv.org/hg/v4l-dvb
changeset: 15164:1da5fed5c8b2
git master:
This is a new ir-core pnp driver for the Nuvoton w836x7hg integrated CIR
function. The chip is found on at least the ASRock ION 330HT boxes and
apparently, on a number of Intel DP55-series motherboards:
http://www.asrock.com/nettop/overview.asp?Model=ION%20330HT
http://downloadcenter.intel.com/Det
Em 08-10-2010 09:32, Jean Delvare escreveu:
> On Sun, 26 Sep 2010 16:25:53 +0200, Jean Delvare wrote:
>> Commit 8dc09004978538d211ccc36b5046919489e30a55 assumes that
>> dev->rc_input_dev is always set. It is, however, NULL if dvb-usb was
>> loaded with option disable_rc_polling=1.
>>
>> Signed-off-
On Sun, 26 Sep 2010 16:25:53 +0200, Jean Delvare wrote:
> Commit 8dc09004978538d211ccc36b5046919489e30a55 assumes that
> dev->rc_input_dev is always set. It is, however, NULL if dvb-usb was
> loaded with option disable_rc_polling=1.
>
> Signed-off-by: Jean Delvare
> Cc: Mauro Carvalho Chehab
> -
Em 08-10-2010 16:03, Dmitri Belimov escreveu:
> Hi Mauro
>
> Not so good. Audio with this patch has bad white noise sometimes and
> bad quality. I try found better configuration for SECAM-DK.
Ok. Well, feel free to modify it. I think that this approach may be better,
especially if we need to add
>> > > Bastian Hecht wrote:
>> > >
>> > > > I want to write a sensor driver for the mt9p031 (not mt9t031) camera
>> > > > chip and start getting confused about the different kernel forks and
>
> There is already an mt9t031 v4l2-subdev / soc-camera driver, so, if
> mt9t031 and mt9p031 are indeed sim
Due to errorneous swapping of image dimensions the rotation
control was not handled properly in subsequent calls.
Signed-off-by: Sylwester Nawrocki
Signed-off-by: Kyungmin Park
---
drivers/media/video/s5p-fimc/fimc-core.c | 15 ++---
drivers/media/video/s5p-fimc/fimc-reg.c | 101 +++
It is not necessary to lock both capture and output buffer queue while
setting format for single queue.
Signed-off-by: Sylwester Nawrocki
Signed-off-by: Kyungmin Park
---
drivers/media/video/s5p-fimc/fimc-core.c | 69 +
1 files changed, 31 insertions(+), 38 deletio
Register access functions refactored for camera capture interface
control. Removed the workqueue since it was only useful for FIFO
output mode which is not supported at this time.
Fixed errors on module unload. Comments and whitespace cleanup.
Signed-off-by: Sylwester Nawrocki
Signed-off-by: Kyun
Add MIPI CSI format definitions, prepare DMA address
definitions for interlaced input frame mode.
Signed-off-by: Sylwester Nawrocki
Signed-off-by: Kyungmin Park
---
drivers/media/video/s5p-fimc/fimc-reg.c |6 +-
drivers/media/video/s5p-fimc/regs-fimc.h | 61 -
Hi all,
here is a fourth version of patches adding camera capture capability
to the s5p-fimc driver. It contains minor changes to adhere to patch
submitting rules.
Changes since v1:
- entirely removed plat-samsung/include/plat/fimc.h header so there is no
platform code dependency
- improved s/
Hi Guennadi,
On Friday 08 October 2010 09:00:36 Guennadi Liakhovetski wrote:
> Hi Mauro
>
> So, as promised, here goes part 2 of 2.6.37 patches for soc-camera and
> related. There's also going to be one issue with this one to take care of:
> the last patch will conflict with Laurent's pad-level o
Hi Mauro
So, as promised, here goes part 2 of 2.6.37 patches for soc-camera and
related. There's also going to be one issue with this one to take care of:
the last patch will conflict with Laurent's pad-level ops patches, which
also move mediabus pixel codes around. But since Laurent's patches
29 matches
Mail list logo
