From: ron minnich <rminnich@lanl.gov>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] loading plan 9 directly from linuxbios
Date: Wed, 29 Oct 2003 09:54:11 -0700 [thread overview]
Message-ID: <Pine.LNX.4.44.0310290948120.28090-100000@maxroach.lanl.gov> (raw)
In-Reply-To: <Pine.LNX.4.44.0310290945010.28090-100000@maxroach.lanl.gov>
On Wed, 29 Oct 2003, ron minnich wrote:
> On Wed, 29 Oct 2003, David Presotto wrote:
>
> > It's good hygeine but you have to assume something. Assuming 32 bit mode
> > is already way too much, we're in 16 bit mode when entered from the normal
> > BIOS.
>
> in plan 9? I know that's the way it is in 9load, but in plan 9 it looks to
> me like it assume that 9load enters plan 9 in protected mode. 9load sets
> up protected mode as far as i can see.
foolish me, I misunderstand. Dave, you're taking this further than I
thought about. I'm always ignoring those commercial BIOSen with their
penchant of entering your code in 16-bit mode, possibly I'm blocking out
bad memories.
To start, I'm going to go with the protected-mode assumption as I want to
get the EPIA boards booting Plan 9 direct from flash. Then, later, we can
get into the lovely 16-bit issue. The problem there is Plan 9 loads at
0x100000 and that's a pain to deal with in 16-bit mode. We're going to
need a little hook in the low 640K to set those things up. It starts to
suck at that point.
ron
next prev parent reply other threads:[~2003-10-29 16:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-29 6:42 ron minnich
2003-10-29 8:08 ` Charles Forsyth
2003-10-29 9:37 ` C H Forsyth
2003-10-29 16:16 ` ron minnich
2003-10-29 16:39 ` David Presotto
2003-10-29 16:46 ` ron minnich
2003-10-29 16:54 ` ron minnich [this message]
2003-10-29 20:58 ` C H Forsyth
2003-10-29 23:17 ` ron minnich
2003-10-29 7:42 Tiit Lankots
2003-10-29 16:12 ` ron minnich
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=Pine.LNX.4.44.0310290948120.28090-100000@maxroach.lanl.gov \
--to=rminnich@lanl.gov \
--cc=9fans@cse.psu.edu \
/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).