From: Mihai Moldovan <ionic@ionic.de>
To: grub-devel@gnu.org
Subject: Re: Legacy Firmware/INT 13H supporting >512 byte sectors?
Date: Fri, 17 Aug 2018 20:01:11 +0200 [thread overview]
Message-ID: <4858ff1e-0788-34c3-8e46-eeb2aed241bb@ionic.de> (raw)
In-Reply-To: <CAEaD8JNum6fhS1JZ6Vt99n=GHmmQ7kP1wo3rjy=ObTMgg+i2fA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1013 bytes --]
[resent to list, since I forgot to add a CC header]
* On 08/17/2018 06:11 PM, Vladimir 'phcoder' Serbinenko wrote:
> Sure. Any BIOS able to read CD supports 2K sectors.
> If you mean HDD then I have never seen one. I wrote support for non-512B sectors
> in GRUB but so far it's untested as I couldn't find such a BIOS
Ah, of course. CD sectors are 2K big. Yeah, that makes sense.
I meant HDD sectors, yes.
My firmware is doing weird things: it always reports a sector size of 512 bytes,
reads and outputs data in 512 byte chunks, but sector addressing is actually
HDD-dependent (i.e., for 4Kn drives 4K-based).
I'll work around that using some heuristic, but that's only part of the problem.
The bigger issue will probably be the boot image, which likely is too small to
incorporate sophisticated code. I guess I could trick THAT into behaving
correctly by spreading the core image file out over several sectors and only
using the first 512 bytes of each sector.
Mihai
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 898 bytes --]
next prev parent reply other threads:[~2018-08-17 18:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-17 14:59 Legacy Firmware/INT 13H supporting >512 byte sectors? Mihai Moldovan
2018-08-17 16:11 ` Vladimir 'phcoder' Serbinenko
2018-08-17 18:01 ` Mihai Moldovan [this message]
2018-08-17 18:07 ` Toomas Soome
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=4858ff1e-0788-34c3-8e46-eeb2aed241bb@ionic.de \
--to=ionic@ionic.de \
--cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.