From: Mikael Pettersson <mikpe@it.uu.se>
To: Rainer Koenig <Rainer.Koenig@fujitsu-siemens.com>
Cc: Mikael Pettersson <mikpe@it.uu.se>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Who can backport the AHCI driver to older kernels
Date: Wed, 4 Jun 2008 10:02:47 +0200 [thread overview]
Message-ID: <18502.19495.626780.26511@harpo.it.uu.se> (raw)
In-Reply-To: <200806040650.12683.Rainer.Koenig@fujitsu-siemens.com>
Rainer Koenig writes:
> Hi Mikael,
>
> Am Dienstag, 3. Juni 2008 14:07 schrieb Mikael Pettersson:
> > Redhat seems to regularly backport the entire libata layer
> > to at least 2.6.18 (RHEL5) and maybe also 2.6.9 (RHEL4).
>
> Yes indeed we get perfect support from both Red Hat and SUSE for their
> enterprise level distribution. I already got a driver kit for the
> SLES10 kernel. The problem is that the targeted market is not willing
> to use enterprise level (which means spend money for subscription)
> distros. They go for the "free" (as in free beer) distros and suffer
> from missing drivers.
a) the RHEL sources are freely available
b) lots of people and organisations grab, tweak, and build them
(including I might add many HPC sites using perfctr)
c) there's at least one no-cost binary redistribution (CentOS)
d) it's also easy to combine e.g. FC user-space with a
self-compiled RHEL kernel, at least as long as they're
closely matched (e.g. FC6 + RHEL5 is fine)
(heck, I've even run FC6 on top of a SLES10.1 kernel)
So everything's that's needed is out there.
next prev parent reply other threads:[~2008-06-04 8:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-03 10:47 Rainer Koenig
2008-06-03 11:37 ` Jan Engelhardt
2008-06-04 4:47 ` Rainer Koenig
2008-06-04 8:52 ` Nicolas Mailhot
2008-06-03 11:52 ` Frans Pop
2008-06-03 12:07 ` Mikael Pettersson
2008-06-04 4:50 ` Rainer Koenig
2008-06-04 8:02 ` Mikael Pettersson [this message]
2008-06-04 8:48 ` Gerhard Mack
2008-06-04 19:36 ` Jan-Benedict Glaw
2008-06-03 14:02 ` Mark Lord
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=18502.19495.626780.26511@harpo.it.uu.se \
--to=mikpe@it.uu.se \
--cc=Rainer.Koenig@fujitsu-siemens.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®