Hi Trent,
On Sat, 21 Feb 2009 05:58:10 -0800 (PST), Trent Piepho wrote:
On Sat, 21 Feb 2009, Jean Delvare wrote:
Well, that's basically what Hans has been doing with
v4l2-i2c-drv-legacy.h for months now, isn't it? This is the easy part
(even though even this wasn't exactly trivial...)
Hi Mauro,
Only answering points Hans didn't already answered (and I agree with
him):
On Fri, 20 Feb 2009 21:23:27 -0300, Mauro Carvalho Chehab wrote:
On Wed, 18 Feb 2009 14:01:05 +0100
Jean Delvare kh...@linux-fr.org wrote:
Not necessarily something to be proud about. This only shows how
On Sat, 21 Feb 2009 08:28:50 +0100
Hans Verkuil hverk...@xs4all.nl wrote:
On Saturday 21 February 2009 03:13:50 Mauro Carvalho Chehab wrote:
On Sat, 21 Feb 2009 02:12:53 +0100
Hans Verkuil hverk...@xs4all.nl wrote:
I think that maybe we'll need some legacy-like support for bttv and
On Fri, 20 Feb 2009, Mauro Carvalho Chehab wrote:
On Sat, 21 Feb 2009 02:12:53 +0100
Hans Verkuil hverk...@xs4all.nl wrote:
I think that maybe we'll need some legacy-like support for bttv and cx88,
since there are some boards that relies on the old i2c method to work. On
those boards
On Saturday 21 February 2009 12:58:01 Mauro Carvalho Chehab wrote:
On Sat, 21 Feb 2009 08:28:50 +0100
Hans Verkuil hverk...@xs4all.nl wrote:
On Saturday 21 February 2009 03:13:50 Mauro Carvalho Chehab wrote:
On Sat, 21 Feb 2009 02:12:53 +0100
Hans Verkuil hverk...@xs4all.nl wrote:
On Sat, 21 Feb 2009 13:45:40 +0100
Hans Verkuil hverk...@xs4all.nl wrote:
tda9840 support is provided by tda9840.ko, but there's no
request_module() or any other reference (except for the above comment) to
it at bttv driver. I believe that this is not an isolated case.
The tda9840 is
On Sat, 21 Feb 2009 04:06:53 -0800 (PST)
Trent Piepho xy...@speakeasy.org wrote:
On Fri, 20 Feb 2009, Mauro Carvalho Chehab wrote:
On Sat, 21 Feb 2009 02:12:53 +0100
Hans Verkuil hverk...@xs4all.nl wrote:
I think that maybe we'll need some legacy-like support for bttv and
cx88,
Hi Trent,
On Sat, 21 Feb 2009 04:06:53 -0800 (PST), Trent Piepho wrote:
On Fri, 20 Feb 2009, Mauro Carvalho Chehab wrote:
On Sat, 21 Feb 2009 02:12:53 +0100
Hans Verkuil hverk...@xs4all.nl wrote:
That's what the i2c_new_probed_device() call is for (called through
On Sat, 21 Feb 2009 14:28:31 +0100, Hans Verkuil wrote:
On Saturday 21 February 2009 14:11:30 Jean Delvare wrote:
Well, that's basically what Hans has been doing with
v4l2-i2c-drv-legacy.h for months now, isn't it? This is the easy part
(even though even this wasn't exactly trivial...)
On Sat, 21 Feb 2009, Jean Delvare wrote:
On Sat, 21 Feb 2009 04:06:53 -0800 (PST), Trent Piepho wrote:
The new i2c driver interface also supports a -detect() method and a list
of address_data to use it with. This is much more like the legacy model
than using i2c_new_probed_device().
On Sat, 21 Feb 2009 13:45:40 +0100, Hans Verkuil wrote:
On Saturday 21 February 2009 12:58:01 Mauro Carvalho Chehab wrote:
On Sat, 21 Feb 2009 08:28:50 +0100
Hans Verkuil hverk...@xs4all.nl wrote:
OK, once more: there are two types of legacy code: one is that drivers
have to be switched
Hi,
just a short confirmation for cx88xx cards with external audio decoders.
Am Samstag, den 21.02.2009, 09:56 -0300 schrieb Mauro Carvalho Chehab:
On Sat, 21 Feb 2009 13:45:40 +0100
Hans Verkuil hverk...@xs4all.nl wrote:
tda9840 support is provided by tda9840.ko, but there's no
On Sat, 21 Feb 2009 10:42:17 -0600 (CST), kilg...@banach.math.auburn.edu wrote:
This is not exactly what I was trying to say. I'll try again.
1. Anyone who would call himself a developer will run quite recent kernels
without being forced to do so, voluntarily and with pleasure.
2.
Am Freitag, den 20.02.2009, 10:49 +0100 schrieb Jean Delvare:
On Fri, 20 Feb 2009 07:53:16 +0100, Hans Verkuil wrote:
On Friday 20 February 2009 04:57:11 hermann pitton wrote:
Hans decided deliberately to extend backward compat even down to 2.6.16,
now seeing the bill.
I didn't
On Wed, 18 Feb 2009 14:01:05 +0100
Jean Delvare kh...@linux-fr.org wrote:
Hi Mauro,
On Wed, 18 Feb 2009 07:10:41 -0300, Mauro Carvalho Chehab wrote:
On Wed, 18 Feb 2009 09:55:53 +0100 (CET)
Hans Verkuil hverk...@xs4all.nl wrote:
Not at all. I work with embedded systems and what
On Saturday 21 February 2009 01:23:27 Mauro Carvalho Chehab wrote:
On Wed, 18 Feb 2009 14:01:05 +0100
Jean Delvare kh...@linux-fr.org wrote:
Hi Mauro,
On Wed, 18 Feb 2009 07:10:41 -0300, Mauro Carvalho Chehab wrote:
On Wed, 18 Feb 2009 09:55:53 +0100 (CET)
Hans Verkuil
On Fri, 20 Feb 2009, Mauro Carvalho Chehab wrote:
On Wed, 18 Feb 2009 14:01:05 +0100
Jean Delvare kh...@linux-fr.org wrote:
Hi Mauro,
On Wed, 18 Feb 2009 07:10:41 -0300, Mauro Carvalho Chehab wrote:
On Wed, 18 Feb 2009 09:55:53 +0100 (CET)
Hans Verkuil hverk...@xs4all.nl wrote:
Not at
On Sat, 21 Feb 2009 02:12:53 +0100
Hans Verkuil hverk...@xs4all.nl wrote:
I think that maybe we'll need some legacy-like support for bttv and cx88,
since there are some boards that relies on the old i2c method to work. On
those boards (like cx88 Pixelview), the same board model (and PCB
Hi,
Am Mittwoch, den 18.02.2009, 14:01 +0100 schrieb Jean Delvare:
Hi Mauro,
On Wed, 18 Feb 2009 07:10:41 -0300, Mauro Carvalho Chehab wrote:
On Wed, 18 Feb 2009 09:55:53 +0100 (CET)
Hans Verkuil hverk...@xs4all.nl wrote:
Not at all. I work with embedded systems and what happens is
On Friday 20 February 2009 04:57:11 hermann pitton wrote:
Hi,
cut
---
I don't want to come up with old stories about what happened in the
past, there are some.
It looks like Jean tries to find a good compromise.
So, I don't deny, that recent Fedora stuff is not as stable as it was
for
--- On Wed, 2/18/09, Hans Verkuil hverk...@xs4all.nl wrote:
From: Hans Verkuil hverk...@xs4all.nl
Subject: Re: Minimum kernel version supported by v4l-dvb
To: Mauro Carvalho Chehab mche...@infradead.org
Cc: Jean Delvare kh...@linux-fr.org, linux-media@vger.kernel.org
Date: Wednesday
--- On Wed, 2/18/09, Hans Verkuil hverk...@xs4all.nl wrote:
From: Hans Verkuil hverk...@xs4all.nl
Subject: Re: Minimum kernel version supported by v4l-dvb
To: Mauro Carvalho Chehab mche...@infradead.org
Cc: Jean Delvare kh...@linux-fr.org, linux-media@vger.kernel.org
Date: Wednesday
Hi Mauro,
On Wed, 18 Feb 2009 09:55:53 +0100 (CET)
Hans Verkuil hverk...@xs4all.nl wrote:
Not at all. I work with embedded systems and what happens is that you
effectively take a kernel snapshot for your device and stick to that.
You're not using v4l-dvb, but you might backport important
On Wed, 18 Feb 2009 11:54:30 +0100 (CET)
Hans Verkuil hverk...@xs4all.nl wrote:
Hi Mauro,
On Wed, 18 Feb 2009 09:55:53 +0100 (CET)
Hans Verkuil hverk...@xs4all.nl wrote:
Not at all. I work with embedded systems and what happens is that you
effectively take a kernel snapshot for your
Hi Mauro,
On Wed, 18 Feb 2009 07:10:41 -0300, Mauro Carvalho Chehab wrote:
On Wed, 18 Feb 2009 09:55:53 +0100 (CET)
Hans Verkuil hverk...@xs4all.nl wrote:
Not at all. I work with embedded systems and what happens is that you
effectively take a kernel snapshot for your device and stick to
kernel version
supported by the v4l-dvb repository from 2.6.16 to at least 2.6.22.
Ideal for us would even be 2.6.26, but I would understand that this is
too recent for you. Kernel 2.6.22 is one year and a half old, I
honestly doubt that people fighting to get their brand new TV adapter
to work
, and our progress is slow.
So I would like you to consider changing the minimum kernel version
supported by the v4l-dvb repository from 2.6.16 to at least 2.6.22.
Ideal for us would even be 2.6.26, but I would understand that this is
too recent for you. Kernel 2.6.22 is one year and a half old, I
already be all done. But as things stand
today, he has to do most of the work, and our progress is slow.
So I would like you to consider changing the minimum kernel version
supported by the v4l-dvb repository from 2.6.16 to at least 2.6.22.
Ideal for us would even be 2.6.26, but I would
of the work, and our progress is slow.
So I would like you to consider changing the minimum kernel version
supported by the v4l-dvb repository from 2.6.16 to at least 2.6.22.
Ideal for us would even be 2.6.26, but I would understand that this is
too recent for you. Kernel 2.6.22 is one year
, and this would already be all done. But as things stand
today, he has to do most of the work, and our progress is slow.
So I would like you to consider changing the minimum kernel version
supported by the v4l-dvb repository from 2.6.16 to at least 2.6.22.
Ideal for us would even be 2.6.26
would
probably have been able to convert most of the drivers myself, without
Hans' help, and this would already be all done. But as things stand
today, he has to do most of the work, and our progress is slow.
So I would like you to consider changing the minimum kernel version
supported
is slow.
So I would like you to consider changing the minimum kernel version
supported by the v4l-dvb repository from 2.6.16 to at least 2.6.22.
Ideal for us would even be 2.6.26, but I would understand that this
is too recent for you. Kernel 2.6.22 is one year and a half old, I
32 matches
Mail list logo
