From: Tero Kaarlela <turo.kaarlela@co.inet.fi>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] No support for non-continuous I/O map mode
Date: Wed, 06 Apr 2005 11:46:22 +0300 [thread overview]
Message-ID: <4253A1DE.6060005@co.inet.fi> (raw)
Hi,
I am trying to get OS/2 PPC edition ro run under Qemu. I have made few
hack to bootloader + openhackware to get it running so far things I had
to do:
1. Hex edit Prep partition address 0x200 to point to beginning of Prep
Partition(Conventional firmware handles Partition map differently than OF)
2. Modify machine model at openhackware bootinfos.c(This Bootloader
has few ASCII strings inside code and it compares them to residual data
model string)
3. Now I have got Qemu -nographic -dummy-net -prep to boot it to
this point where Qemu reports: No support for non-continuous I/O map mode
My question is: Is there going to be support for this soon(is it
planned)? If not can someone tell me how can I start trying
implementing it?
Tero Kaarlela
reply other threads:[~2005-04-06 8:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4253A1DE.6060005@co.inet.fi \
--to=turo.kaarlela@co.inet.fi \
--cc=qemu-devel@nongnu.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).