This message generated a parse failure. Raw output follows here. Please use 'back' to navigate. From devnull@lkml.org Fri Apr 19 08:48:38 2024 Delivery-date: Thu, 16 Feb 2006 13:34:27 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030592AbWBPMdt (ORCPT ); Thu, 16 Feb 2006 07:33:49 -0500 Received: from odyssey.analogic.com ([204.178.40.5]:40710 "EHLO odyssey.analogic.com") by vger.kernel.org with ESMTP id S1030587AbWBPMds convert rfc822-to-8bit (ORCPT ); Thu, 16 Feb 2006 07:33:48 -0500 Received: from chaos.analogic.com ([10.112.50.11]) by phoenix.analogic.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 16 Feb 2006 07:33:39 -0500 Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Received: from chaos.analogic.com (localhost [127.0.0.1]) by chaos.analogic.com (8.12.11/8.12.11) with ESMTP id k1GCXdA9020326; Thu, 16 Feb 2006 07:33:39 -0500 Received: (from linux-os@localhost) by chaos.analogic.com (8.12.11/8.12.11/Submit) id k1GCXc6u020325; Thu, 16 Feb 2006 07:33:38 -0500 In-Reply-To: <43F3AEAA.4080309@cfl.rr.com> X-OriginalArrivalTime: 16 Feb 2006 12:33:39.0958 (UTC) FILETIME=[371BC160:01C632F5] content-class: urn:content-classes:message Subject: Re: RFC: disk geometry via sysfs Date: Thu, 16 Feb 2006 07:33:38 -0500 Message-Id: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: RFC: disk geometry via sysfs Thread-Index: AcYy9Tclz4GMvX9IT5ieTXcKmMGRCQ== References: <43EC8FBA.1080307@bfh.ch> <43F0B484.3060603@cfl.rr.com> <43F0D7AD.8050909@bfh.ch> <43F0DF32.8060709@cfl.rr.com> <43F206E7.70601@bfh.ch> <43F21F21.1010509@cfl.rr.com> <43F2E8BA.90001@bfh.ch> <58cb370e0602150051w2f276banb7662394bef2c369@mail.gmail.com> <11 From: "linux-os \(Dick Johnson\)" To: "Phillip Susi" Cc: "Alan Cox" , "Seewer Philippe" , "Bartlomiej Zolnierkiewicz" , Reply-To: "linux-os \(Dick Johnson\)" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 15 Feb 2006, Phillip Susi wrote: > linux-os (Dick Johnson) wrote: >> Heads start at 0. Sectors start at 1. Cylinders start at 0. >> A "lower head" than allowed would be 0xff so the BIOS wouldn't >> know it was "lower". The BIOS doesn't look at the MBR for >> normal read/write access! Only while booting does it >> read the first sector of the master boot record (MBR) into >> the appropriate physical place (0x7c00). Then it checks to see >> if there is an 0xaa55 as the last word in the sector. If so, >> it executes code starting at offset zero. Modern BIOS don't >> even check the "boot flag" because it may be wrong, preventing >> a boot. >> > > I'm talking about the geometry of the disk. If the disk has 16 sectors > and 8 heads, then the maximum value allowed for any valid address is 16 > in the sector field and 7 in the heads field. This influences the > translation to/from LBA. A sector with LBA of 1234 would have a CHS > address using this geometry of 9/5/3. If the disk reports a geometry of > x/8/16 but the bios is using a geometry of x/255/63, then when you pass > 9/5/3 to int 13 it will fetch LBA 144902 which is clearly not going to > give you what you wanted. > Wrong! The disk gets an OFFSET! It doesn't care how that OFFSET is obtained. That OFFSET is the sum of some variables. Some start at 0 and some start at 1. The BIOS takes these PHONY things, without checking to see if they "fit" in some pre-conceived notion of "geometery" and sums them all up to make an OFFSET. The C/H/S stuff started and ENDED with the ST-506 interface. PERIOD. [Snipped rest] Cheers, Dick Johnson Penguin : Linux version 2.6.13.4 on an i686 machine (5589.66 BogoMips). Warning : 98.36% of all statistics are fiction. _  **************************************************************** The information transmitted in this message is confidential and may be privileged. Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@analogic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them. Thank you. - 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/