on Wed, 17 Mar 2010 09:12 am
in the Usenet newsgroup gmane.linux.drivers.video-input-infrastructure
hermann pitton wrote:
[snip]
>
> unfortunately the problem with these cards is known, but no good
> solution for now.
>
> Best description is from Hartmut and starts here.
>
> http://www.spinics.
Am Freitag, den 19.03.2010, 12:04 -0700 schrieb VDR User:
> Keeping v4l1 because some guys are still using some ancient setup is
> not a good reason. Keeping v4l1 because some app devs still haven't
> bothered to update their apps is not a good reason, especially given
> the amount of time they'v
Hi, Евгений,
is there any reason, why you set the charge pump bit to low and slow
tuning on a non FM tuner?
Cheers,
Hermann
Am Freitag, den 19.03.2010, 20:32 +0200 schrieb Евгений Бацман:
> A add tv tuner AverTV Studio 509UA but radio now not
> work(tuner_tea5764hn not in kernel)
>
>
>
> dif
Herton Ronaldo Krzesinski wrote:
> Em Sex 19 Mar 2010, às 18:56:57, Mauro Carvalho Chehab escreveu:
>> Hi Herton,
>>
>> Herton Ronaldo Krzesinski wrote:
>>> This change adds support for one more remote control type for Avermedia
>>> M135A. The new remote control reports slightly different codes, an
Em Sex 19 Mar 2010, às 18:56:57, Mauro Carvalho Chehab escreveu:
> Hi Herton,
>
> Herton Ronaldo Krzesinski wrote:
> > This change adds support for one more remote control type for Avermedia
> > M135A. The new remote control reports slightly different codes, and was
> > necessary to extend the mas
Hi Herton,
Herton Ronaldo Krzesinski wrote:
> This change adds support for one more remote control type for Avermedia
> M135A. The new remote control reports slightly different codes, and was
> necessary to extend the mask_keycode to differentiate between original
> remote control. One of the remo
Hello. I recently purchased a CHVIDEOCR conceptronic device, but is not
detected in opensuse 11.2 after having compiled and installed the latest
v4l-dvb.
The vendor and product ID is 1b80:e34e.
I tried to make it work with the em28xx module with ID card 9 (not fully
recognized) and 19 (system ha
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 Mar 19 19:00:28 CET 2010
path:http://www.linuxtv.org/hg/v4l-dvb
changeset: 14494:929298149eba
git master:
David Ellingsworth wrote:
> On Fri, Mar 19, 2010 at 1:43 PM, Mauro Carvalho Chehab
> wrote:
>> David Ellingsworth wrote:
>>> On Fri, Mar 19, 2010 at 9:47 AM, Mauro Carvalho Chehab
>>> wrote:
The V4L1 drivers that lasts are the ones without maintainers and probably
without
a large
Hans de Goede wrote:
>> 3) The removal of V4L1 means that the existing applications should not
>> try to include
>> videodev.h with newer kernels or their compilations will break (easy
>> to fix, but better
>> to remind application developers that may be reading this thread).
>> Also, the removal
Hi,
On 03/19/2010 02:01 PM, Mauro Carvalho Chehab wrote:
Hans Verkuil wrote:
Hi all,
V4L1 support has been marked as scheduled for removal for a long time. The
deadline for that in the feature-removal-schedule.txt file was July 2009.
As reference, this is what's written there:
What: Video
Hi,
On 03/19/2010 04:49 PM, David Ellingsworth wrote:
On Fri, Mar 19, 2010 at 9:47 AM, Mauro Carvalho Chehab
wrote:
The V4L1 drivers that lasts are the ones without maintainers and probably
without
a large users base. So, basically legacy hardware. So, their removals make
sense.
In many
Keeping v4l1 because some guys are still using some ancient setup is
not a good reason. Keeping v4l1 because some app devs still haven't
bothered to update their apps is not a good reason, especially given
the amount of time they've had to complete this task. Keeping v4l1
because package maintain
Hi,
On 03/19/2010 09:46 AM, Hans Verkuil wrote:
On Friday 19 March 2010 08:59:08 Hans Verkuil wrote:
Hi all,
V4L1 support has been marked as scheduled for removal for a long time.
The
deadline for that in the feature-removal-schedule.txt file was July
2009.
I think it is time that we remove
Hello all,
just want to let you know, that I found a "bug" in the em28xx driver,
which prevents the audio part of mentioned USB card to work.
Basically it is (to the best of my knowledge) just a typo in 'em28xx.h'
where the define for card #55 "EM2880_BOARD_TERRATEC_HYBRID_XS" should
be
> -Original Message-
> From: Karicheri, Muralidharan
> Sent: Friday, March 19, 2010 11:40 PM
> To: Hiremath, Vaibhav; linux-media@vger.kernel.org
> Cc: Rajashekhara, Sudhakar
> Subject: RE: [PATCH-V2 7/7] TVP514x: Add Powerup sequence during s_input to
> lock the signal properly
>
> Vaibha
A add tv tuner AverTV Studio 509UA but radio now not
work(tuner_tea5764hn not in kernel)
diff -r a/linux/drivers/media/common/tuners/tuner-types.c
--- a/linux/drivers/media/common/tuners/tuner-types.c 2010-03-17
20:38:10.0 +0200
+++ b/linux/drivers/media/common/tuners/tuner-types.c 2
This reverts commit bc52d6eb44de8f19934768d4d10d19fdbdc99950.
On newer kernels, a saa7134 board stopped to display TV video output
properly. After a bisect, I found it as the commit causing the issue.
Turns out that v4l_bound_align_image isn't doing the same bounding
calculation as manually done p
This change adds support for one more remote control type for Avermedia
M135A. The new remote control reports slightly different codes, and was
necessary to extend the mask_keycode to differentiate between original
remote control. One of the remote controls I had matched the original
binding, but s
This change adds support for one more remote control type for Avermedia
M135A. The new remote control reports slightly different codes, and was
necessary to extend the mask_keycode to differentiate between original
remote control. One of the remote controls I had matched the original
binding, but s
On Fri, Mar 19, 2010 at 2:00 PM, David Ellingsworth
wrote:
> Yes it is an old camera, but that does not mean there aren't people
> out there who still own cameras which would otherwise be usable if the
> driver worked. And sure people could just buy another camera.. but why
> replace hardware that
Vaibhav,
This patch has not fully resolved the lock issue. In my testing the change
done by Brijesh was required as well. Can you update me on what was your
findings based on my last email on this issue?
Murali Karicheri
Software Design Engineer
Texas Instruments Inc.
Germantown, MD 20874
phone:
On Fri, Mar 19, 2010 at 1:43 PM, Mauro Carvalho Chehab
wrote:
> David Ellingsworth wrote:
>> On Fri, Mar 19, 2010 at 9:47 AM, Mauro Carvalho Chehab
>> wrote:
>>> The V4L1 drivers that lasts are the ones without maintainers and probably
>>> without
>>> a large users base. So, basically legacy har
David Ellingsworth wrote:
> On Fri, Mar 19, 2010 at 9:47 AM, Mauro Carvalho Chehab
> wrote:
>> The V4L1 drivers that lasts are the ones without maintainers and probably
>> without
>> a large users base. So, basically legacy hardware. So, their removals make
>> sense.
>>
>
> In many ways the abo
On Fri, Mar 19, 2010 at 1:13 PM, Steffen Pankratz wrote:
> On Fri, 19 Mar 2010 13:07:23 -0400
> Devin Heitmueller wrote:
>
>> On Fri, Mar 19, 2010 at 1:01 PM, Steffen Pankratz wrote:
>> > Hi,
>> >
>> > this USB stick is a Pinnacle Pctv Hybrid Pro 320e device
>> > (ID eb1a:2881 eMPIA Technology,
On Fri, 19 Mar 2010 13:07:23 -0400
Devin Heitmueller wrote:
> On Fri, Mar 19, 2010 at 1:01 PM, Steffen Pankratz wrote:
> > Hi,
> >
> > this USB stick is a Pinnacle Pctv Hybrid Pro 320e device
> > (ID eb1a:2881 eMPIA Technology, Inc.).
> >
> > Is there anything else you need to know?
>
>
> This
On Fri, Mar 19, 2010 at 1:01 PM, Steffen Pankratz wrote:
> Hi,
>
> this USB stick is a Pinnacle Pctv Hybrid Pro 320e device
> (ID eb1a:2881 eMPIA Technology, Inc.).
>
> Is there anything else you need to know?
This was fixed some time ago. Just install the current v4l-dvb code
(instructions can
Hi,
this USB stick is a Pinnacle Pctv Hybrid Pro 320e device
(ID eb1a:2881 eMPIA Technology, Inc.).
Is there anything else you need to know?
Mar 19 17:54:47 hermes kernel: usb 1-4: new high speed USB device using
ehci_hcd and address 5
Mar 19 17:54:47 hermes kernel: Linux video capture interfa
On Fri, Mar 19, 2010 at 9:47 AM, Mauro Carvalho Chehab
wrote:
> The V4L1 drivers that lasts are the ones without maintainers and probably
> without
> a large users base. So, basically legacy hardware. So, their removals make
> sense.
>
In many ways the above statement is a catch 22. Most, if no
Laurent Pinchart schrieb:
> Those control, as their names imply, control the camera aperture
> settings.
>
> Signed-off-by: Laurent Pinchart
> ---
> Documentation/DocBook/v4l/compat.xml | 11 +++
> Documentation/DocBook/v4l/controls.xml| 19 +++
> Documentatio
On Fri, 2010-03-19 at 09:46 +0100, Hans Verkuil wrote:
> > On Friday 19 March 2010 08:59:08 Hans Verkuil wrote:
> >> Hi all,
> >>
> >> V4L1 support has been marked as scheduled for removal for a long time.
> >> The
> >> deadline for that in the feature-removal-schedule.txt file was July
> >> 2009.
No one has got this card and can say if this is normal (on a stable
kernel) or my hardware is broken?
Regards
Alina
Am Mittwoch, den 17.03.2010, 02:14 +0100 schrieb Alina Friedrichsen:
> My kernel is 2.6.33.
> When I want to watch DVB-T with VLC, loading the firmwares stops after
> the following
Hans Verkuil wrote:
>> Do we still have V4L1-only drivers that use videobuf ?
>
> No V4L1-only drivers use videobuf, but videobuf has support for the V4L1
> compat support in V4L2 drivers (the cgmbuf ioctl). So when we remove the
> compat support, then that videobuf code can be removed as well.
On Tue, 16 Mar 2010 12:05:02 +0100, Jean Delvare wrote:
> Executive summary (as I understand it): the card that no longer works
> is a DViCO FusionHDTV7 Dual Express
> (CX23885_BOARD_DVICO_FUSIONHDTV_7_DUAL_EXP), bridge driver cx23885. It
> has 2 xc5000 chips at I2C address 0x64 (on 2 different I2C
Hans Verkuil wrote:
> Hi all,
>
> V4L1 support has been marked as scheduled for removal for a long time. The
> deadline for that in the feature-removal-schedule.txt file was July 2009.
As reference, this is what's written there:
What: Video4Linux API 1 ioctls and from Video devices.
When: Ju
Hi Hans,
>Hans Verkuil wrote:
>This patch is for discussion only. It is just to illustrate the possibilities.
>Once the cleanup patch Pawel posted is merged, then I can try to make a proper
>patch series for this depending on the feedback I get.
I went over your patch and it seems like a good nex
card->driver is 15 characters and a NULL, the original code could
cause a buffer overflow.
Signed-off-by: Dan Carpenter
diff --git a/drivers/media/video/cx231xx/cx231xx-audio.c
b/drivers/media/video/cx231xx/cx231xx-audio.c
index 7793d60..b3282ae 100644
--- a/drivers/media/video/cx231xx/cx231xx
card->driver is 15 characters and a NULL. The original code
goes past the end of the array.
Signed-off-by: Dan Carpenter
diff --git a/drivers/media/video/em28xx/em28xx-audio.c
b/drivers/media/video/em28xx/em28xx-audio.c
index bd78338..530df0a 100644
--- a/drivers/media/video/em28xx/em28xx-audi
From: Vaibhav Hiremath
Signed-off-by: Vaibhav Hiremath
---
arch/arm/mach-omap2/devices.c | 28
1 files changed, 28 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-omap2/devices.c b/arch/arm/mach-omap2/devices.c
index 18ad931..83c92cd 100644
--- a/arch/a
From: Vaibhav Hiremath
Refreshed on top of latest linuxtv/master repository and
resubmitting the patch series again.
Please note that this patch is dependent on patch which add "ti-media"
directory (submitted earlier to this patch series).
Vaibhav Hiremath (2):
OMAP2/3 V4L2: Add support for O
From: Vaibhav Hiremath
AM3517 and DM644x uses same CCDC IP, so reusing the driver
for AM3517.
Signed-off-by: Vaibhav Hiremath
---
arch/arm/mach-omap2/board-am3517evm.c | 160 +
1 files changed, 160 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-omap2
This is a proposal to remove the videotext API and drivers for kernel
2.6.35. This API is found in include/linux/videotext.h and is supported by
the saa5246a and saa5249 i2c drivers.
To the best of my knowledge there are no applications that use this. I
have not been able to find any hardware that
On Fri, Mar 19, 2010 at 9:46 AM, Hans Verkuil wrote:
>
>> On Friday 19 March 2010 08:59:08 Hans Verkuil wrote:
>>> Hi all,
>>>
>>> V4L1 support has been marked as scheduled for removal for a long time.
>>> The
>>> deadline for that in the feature-removal-schedule.txt file was July
>>> 2009.
>>>
>>
On Friday 19 March 2010 09:46:02 Hans Verkuil wrote:
> > On Friday 19 March 2010 08:59:08 Hans Verkuil wrote:
> >> Hi all,
> >>
> >> V4L1 support has been marked as scheduled for removal for a long time.
> >> The deadline for that in the feature-removal-schedule.txt file was July
> >> 2009.
> >>
> On Friday 19 March 2010 08:59:08 Hans Verkuil wrote:
>> Hi all,
>>
>> V4L1 support has been marked as scheduled for removal for a long time.
>> The
>> deadline for that in the feature-removal-schedule.txt file was July
>> 2009.
>>
>> I think it is time that we remove the V4L1 compatibility suppo
On Friday 19 March 2010 08:59:08 Hans Verkuil wrote:
> Hi all,
>
> V4L1 support has been marked as scheduled for removal for a long time. The
> deadline for that in the feature-removal-schedule.txt file was July 2009.
>
> I think it is time that we remove the V4L1 compatibility support from V4L2
Hi all,
V4L1 support has been marked as scheduled for removal for a long time. The
deadline for that in the feature-removal-schedule.txt file was July 2009.
I think it is time that we remove the V4L1 compatibility support from V4L2
drivers for 2.6.35.
It would help with the videobuf cleanup as w
47 matches
Mail list logo
