Minimum kernel version supported by v4l-dvb
Hi Mauro,
These days I am helping Hans Verkuil convert the last users of the legacy i2c device driver binding model to the new, standard binding model. It turns out to be a very complex task because the v4l-dvb repository is supposed to still support kernels as old as 2.6.16, while the initial support for the new i2c binding model was added in kernel 2.6.22 (and even that is somewhat different from what is upstream now.) This forces us to add quirks all around the place, which will surely result in bugs because the code becomes hard to read, understand and maintain.
In fact, without this need for backwards compatibility, I 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 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 are using anything older. As a matter of fact, kernel 2.6.22 is what openSUSE 10.3 has, and this is the oldest openSUSE product that is still maintained.
I understand and respect your will to let a large range of users build the v4l-dvb repository, but at some point the cost for developers seems to be too high, so there's a balance to be found between users and developers. At the moment the balance isn't right IMHO.
Thanks,
Signature · 1 line
Jean Delvare
Hi Jean,
Quoted 17 lines · On Tuesday 17 February 2009 14:23:27 Jean Delvare wrote:
Hi Mauro,
These days I am helping Hans Verkuil convert the last users of the legacy i2c device driver binding model to the new, standard binding model. It turns out to be a very complex task because the v4l-dvb repository is supposed to still support kernels as old as 2.6.16, while the initial support for the new i2c binding model was added in kernel 2.6.22 (and even that is somewhat different from what is upstream now.) This forces us to add quirks all around the place, which will surely result in bugs because the code becomes hard to read, understand and maintain.
In fact, without this need for backwards compatibility, I 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.
Quoted 8 lines
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 honestly doubt that people fighting to get their brand new TV adapter to work are using anything older. As a matter of fact, kernel 2.6.22 is what openSUSE 10.3 has, and this is the oldest openSUSE product that is still maintained.
Dropping pre-2.6.22 support may not be an issue for desktop systems that probably already run newer kernel versions. It might be a different story for embedded systems, as many users are stuck with old vendor-provided kernels.
I have no idea how many users we're talking about, but I know that the UVC driver is used with a 2.6.10 kernel on an embedded system by at least one person.
Quoted 4 lines
I understand and respect your will to let a large range of users build the v4l-dvb repository, but at some point the cost for developers seems to be too high, so there's a balance to be found between users and developers. At the moment the balance isn't right IMHO.
I won't vote against setting the minimum kernel version to 2.6.22, but we should at least be aware that embedded users, even if they're not very vocal, are lurking out there in the darkness of vendor-provided kernels.
Cheers,
Laurent Pinchart
Quoted 38 lines · On Tuesday 17 February 2009 23:24:03 Laurent Pinchart wrote:
Hi Jean,
Quoted 17 lines · On Tuesday 17 February 2009 14:23:27 Jean Delvare wrote:
Hi Mauro,
These days I am helping Hans Verkuil convert the last users of the legacy i2c device driver binding model to the new, standard binding model. It turns out to be a very complex task because the v4l-dvb repository is supposed to still support kernels as old as 2.6.16, while the initial support for the new i2c binding model was added in kernel 2.6.22 (and even that is somewhat different from what is upstream now.) This forces us to add quirks all around the place, which will surely result in bugs because the code becomes hard to read, understand and maintain.
In fact, without this need for backwards compatibility, I 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.
Quoted 8 lines
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 honestly doubt that people fighting to get their brand new TV adapter to work are using anything older. As a matter of fact, kernel 2.6.22 is what openSUSE 10.3 has, and this is the oldest openSUSE product that is still maintained.
Dropping pre-2.6.22 support may not be an issue for desktop systems that probably already run newer kernel versions. It might be a different story for embedded systems, as many users are stuck with old vendor-provided kernels.
I have no idea how many users we're talking about, but I know that the UVC driver is used with a 2.6.10 kernel on an embedded system by at least one person.
Quoted 8 lines
Quoted 4 lines
I understand and respect your will to let a large range of users build the v4l-dvb repository, but at some point the cost for developers seems to be too high, so there's a balance to be found between users and developers. At the moment the balance isn't right IMHO.
I won't vote against setting the minimum kernel version to 2.6.22, but we should at least be aware that embedded users, even if they're not very vocal, are lurking out there in the darkness of vendor-provided kernels.
Embedded users tend to make a snapshot of a particular kernel/driver and they don't usually upgrade either one. I do think that we need to make a branch (can hg do that?) or a copy of the repository just before dropping support for older kernels. So people who need to compile for a pre-2.6.22 kernel can still get older, but working sources.
But we are developing drivers for inclusion into the linux kernel, not providing an unpaid (!) service for the few people who cannot/will not upgrade to a newer kernel. Especially companies like Texas Instruments that are working on new v4l2 drivers for the embedded space (omap, davinci) are quite annoyed and confused by all the backwards compatibility stuff that we're dragging along. I find it much more important to cater to their needs than to support a driver on an ancient kernel for some anonymous company. If they need it, then pay someone to backport the driver.
And of course, I have to do way too much work to keep it all running on older kernels. It's really not what I want to spend my time on.
It's great to be able to support older kernels, but only as long as it is technically not too much of a burden. And that might mean that at some stage we have to stop supporting all or most of the older kernels if some core kernel change was made that would require a unreasonable amount of work to keep it running on older kernels.
By going to 2.6.22 we can at least go back to providing i2c drivers without too much compatibility obfuscation. A driver like wm8739 would look like this:
-----------------------------------------------
#if LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 26) static int wm8739_probe(struct i2c_client *client,
const struct i2c_device_id *id)
#else
static int wm8739_probe(struct i2c_client *client) #endif
{
struct wm8739_state *state;
...
}static int wm8739_remove(struct i2c_client *client)
{
struct v4l2_subdev *sd = i2c_get_clientdata(client);
v4l2_device_unregister_subdev(sd);
kfree(to_state(sd));
return 0;
}#if LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 26)
static const struct i2c_device_id wm8739_id[] = {
{ "wm8739", 0 },
{ }
};MODULE_DEVICE_TABLE(i2c, wm8739_id);
#endif
static struct i2c_driver wm8739_driver = {
.name = "wm8739",
.command = wm8739_command,
.probe = wm8739_probe,
.remove = wm8739_remove,
#if LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 26)
.id_table = wm8739_id,#endif
};
static int __init wm8739_init(void)
{
return i2c_add_driver(&wm8739_driver);
}static void __exit v4l2_i2c_drv_cleanup(void)
{
i2c_del_driver(&wm8739ver);
}module_init(wm8739_init);module_exit(wm8739_cleanup);
-----------------------------------------------
So that's three #ifdef's per i2c driver. I would personally prefer to take 2.6.26 as the cut-off point, but I suspect that's not going to happen.
I hope I'm not ranting too much, but these backwards compatibility constraints are really counter productive and slowing down progress. We're mostly unpaid volunteers and we should not have to spend time on this.
Regards,
Hans
Signature · 1 line
Hans Verkuil - video4linux developer - sponsored by TANDBERG
Quoted 5 lines · On Wed, 18 Feb 2009 00:06:38 +0100 Hans Verkuil <[email protected]> wrote:
Especially companies like Texas Instruments that
are working on new v4l2 drivers for the embedded space (omap, davinci) are quite annoyed and confused by all the backwards compatibility stuff that we're dragging along. I find it much more important to cater to their needs than to support a driver on an ancient kernel for some anonymous company.
The i2c code or any other backported code shouldn't affect any new driver.
For new drivers, they can just use 2.6.29-rc as reference and mark that the minimum required version for it is 2.6.30, at v4l/versions.txt.
If the driver is for x86/x86_64, it generally makes sense to preserve the backward compat bits, to help users.
However, in the specific case of TI development, for OMAP and similar drivers that are specific to some embedded architecture, and where a normal user will never need to test it for us, since the vendor is responsible for the driver, it is perfectly fine to update v4l/versions.txt for each new version that needs something for a newer API.
Cheers,
Mauro
Quoted 19 lines · On Saturday 21 February 2009 12:50:46 Mauro Carvalho Chehab wrote:
On Wed, 18 Feb 2009 00:06:38 +0100
Quoted 6 lines · Hans Verkuil
Especially companies like Texas Instruments that
are working on new v4l2 drivers for the embedded space (omap, davinci) are quite annoyed and confused by all the backwards compatibility stuff that we're dragging along. I find it much more important to cater to their needs than to support a driver on an ancient kernel for some anonymous company.The i2c code or any other backported code shouldn't affect any new driver.
For new drivers, they can just use 2.6.29-rc as reference and mark that the minimum required version for it is 2.6.30, at
v4l/versions.txt.If the driver is for x86/x86_64, it generally makes sense to preserve the backward compat bits, to help users.
Quoted 6 lines
However, in the specific case of TI development, for OMAP and similar drivers that are specific to some embedded architecture, and where a normal user will never need to test it for us, since the vendor is responsible for the driver, it is perfectly fine to update
v4l/versions.txtfor each new version that needs something for a newer API.
Not quite true, certainly not in the generic case. If you come from the outside and start developing v4l i2c drivers, then it is simply confusing when you look at existing drivers in the git tree to use as a model. It's not clear at all why we do things the way we do. That's bad.
Secondly, i2c modules developed for embedded systems are perfectly usable in e.g. webcams which you might want to support for older kernels. It's not an issue right now though, as long as soc-camera and int-dev aren't converted to use v4l2_subdev as that prevents them from being used this way.
Regards,
Hans
Signature · 1 line
Hans Verkuil - video4linux developer - sponsored by TANDBERG
Quoted 26 lines · On Tue, 17 Feb 2009 14:23:27 +0100 Jean Delvare <[email protected]> wrote:
Hi Mauro,
These days I am helping Hans Verkuil convert the last users of the legacy i2c device driver binding model to the new, standard binding model. It turns out to be a very complex task because the v4l-dvb repository is supposed to still support kernels as old as 2.6.16, while the initial support for the new i2c binding model was added in kernel 2.6.22 (and even that is somewhat different from what is upstream now.) This forces us to add quirks all around the place, which will surely result in bugs because the code becomes hard to read, understand and maintain.
In fact, without this need for backwards compatibility, I 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 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 are using anything older. As a matter of fact, kernel 2.6.22 is what openSUSE 10.3 has, and this is the oldest openSUSE product that is still maintained.
Quoted 4 lines
I understand and respect your will to let a large range of users build the v4l-dvb repository, but at some point the cost for developers seems to be too high, so there's a balance to be found between users and developers. At the moment the balance isn't right IMHO.
In my case, I use RHEL 5.3 that comes with 2.6.18. I need at least to have compatibility until this version, otherwise it will be harder to me to test things, since most of the time I need to run RHEL 5 kernel.
I know that other developers also use RHEL 5 on their environments.
Cheers,
Mauro
Quoted 34 lines · On Wednesday 18 February 2009 01:08:23 Mauro Carvalho Chehab wrote:
On Tue, 17 Feb 2009 14:23:27 +0100
Quoted 26 lines · Jean Delvare
Hi Mauro,
These days I am helping Hans Verkuil convert the last users of the legacy i2c device driver binding model to the new, standard binding model. It turns out to be a very complex task because the v4l-dvb repository is supposed to still support kernels as old as 2.6.16, while the initial support for the new i2c binding model was added in kernel 2.6.22 (and even that is somewhat different from what is upstream now.) This forces us to add quirks all around the place, which will surely result in bugs because the code becomes hard to read, understand and maintain.
In fact, without this need for backwards compatibility, I 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 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 are using anything older. As a matter of fact, kernel 2.6.22 is what openSUSE 10.3 has, and this is the oldest openSUSE product that is still maintained.
Quoted 4 lines
I understand and respect your will to let a large range of users build the v4l-dvb repository, but at some point the cost for developers seems to be too high, so there's a balance to be found between users and developers. At the moment the balance isn't right IMHO.
Quoted 5 lines
In my case, I use RHEL 5.3 that comes with 2.6.18. I need at least to have compatibility until this version, otherwise it will be harder to me to test things, since most of the time I need to run RHEL 5 kernel.
I know that other developers also use RHEL 5 on their environments.
Why should we have ugly and time consuming workarounds in our repository that hamper progress just to allow you to run RHEL 5? I'm sorry, that's no reason at all. I very much doubt other subsystem maintainers are stuck on 2.6.18.
And anyway, there is no way you can do proper testing against the new i2c API on that old kernel. The loading and probing of i2c modules is quite different, so that's never representative of what kernels >= 2.6.22 do.
Regards,
Hans
Signature · 1 line
Hans Verkuil - video4linux developer - sponsored by TANDBERG
Quoted 39 lines · On Wed, 18 Feb 2009 01:18:37 +0100 Hans Verkuil <[email protected]> wrote:
Quoted 38 lines · On Wednesday 18 February 2009 01:08:23 Mauro Carvalho Chehab wrote:
On Tue, 17 Feb 2009 14:23:27 +0100
Quoted 26 lines · Jean Delvare
Hi Mauro,
These days I am helping Hans Verkuil convert the last users of the legacy i2c device driver binding model to the new, standard binding model. It turns out to be a very complex task because the v4l-dvb repository is supposed to still support kernels as old as 2.6.16, while the initial support for the new i2c binding model was added in kernel 2.6.22 (and even that is somewhat different from what is upstream now.) This forces us to add quirks all around the place, which will surely result in bugs because the code becomes hard to read, understand and maintain.
In fact, without this need for backwards compatibility, I 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 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 are using anything older. As a matter of fact, kernel 2.6.22 is what openSUSE 10.3 has, and this is the oldest openSUSE product that is still maintained.
Quoted 4 lines
I understand and respect your will to let a large range of users build the v4l-dvb repository, but at some point the cost for developers seems to be too high, so there's a balance to be found between users and developers. At the moment the balance isn't right IMHO.
In my case, I use RHEL 5.3 that comes with 2.6.18. I need at least to have compatibility until this version, otherwise it will be harder to me to test things, since most of the time I need to run RHEL 5 kernel.
Quoted 6 lines
Quoted 1 line
I know that other developers also use RHEL 5 on their environments.
Why should we have ugly and time consuming workarounds in our repository that hamper progress just to allow you to run RHEL 5? I'm sorry, that's no reason at all. I very much doubt other subsystem maintainers are stuck on 2.6.18.
The role idea of having compatibility code is to allow people to test with distro kernels. If we decide do exclude one of the major distro, I don't see why not dropping support for the other distros and older kernels. For sure removing all backports will make developers happy, but this will reduce the amount of users that can help with the development, testing the drivers and providing us patches.
It would be much more easy to me to just drop all -hg trees with all backport and out-of-tree compilation and stuck with my -git trees, just like other sybsystem maintainers do, but I _do_ think that our community will suffer a lot with this. So, let's keep supporting at least the latest kernel version used by the major distros. So, for now, we should still keep support for 2.6.18.
Quoted 3 lines
And anyway, there is no way you can do proper testing against the new i2c API on that old kernel. The loading and probing of i2c modules is quite different, so that's never representative of what kernels >= 2.6.22 do.
I can assure you that I2C with v4l/dvb drivers work fine with 2.6.18. I use here with several drivers (uvc, bttv, saa7134, em28xx, ...).
As a normal user, I use skype regularly the latest uvc driver + 2.6.18 on RHEL5.
Of course, while developing, we should always test the drivers against the latest upstream tree, but this don't reduce the value of allowing normal users to use the latest drivers with their systems.
Cheers,
Mauro
Quoted 52 lines · On Wednesday 18 February 2009 03:08:15 Mauro Carvalho Chehab wrote:
On Wed, 18 Feb 2009 01:18:37 +0100
Quoted 42 lines · Hans Verkuil
Quoted 41 lines · On Wednesday 18 February 2009 01:08:23 Mauro Carvalho Chehab wrote:
On Tue, 17 Feb 2009 14:23:27 +0100
Quoted 27 lines · Jean Delvare
Hi Mauro,
These days I am helping Hans Verkuil convert the last users of the legacy i2c device driver binding model to the new, standard binding model. It turns out to be a very complex task because the v4l-dvb repository is supposed to still support kernels as old as 2.6.16, while the initial support for the new i2c binding model was added in kernel 2.6.22 (and even that is somewhat different from what is upstream now.) This forces us to add quirks all around the place, which will surely result in bugs because the code becomes hard to read, understand and maintain.
In fact, without this need for backwards compatibility, I 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 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 are using anything older. As a matter of fact, kernel 2.6.22 is what openSUSE 10.3 has, and this is the oldest openSUSE product that is still maintained.
Quoted 5 lines
I understand and respect your will to let a large range of users build the v4l-dvb repository, but at some point the cost for developers seems to be too high, so there's a balance to be found between users and developers. At the moment the balance isn't right IMHO.
In my case, I use RHEL 5.3 that comes with 2.6.18. I need at least to have compatibility until this version, otherwise it will be harder to me to test things, since most of the time I need to run RHEL 5 kernel.
Quoted 6 lines
Quoted 1 line
I know that other developers also use RHEL 5 on their environments.
Why should we have ugly and time consuming workarounds in our repository that hamper progress just to allow you to run RHEL 5? I'm sorry, that's no reason at all. I very much doubt other subsystem maintainers are stuck on 2.6.18.
Quoted 6 lines
The role idea of having compatibility code is to allow people to test with distro kernels. If we decide do exclude one of the major distro, I don't see why not dropping support for the other distros and older kernels. For sure removing all backports will make developers happy, but this will reduce the amount of users that can help with the development, testing the drivers and providing us patches.
99% (if not 100%) of that comes from the desktop area. We are bending over backwards for the mythical enterprise user who cannot upgrade, must have the latest drivers and wants it all for free. In the meantime we have crummy code in the kernel only to support this mythical user, and new developers starting to work with v4l are confused by the weird way i2c drivers are setup.
Quoted 6 lines
It would be much more easy to me to just drop all -hg trees with all backport and out-of-tree compilation and stuck with my -git trees, just like other sybsystem maintainers do, but I _do_ think that our community will suffer a lot with this. So, let's keep supporting at least the latest kernel version used by the major distros. So, for now, we should still keep support for 2.6.18.
It's not our job. It's the job of the distro companies to maintain their code and drivers and backport newer ones if needed. That's what they are paid for. I'm not paid for that, yet I still have to spend valuable time doing this shit (excuse the language).
If people are so keen on it, then let them pay me.
Quoted 8 lines
Quoted 4 lines
And anyway, there is no way you can do proper testing against the new i2c API on that old kernel. The loading and probing of i2c modules is quite different, so that's never representative of what kernels >= 2.6.22 do.
I can assure you that I2C with v4l/dvb drivers work fine with 2.6.18. I use here with several drivers (uvc, bttv, saa7134, em28xx, ...).
Quoted 6 lines
As a normal user, I use skype regularly the latest uvc driver + 2.6.18 on RHEL5.
Of course, while developing, we should always test the drivers against the latest upstream tree, but this don't reduce the value of allowing normal users to use the latest drivers with their systems.
Normal v4l users use a desktop PC and can easily upgrade. Enterprise users locked to an ancient kernel AND using v4l-dvb are NOT normal users. I've just looked it up and apparently RHEL 6 isn't planned for another year. By that time we're on 2.6.32/33 and maintaining compatibility for a whopping 15 kernels. Doesn't that strike you as ridiculous?
I might be wrong, but aren't you using RHEL 5 because you work for redhat these days? Not a typical user at all.
Regards,
Hans
Signature · 1 line
Hans Verkuil - video4linux developer - sponsored by TANDBERG
Quoted 172 lines · Hans Verkuil
From: Hans Verkuil <[email protected]>
Subject: Re: Minimum kernel version supported by v4l-dvb
To: "Mauro Carvalho Chehab" <[email protected]>
Cc: "Jean Delvare" <[email protected]>, [email protected]
Date: Wednesday, February 18, 2009, 9:36 AMQuoted 4 lines · On Wednesday 18 February 2009 03:08:15 Mauro Carvalho Chehab wrote:
On Wed, 18 Feb 2009 01:18:37 +0100
Quoted 1 line · Hans Verkuil
On Wednesday 18 February 2009 01:08:23 Mauro
Quoted 3 lines · Carvalho Chehab
Quoted 3 lines
Quoted 3 lines
On Tue, 17 Feb 2009 14:23:27 +0100
Jean Delvare <[email protected]>
Quoted 3 lines · wrote:
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Hi Mauro,
These days I am helping Hans Verkuil
convert the last users of the
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
legacy i2c device driver binding model
to the new, standard binding
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
model. It turns out to be a very
complex task because the v4l-dvb
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
repository is supposed to still support
kernels as old as 2.6.16,
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
while the initial support for the new
i2c binding model was added
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
in kernel 2.6.22 (and even that is
somewhat different from what is
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
upstream now.) This forces us to add
quirks all around the place,
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
which will surely result in bugs
because the code becomes hard to
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
read, understand and maintain.
In fact, without this need for
backwards compatibility, I would
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
probably have been able to convert most
of the drivers myself,
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
without Hans' help, and this would
already be all done. But as
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
things stand today, he has to do most
of the work, and our progress
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
is slow.
So I would like you to consider
changing the minimum kernel version
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
supported by the v4l-dvb repository
from 2.6.16 to at least 2.6.22.
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Ideal for us would even be 2.6.26, but
I would understand that this
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
is too recent for you. Kernel 2.6.22 is
one year and a half old, I
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
honestly doubt that people fighting to
get their brand new TV
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
adapter to work are using anything
older. As a matter of fact,
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
kernel 2.6.22 is what openSUSE 10.3
has, and this is the oldest
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
openSUSE product that is still
maintained.
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
I understand and respect your will to
let a large range of users
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
build the v4l-dvb repository, but at
some point the cost for
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
developers seems to be too high, so
there's a balance to be found
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
between users and developers. At the
moment the balance isn't right
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 1 line
IMHO.
In my case, I use RHEL 5.3 that comes with
2.6.18. I need at least to
Quoted 1 line
Quoted 1 line
Quoted 1 line
have compatibility until this version,
otherwise it will be harder to
Quoted 1 line
Quoted 1 line
Quoted 1 line
me to test things, since most of the time I
need to run RHEL 5
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
kernel.
I know that other developers also use RHEL 5
on their environments.
Quoted 2 lines
Quoted 2 lines
Why should we have ugly and time consuming
workarounds in our
Quoted 1 line
Quoted 1 line
repository that hamper progress just to allow you
to run RHEL 5? I'm
Quoted 1 line
Quoted 1 line
sorry, that's no reason at all. I very much
doubt other subsystem
Quoted 3 lines
Quoted 1 line
maintainers are stuck on 2.6.18.
The role idea of having compatibility code is to allow
people to test
Quoted 1 line
with distro kernels. If we decide do exclude one of
the major distro, I
Quoted 1 line
don't see why not dropping support for the other
distros and older
Quoted 1 line
kernels. For sure removing all backports will make
developers happy, but
Quoted 1 line
this will reduce the amount of users that can help
with the development,
Quoted 1 line
testing the drivers and providing us patches.
99% (if not 100%) of that comes from the desktop area. We are bending over
backwards for the mythical enterprise user who cannot upgrade, must have
the latest drivers and wants it all for free. In the meantime we have
crummy code in the kernel only to support this mythical user, and new
developers starting to work with v4l are confused by the weird way i2c
drivers are setup.Quoted 1 line
It would be much more easy to me to just drop all -hg
trees with all
Quoted 1 line
backport and out-of-tree compilation and stuck with my
-git trees, just
Quoted 1 line
like other sybsystem maintainers do, but I _do_ think
that our community
Quoted 1 line
will suffer a lot with this. So, let's keep
supporting at least the
Quoted 1 line
latest kernel version used by the major distros. So,
for now, we should
Quoted 1 line
still keep support for 2.6.18.
It's not our job. It's the job of the distro companies to maintain their
code and drivers and backport newer ones if needed. That's what they are
paid for. I'm not paid for that, yet I still have to spend valuable time
doing this shit (excuse the language).If people are so keen on it, then let them pay me.
Quoted 1 line
Quoted 1 line
And anyway, there is no way you can do proper
testing against the new
Quoted 1 line
Quoted 1 line
i2c API on that old kernel. The loading and
probing of i2c modules is
Quoted 1 line
Quoted 1 line
quite different, so that's never
representative of what kernels >=
Quoted 3 lines
Quoted 1 line
2.6.22 do.
I can assure you that I2C with v4l/dvb drivers work
fine with 2.6.18. I
Quoted 1 line
use here with several drivers (uvc, bttv, saa7134,
em28xx, ...).
Quoted 2 lines
As a normal user, I use skype regularly the latest uvc
driver + 2.6.18 on
Quoted 3 lines
RHEL5.
Of course, while developing, we should always test the
drivers against
Quoted 1 line
the latest upstream tree, but this don't reduce
the value of allowing
Quoted 1 line
normal users to use the latest drivers with their
systems.
Normal v4l users use a desktop PC and can easily upgrade. Enterprise users
locked to an ancient kernel AND using v4l-dvb are NOT normal users. I've
just looked it up and apparently RHEL 6 isn't planned for another year. By
that time we're on 2.6.32/33 and maintaining compatibility for a whopping
15 kernels. Doesn't that strike you as ridiculous?
Quoted 11 lines
I might be wrong, but aren't you using RHEL 5 because you work for redhat
these days? Not a typical user at all.Regards,
Hans
Signature · 2 lines
Hans Verkuil - video4linux developer - sponsored by TANDBERG
Hi,
I strongly oppose the idea to suppress old kernel versions' support.
People here discuss Linux as "This (PC) distro" and other "Desktop" flavor.
But, you must look at the global Linux market. Multiple embedded devices use Linux OS. The embedded Linux "market share" is something to argue about, some say that it about 25%, while other say its about 40%. The true numbers are unknown, since those devices can not be counted easily (like when access to any web-server), and the commercial companies that manufacture those devices neglect to publish numbers (anything between 5 to 7 digits number per device type are legit as any other). The problem is, that the BSPs (board support package to all PC guys here) for those devices are frozen, and hence the kernel version too.
I know devices that still use 2.6.10 (MontaVista) and other old version...
So, older version support is essential for those devices.
Uri Shkolnik