From: wk <handygewinnspiel@gmx.de>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: linux-media@vger.kernel.org
Subject: Re: RFCv1: v4l-dvb development models & old kernel support
Date: Sat, 21 Feb 2009 12:47:57 +0100 [thread overview]
Message-ID: <499FE9ED.7050405@gmx.de> (raw)
In-Reply-To: <200902211200.45373.hverkuil@xs4all.nl>
Hans Verkuil wrote:
> Comments?
>
> Hans
>
As only beeing reader of this list.., why not simply reduce the work load by
- reducing the number of supported kernel versions to five major
versions? Currently 2.6.28 would mean down to 2.6.23,
this would be enough cover all nearly up-to-date distributions. Users
from embedded devices are anyway mostly not able to compile or use newer
drivers.
- not changing to git, already since this generates a lot of work
Not too far away dev was changed from cvs to hg, and already there some
pieces are left over (for example that api stuff).
- force users to upgrade their kernel if (breaking these backward
compat, and only if) *major* upgrades inside standard kernel would
require a very huge amount of backporting, for example that i2c stuff.
I guess such solution would help immediately.
--Winfried
next prev parent reply other threads:[~2009-02-21 11:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-21 11:00 RFCv1: v4l-dvb development models & old kernel support Hans Verkuil
2009-02-21 11:47 ` wk [this message]
2009-02-21 12:50 ` Trent Piepho
2009-02-21 23:47 ` Adam Baker
2009-02-22 0:29 ` hermann pitton
2009-02-22 1:15 ` kilgota
2009-02-22 9:57 ` Hans Verkuil
2009-02-22 13:52 ` Tobias Stöber
2009-02-22 22:16 ` kilgota
2009-02-22 10:05 ` Hans Verkuil
2009-02-22 11:29 ` Andrea Venturi
2009-02-22 17:32 ` CityK
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=499FE9ED.7050405@gmx.de \
--to=handygewinnspiel@gmx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.