From: Molle Bestefich <molle.bestefich@gmail.com>
To: Matthew Garrett <mgarrett@chiark.greenend.org.uk>
Cc: ataraid-list@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: IDE HPA
Date: Fri, 2 Sep 2005 18:24:20 +0200 [thread overview]
Message-ID: <62b0912f05090209242ad72321@mail.gmail.com> (raw)
In-Reply-To: <E1EBCdS-00064p-00@chiark.greenend.org.uk>
Alan Cox wrote:
> > If one does not care to use the HPA, one should disable it in the
> > BIOS entirely, so that everywhere (!) the entire disk is seen.
>
> And in the real world BIOSes don't get updated often
> by vendors let alone by users.
I meant the BIOS setup screen, not a firmware update...
Supposedly the BIOS can change the bounds of the HPA with special ATA commands..
Matthew Garrett wrote:
> Molle Bestefich wrote:
> > If HPA were exposed as /dev/.../hpa then it wouldn't be possible to
> > create such a filesystem. I'm guessing it's not possible with Windows
> > either, or with any BIOS-based OS.
>
> Such filesystems already exist. Changing this behaviour now would break
> existing setups.
Not if, as proposed, there was a kernel switch to enable including the
HPA in the disc area.
Also those who has such filesystems {c,sh}ould disable HPA in their
BIOS (hopefully).
next prev parent reply other threads:[~2005-09-02 16:24 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87941b4c05082913101e15ddda@mail.gmail.com>
[not found] ` <200508300859.19701.tennert@science-computing.de>
2005-08-30 15:52 ` IDE HPA Greg Felix
2005-08-30 16:16 ` Bartlomiej Zolnierkiewicz
2005-08-30 17:05 ` Alan Cox
2005-08-31 0:30 ` Bartlomiej Zolnierkiewicz
2005-08-30 16:38 ` Alan Cox
[not found] ` <87941b4c050830095111bf484e@mail.gmail.com>
2005-09-02 7:27 ` Molle Bestefich
2005-09-02 13:05 ` Alan Cox
2005-09-02 13:33 ` Molle Bestefich
2005-09-02 14:35 ` Matthew Garrett
2005-09-02 16:24 ` Molle Bestefich [this message]
2005-09-02 17:05 ` Alan Cox
2005-09-02 17:44 ` Molle Bestefich
2005-09-02 18:04 ` Matthew Garrett
2005-09-02 18:09 ` Peter Jones
2005-09-02 18:59 ` Alan Cox
2005-09-02 19:14 ` Peter Jones
2005-09-02 20:22 ` Alan Cox
2005-09-02 21:14 ` Peter Jones
2005-09-03 0:05 ` Alan Cox
2005-09-03 23:31 ` Jeff Garzik
2005-09-07 14:52 ` Bill Davidsen
2005-09-03 0:03 ` Pekka Pietikainen
2005-09-02 18:57 ` Alan Cox
2005-09-02 17:57 ` Vojtech Pavlik
2005-09-02 14:50 ` Alan Cox
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=62b0912f05090209242ad72321@mail.gmail.com \
--to=molle.bestefich@gmail.com \
--cc=ataraid-list@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgarrett@chiark.greenend.org.uk \
/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