linux-kernel - Re: Who can backport the AHCI driver to older kernels

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 4 Jun 2008 10:02:47 +0200
From:	Mikael Pettersson <mikpe@...uu.se>
To:	Rainer Koenig <Rainer.Koenig@...itsu-siemens.com>
Cc:	Mikael Pettersson <mikpe@...uu.se>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Who can backport the AHCI driver to older kernels

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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/