(adding V4L ML to CC and preserving the complete reply for V4L readers)
On Thu, 27 May 2010, Jaya Kumar wrote:
> On Wed, May 26, 2010 at 10:09 PM, Guennadi Liakhovetski
> wrote:
> > Problem: Currently the standard way to provide graphical output on various
> > (embedded) displays like LCDs is to
From: Huzaifa Sidhpurwala
---
lib/libv4l1/libv4l1.c | 39 ++-
1 files changed, 38 insertions(+), 1 deletions(-)
diff --git a/lib/libv4l1/libv4l1.c b/lib/libv4l1/libv4l1.c
index f64025a..077d57c 100644
--- a/lib/libv4l1/libv4l1.c
+++ b/lib/libv4l1/libv4l1.c
> -Original Message-
> From: linux-fbdev-ow...@vger.kernel.org [mailto:linux-fbdev-
> ow...@vger.kernel.org] On Behalf Of Guennadi Liakhovetski
> Sent: Wednesday, May 26, 2010 7:40 PM
> To: linux-fb...@vger.kernel.org
> Subject: Idea of a v4l -> fb interface driver
>
> This message has be
From: Huzaifa Sidhpurwala
---
lib/libv4l1/libv4l1.c | 39 ++-
1 files changed, 38 insertions(+), 1 deletions(-)
diff --git a/lib/libv4l1/libv4l1.c b/lib/libv4l1/libv4l1.c
index f64025a..077d57c 100644
--- a/lib/libv4l1/libv4l1.c
+++ b/lib/libv4l1/libv4l1.c
> -Original Message-
> From: Guennadi Liakhovetski [mailto:g.liakhovet...@gmx.de]
> Sent: Sunday, May 23, 2010 11:33 PM
> To: Hans Verkuil
> Cc: Linux Media Mailing List; Zhong, Jeff; Laurent Pinchart; Pawel Osciak;
> Zhang, Xiaolin; Aguirre, Sergio; Hiremath, Vaibhav; Hans de Goede; Mauro
I looked through my revision history and that bug has been there in the
driver source since at least May 2005, long before it was ever merged
into the kernel. Wow, what a great catch. Thanks!
Acked-By: Mike Isely
-Mike
On Wed, 26 May 2010, Julia Lawall wrote:
> From: Julia Lawall
>
>
ULE (Unidirectional Lightweight Encapsulation RFC 4326) decapsulation
code has a bug that incorrectly treats ULE SNDU packed into the
remaining 2 or 3 bytes of a MPEG2-TS frame as having invalid pointer
field on the subsequent MPEG2-TS frame.
This patch was generated and tested against the lat
If you need two receivers but can only spare up to one PCI or PCIe
slot,
why not use two USB or FireWire attached receivers?
FireWire ones seem to be out of production now though and weren't
exactly on the cheap side. OTOH one can drive up to 3 DVB FireWire
receivers on a single FireWire bus; and
It makes IR to work again for dm1105 and, possibly, others.
Signed-off-by: Igor M. Liplianin
---
diff --git a/linux/drivers/media/IR/ir-keytable.c
b/linux/drivers/media/IR/ir-keytable.c
--- a/linux/drivers/media/IR/ir-keytable.c
+++ b/linux/drivers/media/IR/ir-keytable.c
@@ -491,11 +491,12 @@
Ok so here is a new version for the controls state store/restore
functionality and a test app implementing the functionality.
I've removed the need for control order inside the file since this can
be done inside the application.
Simply ordering by id is enough for most auto/absolute control pairs
Am 25.05.2010 23:59, schrieb Helmut Auer:
> Hello
>
> I just wanted to compile v4l-dvb for my Gen2VDR Ditribution with kernel
> 2.6.34, but it fails
> because many modules are missing:
>
> #include
>
> and are getting errors like:
>
> /tmp/portage/media-tv/v4l-dvb-hg-0.1-r3/work/v4l-dvb/v4l/t
On Wednesday 26 May 2010 17:47:57 Hans de Goede wrote:
> Hi,
>
> I would like to add my "RFC: a processing plugin API for libv4l" to the
> schedule, see the mail I just send. This actually is one of the main
> reasons for me to come to the summit.
OK, I'll add it. I'll post an update topic list t
On Wednesday 26 May 2010 17:46:16 Pawel Osciak wrote:
> Hi Hans,
>
> thank you for your work on this!
>
> >Hans Verkuil wrote:
>
> >3) videobuf/videobuf2: what are the shortcomings, what are the requirements
> >for a 'proper' videobuf implementation, can the existing videobuf be fixed or
> >do w
Add auto-config support for iMON 2.4G LT RF device, based on
debug output from Giulio Amodeo in Red Hat bugzilla #572288.
Also flips the switch on only setting up the rf associate sysfs
attr only if we think we're looking at an RF device, vs. previously,
setting up the attr for all 0xffdc devices,
There was a mix of 0/1 and false/true. Pick one convention and stick
with it (I picked false/true).
I sent this once before, but it seems to have lost its way somehow, so
apologies if this is a duplicate...
Signed-off-by: Jarod Wilson
---
drivers/media/IR/imon.c | 48 +++--
Sorry for the line breakages.
diff -uprN v4l-dvb_orig/Documentation/video4linux/CARDLIST.saa7134
v4l-dvb/Documentation/video4linux/CARDLIST.saa7134
--- v4l-dvb_orig/Documentation/video4linux/CARDLIST.saa7134 2010-05-26
20:34:06.0 +0300
+++ v4l-dvb/Documentation/video4linux/CARDLIST.s
Am 25.05.2010 23:59, schrieb Helmut Auer:
> Hello
>
> I just wanted to compile v4l-dvb for my Gen2VDR Ditribution with kernel
> 2.6.34, but it fails
> because many modules are missing:
>
> #include
>
> and are getting errors like:
>
> /tmp/portage/media-tv/v4l-dvb-hg-0.1-r3/work/v4l-dvb/v4l/t
Hello Hermann, thank you for reply.
I updated the patch according to your advice. This card really doesn't
have tda9887 chip, so I fixed it.
As for UHF: I have cable TV and frequencies of most channels are in
range from 300 to 900 MHz,
so I think UHF is fine.
diff -uprN v4l-dvb_orig/Documentatio
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:Wed May 26 19:00:26 CEST 2010
path:http://www.linuxtv.org/hg/v4l-dvb
changeset: 14875:304cfde05b3f
git master:
>> I'm only writing about the technical possibilities.
>> Personally I prefer the USB Dongles, since they are flexible. Once you
>> leave your
>> home you can just unplug the DVB-C tuner connect it to a
>> notebook/netbook and use
>> it for FM, analog TV or DVB-T.
>>
>> Markus
>
> Oh, so you're not
On Tue, May 25, 2010 at 5:05 PM, Jarod Wilson wrote:
> On Wed, Apr 28, 2010 at 12:32 AM, Jarod Wilson wrote:
>> On Sat, Apr 24, 2010 at 1:12 AM, David Härdeman wrote:
>>> On Fri, Apr 23, 2010 at 01:40:34PM -0400, Jarod Wilson wrote:
So now that I'm more or less done with porting the imon dr
From: Randy Dunlap
Fix ir-nec-decoder build: it uses bitrev library code, so
select BITREVERSE in its Kconfig.
ir-nec-decoder.c:(.text+0x1a2517): undefined reference to `byte_rev_table'
ir-nec-decoder.c:(.text+0x1a2526): undefined reference to `byte_rev_table'
ir-nec-decoder.c:(.text+0x1a2530):
From: Julia Lawall
Add a mutex_unlock missing on the error path. In the other functions in
the same file the locks and unlocks of this mutex appear to be balanced,
so it would seem that the same should hold in this case.
The semantic match that finds this problem is as follows:
(http://coccinel
Hi Hans,
thank you for your work on this!
>Hans Verkuil wrote:
>3) videobuf/videobuf2: what are the shortcomings, what are the requirements
>for a 'proper' videobuf implementation, can the existing videobuf be fixed or
>do we need a videobuf2. If the latter, what would be needed to convert
>exis
Hi,
I would like to add my "RFC: a processing plugin API for libv4l" to the
schedule, see the mail I just send. This actually is one of the main
reasons for me to come to the summit.
Thanks & Regards,
Hans
On 05/23/2010 12:36 PM, Hans Verkuil wrote:
Hi all,
This is a tentative agenda for th
Hi all,
See attachment.
Regards,
Hans
RFC: a processing plugin API for libv4l
===
Since libv4l-0.6.x libv4l has the ability to do various video
processing steps in software:
- white balance
- gamma correction
- autogain and exposure (simply called autogain i
If you need two receivers but can only spare up to one PCI or PCIe
slot,
why not use two USB or FireWire attached receivers?
FireWire ones seem to be out of production now though and weren't
exactly on the cheap side. OTOH one can drive up to 3 DVB FireWire
receivers on a single FireWire bus; and
The problem is that dprintk() dereferences "dev" which is null here.
The i2cdprintk() uses "ir" so that's OK.
Also Jean Delvare pointed out a typo in the comment so we may as well
fix that.
Signed-off-by: Dan Carpenter
Acked-by: Jean Delvare
---
v2: Jean Delvare suggested that I use i2cdprintk(
Hi Mauro,
On Sun, 2010-04-25 at 13:13 -0300, Mauro Carvalho Chehab wrote:
> >
> > 2.
> > I tried using videobuf-dma-contig, but got poor performance. I can not
> > really explain why, I though it's due to the fact that the contiguous
> > buffer is allocated coherent -> no caching.
> > I saw both
The pvrusb2 driver does not currently support uncompressed video
capture. Rather, the data arrives to the application as mpeg2. There
are numerous ways to use this data. You can make it work with mplayer
for example, but not when mplayer is in pure V4L mode. Rather than
repeating it all he
Hi,
So I have decided to go with the v4l2-subdev API.
I have taken the omapxxcam and vivi.c as exemple, but I have some
questions...
I still don't understand how to register a v4l2 device. I tried to copy
the method from vivi.c using v4l2_device_register but it is not working?
If I just use vid
On Wed, 26 May 2010, Sascha Hauer wrote:
> Hi Guennadi et all,
>
> On our i.MX27 board we have a wide range of cameras (mt9m001, mt9v022,
> mt9m131). Registering all of them and let the probe routines decide
> which one is connected works quite good.
> The problem I have now is that the mt9m131 a
Hi,
The mt9m111 soc-camera driver has a swap_rgb_red_blue variable which is
hardcoded to 1. This results in, well the name says it, red and blue being
swapped in my picture.
Is this value needed on some boards or is it just a leftover from
development?
Sascha
--
Pengutronix e.K.
Hi Guennadi et all,
On our i.MX27 board we have a wide range of cameras (mt9m001, mt9v022,
mt9m131). Registering all of them and let the probe routines decide
which one is connected works quite good.
The problem I have now is that the mt9m131 allows for a higher master
clock frequency. ATM the mcl
IR support on FusionHDTV cards is broken since kernel 2.6.31. One side
effect of the switch to the standard binding model for IR I2C devices
was to let i2c-core do the probing instead of the ir-kbd-i2c driver.
There is a slight difference between the two probe methods: i2c-core
uses 0-byte writes,
On Tue, 25 May 2010 11:21:50 +0200, Dan Carpenter wrote:
> The original code had two break statements in a row.
>
> Signed-off-by: Dan Carpenter
Acked-by: Jean Delvare
> ---
> v3: Put this in a seperate patch.
>
> diff --git a/drivers/media/video/saa7134/saa7134-input.c
> b/drivers/media/vid
Hi Dan,
On Tue, 25 May 2010 11:19:53 +0200, Dan Carpenter wrote:
> The problem is that dprintk() dereferences "dev" which is null here.
> The i2cdprintk() uses "ir" so that's OK.
>
> Signed-off-by: Dan Carpenter
> ---
> v2: Jean Delvare suggested that I use i2cdprintk() instead of modifying
> dp
This is the soc_camera support developed by Sascha Hauer for the i.MX27. Alan
Carvalho de Assis modified the original driver to get it working on more recent
kernels. I modified it further to add support for i.MX25. This driver has been
tested on i.MX25 and i.MX27 based platforms.
Signed-off-by:
Signed-off-by: Baruch Siach
---
arch/arm/mach-mx25/clock.c| 14 --
arch/arm/mach-mx25/devices.c | 22 ++
arch/arm/mach-mx25/devices.h |1 +
arch/arm/plat-mxc/include/mach/mx25.h |2 ++
4 files changed, 37 insertions(+), 2 d
Signed-off-by: Baruch Siach
---
arch/arm/mach-mx2/clock_imx27.c |2 +-
arch/arm/mach-mx2/devices.c | 31 +++
arch/arm/mach-mx2/devices.h |1 +
3 files changed, 33 insertions(+), 1 deletions(-)
diff --git a/arch/arm/mach-mx2/clock_imx27.c b/arch/arm/m
This series contains a soc_camera driver for the i.MX25/i.MX27 CSI device, and
platform code for the i.MX25 and i.MX27 chips. This driver is based on a
driver for i.MX27 CSI from Sascha Hauer, that Alan Carvalho de Assis has
posted in linux-media last December[1]. I tested the mx2_camera driver
On Tue, May 25, 2010 at 04:20:49PM +0300, Baruch Siach wrote:
> Hi Sascha,
>
> On Tue, May 25, 2010 at 03:16:24PM +0200, Sascha Hauer wrote:
> > On Mon, May 24, 2010 at 04:20:39PM +0300, Baruch Siach wrote:
> > > This is the soc_camera support developed by Sascha Hauer for the i.MX27.
> > > Alan
On Wed, 26 May 2010, Baruch Siach wrote:
> Hi Guennadi,
>
> Thanks for your comments. A question below.
>
> On Tue, May 25, 2010 at 05:34:52PM +0200, Guennadi Liakhovetski wrote:
> > On Mon, 24 May 2010, Baruch Siach wrote:
>
> [snip]
>
> > > +static void mx2_camera_deactivate(struct mx2_camer
Hi Guennadi,
Thanks for your comments. A question below.
On Tue, May 25, 2010 at 05:34:52PM +0200, Guennadi Liakhovetski wrote:
> On Mon, 24 May 2010, Baruch Siach wrote:
[snip]
> > +static void mx2_camera_deactivate(struct mx2_camera_dev *pcdev)
> > +{
> > + unsigned long flags;
> > +
> > +
Mauro Carvalho Chehab wrote:
> Stefan Richter wrote:
[CONFIG_RC_MAP et al]
>> Please leave the default of new options at N.
>>
>> (Unless this were a special case of new options that replaced older
>> options and need to be migrated to 'on' per default in make oldconfig.
>> I think this is not the
I've got a Genius iSlim 310 camera. This device works for me (skype,
mplayer, ffmpeg etc works).
The only problem I've noticed is that sometimes image blinks with green colour.
lsusb -v
Bus 005 Device 013: ID 093a:2625 Pixart Imaging, Inc.
Device Descriptor:
bLength 18
bDescript
If you need two receivers but can only spare up to one PCI or PCIe
slot,
why not use two USB or FireWire attached receivers?
FireWire ones seem to be out of production now though and weren't
exactly on the cheap side. OTOH one can drive up to 3 DVB FireWire
receivers on a single FireWire bus; and
On Wed, May 26, 2010 at 9:01 AM, Jed wrote:
>
> Not sure what you mean, I don't suppose you could clarify?
>
> You mean I might be able to buy 2x mini-PCIe cards that can be mounted onto
> a PCIe <-> USB bridge & then that card (bridge) will have two usb cables
> that need to be connected to 2 USB
Ideally it'd be dual DVB-C, the only one I've found is more than dual
DVB-C& is far too expensive.
If you need two receivers but can only spare up to one PCI or PCIe
slot,
why not use two USB or FireWire attached receivers?
FireWire ones seem to be out of production now though and weren't
exac
49 matches
Mail list logo
