From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Andrew Kirilenko <icedank@gmx.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Data storing
Date: Wed, 23 Apr 2003 07:36:59 -0700 [thread overview]
Message-ID: <20030423073659.7851c2a1.rddunlap@osdl.org> (raw)
In-Reply-To: <200304231528.08720.icedank@gmx.net>
On Wed, 23 Apr 2003 15:28:08 +0300 Andrew Kirilenko <icedank@gmx.net> wrote:
| > > I need to make some checks (search for particular BIOS version) in the
| > > very start of the kernel. I need to store this data (zero page is pretty
| > > good for this, I think) and access it from arch/i386/boot/setup.S,
| > > arch/i386/boot/compressed/misc.c and in some other places. Can somebody
| > > suggest me good place to put check procedure and how to pass data?
| >
| > I use 0x000001f0 (absolute) for relocating virtual disk code
| > for booting embedded systems. After Linux is up, the code remains
| > untouched. This might be a good location because the BIOS doesn't
| > use it during POST/boot and Linux (currently) leaves it alone.
| > Of course, this doesn't mean that somebody will not destroy this
| > area in the future (probably to spite you and me!!!).
|
| Yes, I know about this area, as I wrote (Documentation/i386/zero-page.txt).
| And I even know how to pass parameter from zero-page into kernel space
| (setup.c). But I need to use this parm, I fetched, in both setup.S and misc.c
| (see below). And I don't have any ideas about execute order of setup.S,
| misc.c and setup.c.
Hi,
Some of this early boot info can be found in my (somewhat old)
"Linux 2.4.x Initialization for IA-32", located at
http://www.xenotime.net/linux/linit/lin240_init_x86.html
--
~Randy
prev parent reply other threads:[~2003-04-23 14:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-23 11:59 Andrew Kirilenko
2003-04-23 12:22 ` Richard B. Johnson
2003-04-23 12:28 ` Andrew Kirilenko
2003-04-23 14:36 ` Randy.Dunlap [this message]
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=20030423073659.7851c2a1.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=icedank@gmx.net \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®