From: "Hitoshi Ozeki" <h-ozeki@ck2.so-net.ne.jp>
To: "'The development of GRUB 2'" <grub-devel@gnu.org>
Subject: RE: I write a patch for Japanese NEC i386 old computers.
Date: Wed, 11 Apr 2007 03:56:26 +0900 [thread overview]
Message-ID: <000001c77ba1$fb0246d0$030010ac@ozeki> (raw)
In-Reply-To: <200703282125.06774.okuji@enbug.org>
Hello, all.
Okuji-san wrote about the different(128-2048 bytes) sector-size support:
I think there are two different ways to address this issue. One way
is to use
variable sector size. This looks elegant, but this affects the disk
device
API very much. The other is to use fixed sector size, as it is for
now, but
align boundaries at a device driver level. The latter way is used
for GRUB
Legacy to support CDROM, and it works well.
I don't know which way is better. What do you think?
Maybe, The implement of GRUB legacy comes from PC architecture.
On the PC architecture BIOS, regards 512 bytes as a block. And
BIOS requires a number of blocks.
On NEC PC-9800 series, Disk BIOS requires data size in byte,
not a number of sectors. Data size must be divisible by sector size.
And the partition table starts with LBA sector 1, and its length
equals to sector size.
It's too difficult to change the API.
I think to set the GRUB_DISK_SECTOR_SIZE as the least.
(As far as I know, The least hardware sector size is 128 bytes.)
and add the variable to 'struct grub_disk'. Its variable stores
sector size(blocks per sector).
In this case, A name of 'GRUB_DISK_SECTOR_SIZE' does not match
the actual situation. I'd like its name changed.
--
Hitoshi Ozeki h-ozeki@ck2.so-net.ne.jp
next prev parent reply other threads:[~2007-04-10 19:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-25 6:33 I write a patch for Japanese NEC i386 old computers Ernest Sales
2007-03-28 15:27 ` Hitoshi Ozeki
2007-03-28 19:25 ` Yoshinori K. Okuji
2007-03-30 9:34 ` i386-pc 'chainloader' is something wrong. (RE: I write a patch for Japanese NEC i386 old computers.) Hitoshi Ozeki
2007-03-31 4:24 ` i386-pc 'chainloader' is something wrong. (RE: I write a patch forJapanese " Hitoshi Ozeki
2007-04-07 13:13 ` Yoshinori K. Okuji
2007-09-03 20:27 ` i386-pc 'chainloader' is something wrong. (RE: I write a patch for Japanese " Yoshinori K. Okuji
2007-04-10 18:56 ` Hitoshi Ozeki [this message]
2007-04-13 10:57 ` I write a patch for Japanese NEC i386 old computers Hitoshi Ozeki
2007-04-13 11:12 ` Vesa Jääskeläinen
[not found] <460a9fb4.7dc3c2f3.286c.ffffde40SMTPIN_ADDED@mx.google.com>
2007-03-29 6:39 ` Ernest Sales
2007-04-07 13:09 ` Yoshinori K. Okuji
2007-04-10 13:25 ` Hitoshi Ozeki
-- strict thread matches above, loose matches on Subject: below --
2007-03-24 15:53 小関 一志
2007-03-24 16:25 ` Hollis Blanchard
2007-03-24 19:01 ` Hitoshi Ozeki
2007-03-24 23:00 ` Yoshinori K. Okuji
2007-03-25 3:14 ` Hitoshi Ozeki
2007-03-26 4:24 ` Hitoshi Ozeki
2007-03-28 18:49 ` Yoshinori K. Okuji
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='000001c77ba1$fb0246d0$030010ac@ozeki' \
--to=h-ozeki@ck2.so-net.ne.jp \
--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.