mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Francois Rigaut <frigaut@mso.anu.edu.au>
To: Seth Forshee <seth.forshee@canonical.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	Matthew Garrett <mjg59@srcf.ucam.org>,
	matt.fleming@intel.com, bhelgaas@google.com,
	linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
	x86@kernel.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH V2 1/4] EFI: Stash ROMs if they're not in the PCI BAR
Date: Sat, 04 Aug 2012 15:44:14 +1000	[thread overview]
Message-ID: <501CB6AE.3000400@mso.anu.edu.au> (raw)
In-Reply-To: <20120804035844.GA31711@thinkpad-t410>

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


  parent reply	other threads:[~2012-08-04  5:44 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-27 16:52 Matthew Garrett
2012-07-27 16:52 ` [PATCH V2 2/4] PCI: Add pcibios_add_device Matthew Garrett
2012-07-27 16:52 ` [PATCH V2 3/4] PCI: Add support for non-BAR ROMs Matthew Garrett
2012-07-29 21:49   ` [PATCH] Fix priority of non-BAR ROM data David Woodhouse
2012-07-29 21:53     ` Matthew Garrett
2012-08-01 14:20       ` Bjorn Helgaas
2012-08-01 14:26         ` Matthew Garrett
2012-07-27 16:52 ` [PATCH V2 4/4] X86: Use PCI setup data Matthew Garrett
2012-07-31 22:32 ` [PATCH V2 1/4] EFI: Stash ROMs if they're not in the PCI BAR Greg KH
2012-08-01 16:54   ` Matthew Garrett
2012-08-01 23:21     ` Greg KH
2012-08-02  4:02       ` Seth Forshee
2012-08-02 10:34         ` Greg KH
2012-08-02 14:57           ` Francois Rigaut
2012-08-02 16:12             ` Seth Forshee
2012-08-02 22:40               ` Francois Rigaut
2012-08-02 22:54                 ` Francois Rigaut
2012-08-03  4:53                   ` Seth Forshee
     [not found]                     ` <501BD1FC.9020601@mso.anu.edu.au>
     [not found]                       ` <20120803141421.GA8165@thinkpad-t410>
     [not found]                         ` <501C7C1D.5010903@mso.anu.edu.au>
     [not found]                           ` <20120804035844.GA31711@thinkpad-t410>
2012-08-04  5:44                             ` Francois Rigaut [this message]
2012-08-06 13:49                               ` Seth Forshee
2012-08-06 22:50                                 ` Francois Rigaut

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=501CB6AE.3000400@mso.anu.edu.au \
    --to=frigaut@mso.anu.edu.au \
    --cc=bhelgaas@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=matt.fleming@intel.com \
    --cc=mjg59@srcf.ucam.org \
    --cc=seth.forshee@canonical.com \
    --cc=x86@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

Powered by JetHome