linux-kernel - Re: [RFC] Best place/method to determine BIOS version?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 11 Jun 2014 09:55:48 +0100
From:	Matt Fleming <matt@...sole-pimps.org>
To:	Alex Thorlton <athorlton@....com>
Cc:	Linux EFI <linux-efi@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Borislav Petkov <bp@...e.de>, Russ Anderson <rja@....com>
Subject: Re: [RFC] Best place/method to determine BIOS version?

On Mon, 09 Jun, at 03:00:17PM, Alex Thorlton wrote:
> 
> I think the problem is that I really need to be doing this at a point
> where I can directly use physical addressing (the function pointer that
> we have stored in efi.uv_systab contains the physical address of our
> function) - at least that's the idea I get from our BIOS guys, but I
> really don't know what I'm talking about here :)

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()?

-- 
Matt Fleming, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/