Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 9 Mar 2003 15:23:28 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 9 Mar 2003 15:23:28 -0500 Received: from tmr-02.dsl.thebiz.net ([216.238.38.204]:47623 "EHLO gatekeeper.tmr.com") by vger.kernel.org with ESMTP id ; Sun, 9 Mar 2003 15:23:26 -0500 Date: Sun, 9 Mar 2003 15:30:08 -0500 (EST) From: Bill Davidsen To: Andries.Brouwer@cwi.nl cc: Linux Kernel Mailing List Subject: Re: ide-problem still with 2.4.21-pre5-ac1 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1090 Lines: 28 On Sun, 9 Mar 2003 Andries.Brouwer@cwi.nl wrote: > > So you are saying the same thing I am, are you not? > > The problem was one about translation, not about capacity. The *problem* was translation, the proposed *solution* was using the BIOS values in preference to drive values would include capacity. Or I misread the intent (or code). I would think that the capacity should code from the drive, if the BIOS geometry is clearly wrong from that capacity (no, I didn't define that) then using it will/may cause problems in applications and perhaps the kernel, although LBA should be used and geometry not an issue. Feel free to read the original post otherwise, I thought using the BIOS data was the intent, period. -- bill davidsen CTO, TMR Associates, Inc Doing interesting things with little computers since 1979. - 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/