From: Jean Delvare <khali@linux-fr.org>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: linux-media@vger.kernel.org
Subject: Re: POLL: for/against dropping support for kernels < 2.6.22
Date: Mon, 23 Feb 2009 14:49:17 +0100 [thread overview]
Message-ID: <20090223144917.257a8f65@hyperion.delvare> (raw)
Hi Hans,
> There are lot's of discussions, but it can be hard sometimes to actually
> determine someone's opinion.
>
> So here is a quick poll, please reply either to the list or directly to me
> with your yes/no answer and (optional but welcome) a short explanation to
> your standpoint. It doesn't matter if you are a user or developer, I'd like
> to see your opinion regardless.
>
> Please DO NOT reply to the replies, I'll summarize the results in a week's
> time and then we can discuss it further.
>
> Should we drop support for kernels <2.6.22 in our v4l-dvb repository?
>
X: Yes
> _: No
>
> Optional question:
>
> Why:
The cost to preserve backwards compatibility for these old kernels is
much too high compared to the remaining user-base. I can only repeat
the points I have made in the past week:
* Maintained distributions aimed at home users (Fedora, openSUSE) run
kernels >= 2.6.22 by now.
* Enterprise-class distributions (RHEL, SLED) are not the right target
for the v4l-dvb repository, so we don't care which kernels these are
running.
* Engineering time which is put into backwards compatibility would be
better spent on improving the drivers upstream and adding support
for new hardware faster.
* v4l-dvb depends on subsystems which do evolve, and when these changes
are too important (e.g. new i2c device driver binding model)
backwards compatibility comes are an unbearable complexity and cost.
That kind of cost sucks the time of current developers, might turn
them into ex-developers when they realize they lost all the fun, and
prevents new developers from joining the project because of the
complexity of the compatibility layer.
So let's just drop support for kernels < 2.6.22 and focus on better
supporting upstream and recent kernels.
Thanks,
--
Jean Delvare
next reply other threads:[~2009-02-23 13:49 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-23 13:49 Jean Delvare [this message]
2009-02-23 13:54 ` POLL: for/against dropping support for kernels < 2.6.22 Trent Piepho
2009-02-24 11:56 ` John Pilkington
2009-02-24 20:41 ` Simon Kenyon
[not found] ` <49A3DDFC.6010608@tesco.net>
2009-02-24 13:15 ` Jean Delvare
2009-02-24 14:34 ` John Pilkington
-- strict thread matches above, loose matches on Subject: below --
2009-02-25 8:35 Hans Verkuil
2009-02-23 14:09 Hans Verkuil
2009-02-23 1:24 sonofzev
2009-02-22 10:15 Hans Verkuil
2009-02-22 19:12 ` CityK
2009-02-22 23:52 ` Andy Walls
2009-02-22 22:56 ` Guennadi Liakhovetski
2009-02-22 23:27 ` kilgota
2009-02-23 1:13 ` hermann pitton
2009-02-23 6:41 ` Robert Golding
2009-02-23 8:32 ` VDR User
2009-02-23 12:26 ` Mauro Carvalho Chehab
2009-02-23 14:54 ` Mauro Carvalho Chehab
2009-02-23 14:48 ` Douglas Schilling Landgraf
2009-02-23 14:53 ` David Ellingsworth
2009-02-24 5:04 ` Trent Piepho
2009-02-24 7:25 ` Hans Verkuil
2009-02-24 13:12 ` Ales Jurik
2009-02-24 20:19 ` Hans Verkuil
2009-02-24 20:43 ` Jonathan Johnson
2009-02-25 0:06 ` Markus Rechberger
2009-02-25 3:24 ` Markus Rechberger
2009-02-25 0:01 ` Simeon Simeonov
2009-02-24 20:40 ` Rudy Zijlstra
2009-02-24 21:02 ` Michael Krufky
2009-02-24 23:37 ` hermann pitton
2009-02-25 0:52 ` Ant
2009-02-25 8:23 ` Simon Kenyon
2009-02-25 12:31 ` Simon Kenyon
2009-02-25 17:58 ` wk
2009-02-25 18:19 ` Jean-Francois Moine
2009-02-25 19:10 ` Hans Werner
2009-02-25 19:32 ` Lars Hanisch
2009-02-26 5:26 ` Mike Isely
2009-02-27 2:25 ` Magnus Damm
2009-03-01 19:51 ` Tobias Stoeber
2009-03-01 21:50 ` Adrian Pardini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090223144917.257a8f65@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox