All of lore.kernel.org
 help / color / mirror / Atom feed
From: Francois Rigaut <frigaut@mso.anu.edu.au>
To: Greg KH <gregkh@linuxfoundation.org>,
	Matthew Garrett <mjg59@srcf.ucam.org>,
	matt.fleming@intel.com, linux-efi@vger.kernel.org,
	linux-kernel@vger.kernel.org, x86@kernel.org,
	linux-pci@vger.kernel.org, bhelgaas@google.com
Subject: Re: [PATCH V2 1/4] EFI: Stash ROMs if they're not in the PCI BAR
Date: Fri, 03 Aug 2012 08:40:45 +1000	[thread overview]
Message-ID: <501B01ED.9080309@mso.anu.edu.au> (raw)
In-Reply-To: <20120802161209.GF32395@thinkpad-t410>

Hi Seth,

Sorry for the belated response. On Oz time here.
I don't have a /var/log/kernel.log !
Let me make sure of something:
This switcher code is to be run on osx, no? That's where gfxcardstatus 
lives and where I can effect the card switch. Just to make sure.
So I'm running osx mountain lion, and the only thing I see in the logs 
when I switch cards (using gfxcardstatus) is what I pasted below. and 
you're right, it was not in message.log, but system.log (it was late). I 
just went through the whole thing again.
Am I missing something?
Cheers,
Francois

On 03/08/12 02:12, Seth Forshee wrote:
> On Fri, Aug 03, 2012 at 12:57:33AM +1000, Francois Rigaut wrote:
>> Greg, Seth,
>>
>> Here is what the message.log shows:
>>
>> switching to the HD4000 (integrated):
>>
>> Aug  3 00:49:55 poliahu.ctio.noao.edu WindowServer[79]: Received display connect changed for display 0x42803c0
>> Aug  3 00:49:55 poliahu.ctio.noao.edu WindowServer[79]: CGXMuxAcknowledge: Posting glitchless acknowledge
>> Aug  3 00:49:55 poliahu.ctio.noao.edu WindowServer[79]: MPAccessSurfaceForDisplayDevice: Set up page flip mode on display 0x042803c0 device: 0x10c678320  isBackBuffered: 0 numComp: 1 numDisp: 3
>> Aug  3 00:49:55 poliahu.ctio.noao.edu WindowServer[79]: Received display connect changed for display 0x42803c0
>> Aug  3 00:49:55 poliahu.ctio.noao.edu WindowServer[79]: Received display connect changed for display 0x3f003d
>> Aug  3 00:49:55 poliahu.ctio.noao.edu WindowServer[79]: Received display connect changed for display 0x3f003e
>> Aug  3 00:49:55 poliahu.ctio.noao.edu WindowServer[79]: Received display connect changed for display 0x3f003f
>>
>> switching to the nvidia (discrete):
>>
>> Aug  3 00:50:35 poliahu.ctio.noao.edu WindowServer[79]: Received display connect changed for display 0x42803c0
>> Aug  3 00:50:35 poliahu.ctio.noao.edu WindowServer[79]: Received display connect changed for display 0x3f003d
>> Aug  3 00:50:35 poliahu.ctio.noao.edu WindowServer[79]: Received display connect changed for display 0x3f003e
>> Aug  3 00:50:35 poliahu.ctio.noao.edu WindowServer[79]: Received display connect changed for display 0x3f003f
>> Aug  3 00:50:35 poliahu.ctio.noao.edu WindowServer[79]: CGXMuxAcknowledge: Posting glitchless acknowledge
>> Aug  3 00:50:35 poliahu.ctio.noao.edu WindowServer[79]: MPAccessSurfaceForDisplayDevice: Set up page flip mode on display 0x042803c0 device: 0x10c678320  isBackBuffered: 0 numComp: 1 numDisp: 3
>> Aug  3 00:50:35 poliahu.ctio.noao.edu WindowServer[79]: Received display connect changed for display 0x42803c0
>>
>> Hope that helps.
> Thanks for trying it out, but it's not really what I was hoping for. I
> get a bunch of messages similar to these in /var/log/kernel.log, mixed
> in with a lot of other stuff.
>
>   AGC:: setMuxRegister:1666 (728, 1, 1)
>   AGC:: setMuxRegister:1666 (710, 1, 4)
>   AGC:: getMuxRegister:1647 (716, 1) = 1
>
> I don't even have message.log. You don't have a kernel.log? Do you see
> any messages like those if you run dmesg?
>
> Seth


  reply	other threads:[~2012-08-02 22:41 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-27 16:52 [PATCH V2 1/4] EFI: Stash ROMs if they're not in the PCI BAR 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 [this message]
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
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=501B01ED.9080309@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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.