From: Alex Thorlton <athorlton@sgi.com>
To: Matt Fleming <matt@console-pimps.org>
Cc: Alex Thorlton <athorlton@sgi.com>,
Linux EFI <linux-efi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>, Borislav Petkov <bp@suse.de>,
Russ Anderson <rja@sgi.com>
Subject: Re: [RFC] Best place/method to determine BIOS version?
Date: Wed, 11 Jun 2014 12:30:22 -0500 [thread overview]
Message-ID: <20140611173022.GD3275@sgi.com> (raw)
In-Reply-To: <20140611085548.GB26290@console-pimps.org>
On Wed, Jun 11, 2014 at 09:55:48AM +0100, Matt Fleming wrote:
> Can't you use either early_ioremap() or ioremap() (depending on when you
> want to access the physical address), perhaps coupled with
> efi_call_phys()?
I had actually tried that exact approach, but I think the problem is
that I need to remap both the function code, and the data that it needs
to access, and the pointers get clobbered in that process. The pointers
work fine in direct physical mode, and they work fine after being mapped
into the EFI page table in virtual mode, but I think there's some magic
in there that helps fix them up when set_virtual_address_map is called,
which isn't getting done when I try to remap manually.
I'll look into this approach a bit more to be absolutely sure that it
won't work, but I hadn't had any luck so far.
- Alex
prev parent reply other threads:[~2014-06-11 17:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 20:00 [RFC] Best place/method to determine BIOS version? Alex Thorlton
[not found] ` <20140609200017.GD2700-sJ/iWh9BUns@public.gmane.org>
2014-06-10 8:03 ` Borislav Petkov
[not found] ` <20140610080300.GA28607-fF5Pk5pvG8Y@public.gmane.org>
2014-06-10 20:44 ` efi_call on SGI Borislav Petkov
[not found] ` <20140610204414.GB29302-fF5Pk5pvG8Y@public.gmane.org>
2014-06-11 17:32 ` Alex Thorlton
2014-06-11 8:55 ` [RFC] Best place/method to determine BIOS version? Matt Fleming
2014-06-11 17:30 ` Alex Thorlton [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=20140611173022.GD3275@sgi.com \
--to=athorlton@sgi.com \
--cc=bp@suse.de \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@console-pimps.org \
--cc=rja@sgi.com \
/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