qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Natalia Portillo <claunia@claunia.com>
To: Kevin O'Connor <kevin@koconnor.net>
Cc: seabios@seabios.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] BIOS calls in 16bit protected mode
Date: Thu, 14 Jun 2012 04:17:19 +0100	[thread overview]
Message-ID: <A8F6330C-AE98-409B-A78C-AE8BE43DF0AB@claunia.com> (raw)
In-Reply-To: <20120614031305.GA26968@morn.localdomain>

[-- Attachment #1: Type: text/plain, Size: 2046 bytes --]

Hi Kevin,

Long time ago I read about OS/2 calling 16-bit protected mode BIOS, but the documentation didn't specified if this was constrained to the separate protected mode BIOS included by PS/2 systems or the real mode BIOS included by the same PS/2 systems and the whole rest of PC computers.

Regards,
Natalia Portillo

El 14/06/2012, a las 04:13, Kevin O'Connor escribió:

> Hi,
> 
> I am trying to determine if there are legacy applications or operating
> systems that invoke standard BIOS real-mode interrupt handlers while
> in 16bit protected mode.  (The legacy real-mode entry points - like
> "int 0x13" - not the declared 16bit protected mode entry points
> defined by the PnP and APM specs.)
> 
> I am considering changes to SeaBIOS that would make 16bit protected
> mode callers much less likely to work.  (Specifically, enhancing
> SeaBIOS to use memory in the e-segment which is unlikely to be mapped
> in protected mode.)
> 
> Most documents I've seen state that calling the real-mode entry points
> in protected mode will not work.  Though, I am aware that the PCI BIOS
> spec specifically requires this support for calls to "int 0x1a
> ah=0xb1".
> 
> The advantage of making these changes is that it will allow SeaBIOS to
> use notably less stack space and therefore be more compatible with old
> applications that call the BIOS with very little stack space.  For
> example, these changes enable DOS 1.0 to boot and run under SeaBIOS.
> 
> What would really help is pointers to applications and/or program
> images that use 16bit protected mode calls to real-mode entry points.
> Specifications or documents detailing valid or invalid uses would also
> be helpful.
> 
> For those that are willing to run tests, one can compare the standard
> SeaBIOS v1.7.0 image (for KVM/QEMU) at:
> 
> http://git.seabios.org/downloads/get/bios.bin-1.7.0.gz
> 
> to a test image with the new code at:
> 
> http://git.seabios.org/downloads/get/bios.bin-test-20120613.gz
> 
> Thanks,
> -Kevin
> 


[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 235 bytes --]

  reply	other threads:[~2012-06-14  3:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-14  3:13 [Qemu-devel] BIOS calls in 16bit protected mode Kevin O'Connor
2012-06-14  3:17 ` Natalia Portillo [this message]
2012-06-14  3:57   ` Kevin O'Connor
2012-06-14  3:58   ` Roy Tam

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=A8F6330C-AE98-409B-A78C-AE8BE43DF0AB@claunia.com \
    --to=claunia@claunia.com \
    --cc=kevin@koconnor.net \
    --cc=qemu-devel@nongnu.org \
    --cc=seabios@seabios.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;
as well as URLs for NNTP newsgroup(s).