From: Frediano Ziglio <freddyz77@tin.it>
To: Andries Brouwer <Andries.Brouwer@cwi.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.x partition breakage and dual booting
Date: Thu, 03 Jun 2004 14:30:33 +0200 [thread overview]
Message-ID: <1086265833.3988.13.camel@freddy> (raw)
In-Reply-To: <20040603103907.GV23408@apps.cwi.nl>
Il gio, 2004-06-03 alle 12:39, Andries Brouwer ha scritto:
> On Thu, Jun 03, 2004 at 08:51:35AM +0200, Frediano Ziglio wrote:
>
> > Actually I'm writing two patch:
> > - extending EDD code to provide DPTE informations and signature for all
> > drives
> > - modify IDE code to match BIOS disks.
>
> That second part is undesirable.
> The Linux IDE code is not interested in getting a conjecture about
> how other operating systems would name or number the disks.
>
> > How to match BIOS with Linux?
>
> It is impossible. But you can easily do a 95% job.
>
> > I think it's important to know BIOS point of view. Linux provide these
> > information so we have two choices to solve the problem:
> > - correct the informations we return
> > - do not return anything and let user space programs do the job!
>
> Yes, leave it to user space. That is what we do today.
>
Yes and not... HDIO_GETGEO still exists and report inconsistent
informations. IMHO should be removed. I know this breaks some existing
programs however these programs do not actually works correctly.
> > - EDD 2.0. I don't understand why Linux code int 41h/46h and ignore
> > these informations.
>
> Long ago, long before EDD, disks actually had a geometry, and it was
> necessary to find it in order to do I/O to e.g. MFM disks.
> Today disk geometry is not related to the disk, but to the BIOS.
> The kernel has no need to know it.
>
EDD 2.0 information consists of
- base port
- control port
- flags (slave or not)
- others (DMA, etc)
In order to be able (for user space programs) to match these
informations user space programs should be able to read at last base
port of hdX disks.
freddy77
next prev parent reply other threads:[~2004-06-03 12:30 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-30 18:04 2.6.x partition breakage and dual booting Jeff Garzik
2004-05-30 18:36 ` Andries Brouwer
2004-05-30 18:56 ` Jeff Garzik
2004-05-30 20:03 ` Andries Brouwer
2004-05-30 20:47 ` viro
2004-05-30 21:06 ` Andries Brouwer
2004-05-30 21:08 ` Andreas Schwab
2004-05-30 21:14 ` viro
2004-05-30 21:02 ` Patrick J. LoPresti
2004-05-30 22:20 ` Andries Brouwer
[not found] ` <mit.lcs.mail.linux-kernel/20040530222001.GD4681@apps.cwi.nl>
2004-05-30 22:54 ` Patrick J. LoPresti
2004-05-31 18:08 ` Tomas Szepe
2004-05-31 19:19 ` Frediano Ziglio
2004-05-31 20:06 ` Patrick J. LoPresti
2004-05-31 21:03 ` Sean Estabrooks
2004-06-01 15:10 ` Patrick J. LoPresti
2004-06-01 23:55 ` Andries Brouwer
2004-06-02 13:02 ` Patrick J. LoPresti
2004-06-02 15:00 ` Matt Domsch
2004-06-02 21:22 ` [PATCH] Better names for EDD legacy_* fields Patrick J. LoPresti
2004-06-02 23:03 ` Andries Brouwer
2004-06-02 23:38 ` Patrick J. LoPresti
2004-06-02 23:53 ` [PATCH] Use decimal instead of hex for EDD values Patrick J. LoPresti
2004-06-01 16:28 ` 2.6.x partition breakage and dual booting Stephen Hemminger
2004-06-03 6:51 ` Frediano Ziglio
2004-06-03 10:39 ` Andries Brouwer
2004-06-03 12:30 ` Frediano Ziglio [this message]
2004-06-03 14:35 ` Bartlomiej Zolnierkiewicz
2004-06-03 15:11 ` Andries Brouwer
2004-06-03 14:46 ` Patrick J. LoPresti
2004-06-03 15:32 ` Bartlomiej Zolnierkiewicz
2004-06-03 15:55 ` Patrick J. LoPresti
2004-05-30 19:35 ` Patrick J. LoPresti
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=1086265833.3988.13.camel@freddy \
--to=freddyz77@tin.it \
--cc=Andries.Brouwer@cwi.nl \
--cc=linux-kernel@vger.kernel.org \
/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