Date: Sun, 16 Mar 1997 19:14:33 -0700 (MST) From: Don Yuniskis <dgy@rtd.com> To: terry@lambert.org (Terry Lambert) Cc: bde@zeta.org.au, dgy@rtd.com, helbig@MX.BA-Stuttgart.De, hackers@FreeBSD.ORG Subject: Re: wd driver questions Message-ID: <199703170214.TAA16040@seagull.rtd.com> In-Reply-To: <199703162105.OAA06259@phaeton.artisoft.com> from "Terry Lambert" at Mar 16, 97 02:05:25 pm
next in thread | previous in thread | raw e-mail | index | archive | help
It seems that Terry Lambert said: > > > >> And, how (if at all) does the geometry written to the disklabel > > >> figure into the operation/calculations of the driver? > > > > > >As far as I could decipher from the driver code (wd.c) the probed geometry > > >is used only to read the label. > > > > No, the probed geometry is used for everything in the driver. > > Why are we using a probed geometry insted of the geometry reported > from the INT 0x13 call in the boot blocks? The idea that the drive > could be INIT'ed to a different geometry is valid. This is the heart of the "problem" that I was discussing. My disks, for example, are INITed by the system ROMs to a particular geometry. *Then* the probe (actually, the attach()) queries the drive and reINITs the drive for the *default* drive geometry (which, in my case, is very different from the "BIOS" geometry. See my followup (long) post on this... --don
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199703170214.TAA16040>