Re: [ANNOUNCE] "iswraid" (ICHxR ataraid sub-driver) for 2.4.29

From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
	Martins Krikis <mkrikis@yahoo.com>,
	marcelo.tosatti@cyclades.com, linux-kernel@vger.kernel.org,
	alan@lxorguk.ukuu.org.uk
Subject: Re: [ANNOUNCE] "iswraid" (ICHxR ataraid sub-driver) for 2.4.29
Date: Sun, 6 Feb 2005 16:19:44 +0100	[thread overview]
Message-ID: <58cb370e05020607197db9ecf4@mail.gmail.com> (raw)
In-Reply-To: <420631BF.7060407@pobox.com>

On Sun, 06 Feb 2005 10:03:27 -0500, Jeff Garzik <jgarzik@pobox.com> wrote:
> Arjan van de Ven wrote:
> >>I consider it not a new feature, but a missing feature, since otherwise
> >>user data cannot be accessed in the RAID setups.
> >
> >
> > the same is true for all new hardware drivers and hardware support
> > patches. And for new DRM (since new X may need it) and new .. and
> > new ... where is the line?
> >
> > for me a deep maintenance mode is about keeping existing stuff working;
> > all new hw support and derivative hardware support (such as this) can be
> > pointed at the new stable series... which has been out for quite some
> > time now..
> 
> Red herring.
> 
> 2.4.x has ICH5/6 support -- but is missing the RAID support component.
> 
> We are talking about hardware that is ALREADY supported by 2.4.x kernel,
> not new hardware.
> 
> We are also talking about inability to access data on hardware supported
> by 2.4.x, not something that can easily be ignored or papered over with
> a compatibility mode.

the same arguments can be used for crypto support etc.,
answer is - use 2.6.x or add extra patches to get 2.4.x working