From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jens Axboe Subject: Re: What's in libata-dev.git Date: Mon, 11 Sep 2006 17:06:15 +0200 Message-ID: <20060911150615.GB4955@suse.de> References: <20060911132250.GA5178@havoc.gtf.org> <45056627.7030202@ru.mvista.com> <450566A2.1090009@garzik.org> <450568F3.3020005@ru.mvista.com> <1157986974.23085.147.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from brick.kernel.dk ([62.242.22.158]:51041 "EHLO kernel.dk") by vger.kernel.org with ESMTP id S932291AbWIKPH6 (ORCPT ); Mon, 11 Sep 2006 11:07:58 -0400 Content-Disposition: inline In-Reply-To: <1157986974.23085.147.camel@localhost.localdomain> Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: Alan Cox Cc: Sergei Shtylyov , Jeff Garzik , linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org, Andrew Morton , Linus Torvalds On Mon, Sep 11 2006, Alan Cox wrote: > Ar Llu, 2006-09-11 am 17:47 +0400, ysgrifennodd Sergei Shtylyov: > > It's not likely I'll be able to try it. But I'm absolutely sure that drive > > aborted the read commands with the sector count of 0 (i.e. 256 actually). The > > exact model was IBM DHEA-34331. > > Several people reported this problem when we tried 256 years ago in > drivers/ide. You might want to do 256 for SATA Jeff but please don't do > 256 for PATA. Reading specs is too hard for some people ;) > > Some drives abort the xfer, some just choked. Ehm it's 256 now and it has been for a looong time. The few cases I've seen where people claimed it broke, turned out to be something else. I've still haven't seen a valid report on this. It might sound obscure that 0 means 256 sectors, but it's really not a hidden obscure fact - people do know. I'm all for being conservative where it matters, but I'm siding with Jeff on this one. I suspect that Windows uses 256 as well, which basically means that we're in the clear. -- Jens Axboe