public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andries Brouwer <Andries.Brouwer@cwi.nl>
To: Frediano Ziglio <freddyz77@tin.it>
Cc: Andries Brouwer <Andries.Brouwer@cwi.nl>,
	linux-kernel@vger.kernel.org,
	Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
	"Patrick J. LoPresti" <patl@users.sourceforge.net>
Subject: Re: EDD enhanchement patch
Date: Thu, 8 Jul 2004 01:24:10 +0200	[thread overview]
Message-ID: <20040707232409.GC11556@apps.cwi.nl> (raw)
In-Reply-To: <1089233331.6856.20.camel@freddy>

On Wed, Jul 07, 2004 at 10:48:51PM +0200, Frediano Ziglio wrote:

> Did anyone forget about first fields? base-port and control-port ? If
> you have an IDE disk they correspond with IDE port and with slave bit
> you can know exactly which disk is. EDD 3.0 it's not required cause it's
> EDD 2.0 (supported by most recent BIOSes).

True. Below a simple example for hda and hdb.
Yes, having EDD 2.0 helps.

> lba 0 ?? cursize 0 ?? sector > 63 ??
> IMHO this disk doesn't exist...

It was hdh: IOMEGA ZIP 100 ATAPI, ATAPI FLOPPY drive, with geometry
(probably 96/64/32, don't know why C and S are interchanged)
obtained from HDIO_GET_IDENTITY.

> For 0x84 it must be hda cause it's the first IDE.

hda or hdb. Since that system boots from SCSI there is no reason to
prefer seeing the first or second IDE disk in the BIOS setup.
(Don't know anymore what the truth was.)

> I know that some boot loader can however change disk order.

Also Linux can change disk order with boot option "ide=reverse".

Andries

----------------------------------------------------------------------------------------
disk 0: len=30 api=0x1
  flags 2, phys CHS 2100/255/63, totsecs 33736500, seclen 512
iobase 0x1f0  controlport 0x3f6 irq 14 sector_count 16 dma 32 pio 4
flags: 0xe0: LBA, Master; revision 1.1

disk 1: len=30 api=0x1
  flags 2, phys CHS 2100/255/63, totsecs 33736500, seclen 512
iobase 0x1f0  controlport 0x3f6 irq 14 sector_count 16 dma 32 pio 4
flags: 0xf0: LBA, Slave; revision 1.1

Found 2 Linux disks

hda: Size  33750864 LinuxCHS=2100/255/63 FdiskCHS=*/0/63
  LBASize  33750864 CurSize  33750864  RawCHS=33483/16/63 CurCHS=2100/255/63
hdb: Size  33750864 LinuxCHS=2100/255/63 FdiskCHS=*/255/63
  LBASize  33750864 CurSize  33750864  RawCHS=33483/16/63 CurCHS=2100/255/63

Found 2 BIOS disks

0 of 2:   33720435 sectors, C/H/S 1024 / 255 / 63 C*H*S=16450560
1 of 2:   33720435 sectors, C/H/S 1024 / 255 / 63 C*H*S=16450560


hda: 0x80
hdb: 0x81
----------------------------------------------------------------------------------------


  reply	other threads:[~2004-07-07 23:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-06 16:53 EDD enhanchement patch Frediano Ziglio
2004-07-07 17:40 ` Andries Brouwer
2004-07-07 20:48   ` Frediano Ziglio
2004-07-07 23:24     ` Andries Brouwer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-07-07  4:45 Fw: " Matt Domsch
2004-07-07 10:05 ` Frediano Ziglio
2004-07-08 12:56   ` Matt Domsch

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040707232409.GC11556@apps.cwi.nl \
    --to=andries.brouwer@cwi.nl \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --cc=freddyz77@tin.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patl@users.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox