Date: Thu, 15 Apr 2004 15:36:23 -0400
From: Jeff Garzik <jgarzik@pobox.com>
To: Andi Kleen <ak@muc.de>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
       linux-kernel@vger.kernel.org
Subject: Re: SATA support merge in 2.4.27
Message-ID: <20040415193623.GA29492@havoc.gtf.org>
References: <1Ljts-1eQ-29@gated-at.bofh.it> <m37jwhqc2u.fsf@averell.firstfloor.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <m37jwhqc2u.fsf@averell.firstfloor.org>
User-Agent: Mutt/1.4.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1266
Lines: 36

On Thu, Apr 15, 2004 at 09:24:09PM +0200, Andi Kleen wrote:
> Marcelo Tosatti <marcelo.tosatti@cyclades.com> writes:
> 
> > Jeff Garzik sent me a SATA update to be merged in 2.4.x. 
> >
> > A lot of new boxes are shipping with SATA-only disks, and its pretty bad
> > to not have a "stable" series without such industry-standard support.
> >
> > This is the last feature to be merged on 2.4.x, and only because its quite 
> > necessary.
> >
> > Any oppositions?
> 
> The big problem is that the SATA code will move some disks from
> /dev/hdX to /dev/sdX (e.g. most disks in modern intel chipsets) And
> then the boxes don't boot anymore. It's probably a bad idea to merge
> it.

Oh, this is also false for all the distro users which are _already_
using /dev/sdX for their disks.

They _have_ to patch in libata, otherwise the upstream kernel will break
their disks by changing them from /dev/hdX to /dev/sdX.

Another problem is that the upstream /dev/hdX driver locks up for a many
users, where libata does not.

	Jeff


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