From: Christian Franke <Christian.Franke@t-online.de>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: status grub2 port of grub-legasy map command
Date: Sun, 31 May 2009 21:35:52 +0200 [thread overview]
Message-ID: <4A22DC18.7000709@t-online.de> (raw)
In-Reply-To: <d7ead6de0905310900k4c59b0ddq102cc4d2fccfa5d2@mail.gmail.com>
Vladimir 'phcoder' Serbinenko wrote:
>>
>> Do not do this. Some BIOS functions (like ah=08h) return data in dl.
>> Clients should not expect data in registers to be preserved across
>> interrupt calls. I don't know if there is something like a 8086/PC-BIOS
>> ABI document that we can find to confirm the non-preservation of dl, but
>> the FreeDOS MBR should be fixed then.
>>
> Thank you for pointing ah=8 function
> AFAIK there is no normative reference. The source which was mainly
> used for long years is helppc and it states following:
> - registers DS, BX, CX and DX are preserved
> (http://heim.ifi.uio.no/~stanisls/helppc/int_13.html)
> But now this reference is terribly outdated.
> SeaBIOS preserves %dl too
>
T13 EDD provides a probably more up to date documentation of int13.
There was no requirement to preserve registers is in EDD (2000) and
EDD-2 (2002). It appeared in EDD-3 (2004) and is still in first EDD-4
draft (2009):
"The values in all registers that are not explicitly defined in the
following sections shall be preserved at the completion of each function
call"
From Section 8 of: BIOS Enhanced Disk Drive Services - 3 (T13/1572D
Revision 3)
Fortunately, T13 docs are (unlike T10 and SATA-IO) still publicly available:
http://www.t13.org/Documents/MinutesDefault.aspx?DocumentType=4&DocumentStage=2
--
Regards,
Christian Franke
next prev parent reply other threads:[~2009-05-31 19:36 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 1:03 status grub2 port of grub-legasy map command John Stanley
2009-04-14 7:33 ` Felix Zielcke
2009-04-14 9:21 ` John Stanley
2009-04-14 9:04 ` phcoder
2009-04-15 8:55 ` John Stanley
2009-04-15 9:06 ` phcoder
2009-04-15 9:30 ` John Stanley
2009-04-15 9:34 ` phcoder
2009-04-17 21:20 ` Javier Martín
2009-04-17 21:42 ` Vladimir Serbinenko
2009-04-17 23:12 ` John Stanley
2009-04-17 23:46 ` Vladimir Serbinenko
2009-04-18 0:01 ` John Stanley
2009-04-18 2:18 ` Javier Martín
2009-04-18 2:36 ` Vladimir Serbinenko
2009-05-03 0:02 ` Javier Martín
2009-05-03 9:17 ` Vladimir 'phcoder' Serbinenko
2009-05-03 19:45 ` Pavel Roskin
2009-05-03 20:59 ` Pavel Roskin
2009-05-03 23:37 ` Javier Martín
2009-05-04 3:57 ` Pavel Roskin
2009-05-06 18:41 ` Javier Martín
2009-05-09 9:17 ` Vladimir 'phcoder' Serbinenko
2009-05-09 13:27 ` Javier Martín
2009-05-09 14:04 ` Vladimir 'phcoder' Serbinenko
2009-05-09 15:42 ` Javier Martín
2009-05-10 11:47 ` Vladimir 'phcoder' Serbinenko
2009-05-10 17:03 ` Javier Martín
2009-05-14 1:51 ` Pavel Roskin
2009-05-14 6:49 ` Vladimir 'phcoder' Serbinenko
2009-05-14 14:03 ` Pavel Roskin
2009-05-14 15:01 ` Vladimir 'phcoder' Serbinenko
2009-05-14 18:17 ` Pavel Roskin
2009-05-14 18:38 ` Vladimir 'phcoder' Serbinenko
2009-05-15 22:46 ` Javier Martín
2009-05-30 15:28 ` Vladimir 'phcoder' Serbinenko
2009-05-31 10:01 ` Javier Martín
2009-05-31 11:36 ` Vladimir 'phcoder' Serbinenko
2009-05-31 12:48 ` Javier Martín
2009-05-31 16:00 ` Vladimir 'phcoder' Serbinenko
2009-05-31 16:26 ` Javier Martín
2009-05-31 18:05 ` Vladimir 'phcoder' Serbinenko
2009-05-31 18:50 ` Javier Martín
2009-05-31 19:00 ` Vladimir 'phcoder' Serbinenko
2009-05-31 19:35 ` Christian Franke [this message]
2009-05-31 20:13 ` Javier Martín
2009-06-01 9:53 ` Vladimir 'phcoder' Serbinenko
2009-06-01 20:41 ` Javier Martín
2009-06-01 21:45 ` Vladimir 'phcoder' Serbinenko
2009-06-04 18:56 ` Vladimir 'phcoder' Serbinenko
2009-06-05 13:55 ` Vladimir 'phcoder' Serbinenko
2009-06-05 14:06 ` Javier Martín
2009-05-14 6:53 ` Vladimir 'phcoder' Serbinenko
2009-05-14 14:11 ` Pavel Roskin
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=4A22DC18.7000709@t-online.de \
--to=christian.franke@t-online.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.