From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Slightly OT but interesting nonetheless...
Date: Tue, 27 Sep 2011 10:10:33 -0700 [thread overview]
Message-ID: <CAK2H+ecSrhLcGvAwEG32h16wTf=Rn3F0NWQBsZpSUDdgnbh_XQ@mail.gmail.com> (raw)
In-Reply-To: <j5ri2a$jnd$1@dough.gmane.org>
On Mon, Sep 26, 2011 at 9:05 PM, Grant Edwards
<grant.b.edwards@gmail.com> wrote:
<SNIP>
>> Contribute your drivers upstream. When the devs change an API, they'll
>> update your code for you.
>
> That sounds good, but in practice it doesn't work.
>
> 1) The kernel developers don't support any existing customers. Bugs
> are only fixed for customers who are willing to run the next
> kernel verison. I've got customers that are still running 2.4
> kernels. 2.6.18 is still widely used. Will the kernel developers
> add new features, support for new hardware, or fix bugs for those
> customers. Not a chance.
>
Grant,
Check out the Long Term Stable family of kernels. It's a bit hard
right now due to the status of the kernel web site being
down/changing. However you can see here at Andi Kleen's blog that he's
interested in participation:
http://halobates.de/blog/p/38
I know from watching the lkml list over the years that updates to long
term stable kernels come out periodically and do include fixes. I
don't know about new drivers, but reading Andi's blog it seems he's
potentially open to receiving driver updates from folks interested in
having the driver included.
Hope this helps,
Mark
next prev parent reply other threads:[~2011-09-27 17:12 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 19:37 [gentoo-user] Slightly OT but interesting nonetheless pk
2011-09-26 19:44 ` Michael Mol
2011-09-26 20:13 ` [gentoo-user] " Grant Edwards
2011-09-27 0:12 ` Michael Orlitzky
2011-09-27 4:05 ` Grant Edwards
2011-09-27 16:54 ` Volker Armin Hemmann
2011-09-27 17:07 ` Michael Mol
2011-09-27 17:22 ` Volker Armin Hemmann
2011-09-27 17:43 ` Michael Mol
2011-09-27 18:24 ` Mark Knecht
2011-09-27 18:33 ` Michael Mol
2011-09-27 18:41 ` Mark Knecht
2011-09-27 17:03 ` Michael Orlitzky
2011-09-27 17:10 ` Mark Knecht [this message]
2011-09-27 16:52 ` Volker Armin Hemmann
2011-09-28 14:44 ` James
2011-09-28 16:54 ` Volker Armin Hemmann
2011-09-29 13:10 ` Indi
2011-09-28 17:15 ` Grant Edwards
2011-09-29 16:19 ` Volker Armin Hemmann
2011-09-29 16:26 ` Joerg Schilling
2011-09-29 16:30 ` Michael Mol
2011-09-29 16:55 ` Grant Edwards
2011-09-29 16:56 ` Grant Edwards
2011-09-29 0:27 ` Peter Humphrey
2011-09-29 16:20 ` Volker Armin Hemmann
2011-09-30 0:45 ` Adam Carter
2011-09-30 1:04 ` Peter Humphrey
2011-09-30 1:34 ` Adam Carter
2011-09-30 2:29 ` Dale
2011-09-30 2:47 ` Michael Mol
2011-09-30 4:10 ` Dale
2011-09-26 20:16 ` [gentoo-user] " James Broadhead
2011-09-26 21:06 ` Jonas de Buhr
2011-09-26 21:45 ` Alan McKinnon
2011-09-26 22:21 ` Peter Humphrey
2011-09-27 7:45 ` Mick
2011-09-26 21:00 ` Canek Peláez Valdés
2011-09-26 22:42 ` Dale
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='CAK2H+ecSrhLcGvAwEG32h16wTf=Rn3F0NWQBsZpSUDdgnbh_XQ@mail.gmail.com' \
--to=markknecht@gmail.com \
--cc=gentoo-user@lists.gentoo.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