linux-kernel - Re: [PATCH V2 1/4] EFI: Stash ROMs if they're not in the PCI BAR

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-next>] [day] [month] [year] [list]

Date:	Sat, 04 Aug 2012 15:44:14 +1000
From:	Francois Rigaut <frigaut@....anu.edu.au>
To:	Seth Forshee <seth.forshee@...onical.com>
CC:	Greg KH <gregkh@...uxfoundation.org>,
	Matthew Garrett <mjg59@...f.ucam.org>, matt.fleming@...el.com,
	bhelgaas@...gle.com, linux-efi@...r.kernel.org,
	linux-kernel@...r.kernel.org, x86@...nel.org,
	linux-pci@...r.kernel.org
Subject: Re: [PATCH V2 1/4] EFI: Stash ROMs if they're not in the PCI BAR

Seth,

[CC'd people, sorry we exchanged a few emails with Seth outside of the 
lists, I passed him the acpi tables and here are gmux dumps]

Allright. thanks for gmux-dump. There seems to be progress, as I can see 
the gmux dumps for the nividia-selected and intel-selected are clearly 
different (I did it twice to be sure, it checks out).
The 2 dumps are at
http://maumae.net/retina/gmux-dump_intel.dat
and
http://maumae.net/retina/gmux-dump_nvidia_only.dat
I hope you'll be able to get something from these.
Francois



On 04/08/12 13:58, Seth Forshee wrote:
> On Sat, Aug 04, 2012 at 11:34:21AM +1000, Francois Rigaut wrote:
>> Seth,
>>
>> I've put the acpi table dump in http://maumae.net/retina/acpi_tables.tgz
> The ACPI stuff for the gmux looks exactly the same as for the machine
> I've got. The I/O range is still 0x700 to 0x7ff.
>
>> As far as the mem dump, I've done it but can not see any difference
>> (between case where one or the other graphic card are selected) in
>> the first 3000 bytes. Not sure I'm doing that well though. I'm just
>> dd'ing /dev/mem with
>> dd bs=1000 count=3 if=/dev/mem of=some_file
>> Am I addressing the right memory or is the switch going to be (or
>> likely to be) somewhere else?
> That's going to access sytem memory, not the I/O space for the gmux. Try
> the attached instead. It's going to output the raw binary, so if you
> want to view the output do something like
>
>   gmux-dump | xxd -g1
>
> Seth

--
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/