From: "Sluder, Charles" <Charles.Sluder@UNISYS.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] Problem with elilo 3.3a
Date: Sat, 15 Feb 2003 06:28:09 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805859@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805846@msgid-missing>
Looks like it might be a problem in EFI. I traced through BS->GetMemMap()
and the corruption in the returned memory map are left over data in fields
that are not being filled in by the function call.
-chuck
-----Original Message-----
From: David Mosberger [mailto:davidm@napali.hpl.hp.com]
Sent: Friday, February 14, 2003 12:35 AM
To: eranian@hpl.hp.com
Cc: linux-ia64@linuxia64.org; David Mosberger
Subject: Re: [Linux-ia64] Problem with elilo 3.3a
>>>>> On Thu, 13 Feb 2003 23:28:28 -0800, Stephane Eranian
<eranian@frankl.hpl.hp.com> said:
Stephane> The bootloader obtains the memory map from EFI. The map is
Stephane> stored into a region specifically allocated by elilo. The
Stephane> bootparam structure passes the address of the table and
Stephane> its size to the kernel.
Ah, that's how I thought it worked. I misunderstood your previous
mail (on re-reading it, it's clear though... ;-).
Thanks,
--david
_______________________________________________
Linux-IA64 mailing list
Linux-IA64@linuxia64.org
http://lists.linuxia64.org/lists/listinfo/linux-ia64
next prev parent reply other threads:[~2003-02-15 6:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-14 3:15 [Linux-ia64] Problem with elilo 3.3a Sluder, Charles
2003-02-14 6:58 ` Stephane Eranian
2003-02-14 7:09 ` David Mosberger
2003-02-14 7:28 ` Stephane Eranian
2003-02-14 7:34 ` David Mosberger
2003-02-14 18:33 ` Sluder, Charles
2003-02-15 6:28 ` Sluder, Charles [this message]
2003-02-18 18:23 ` Stephane Eranian
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=marc-linux-ia64-105590709805859@msgid-missing \
--to=charles.sluder@unisys.com \
--cc=linux-ia64@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