From: Seth Forshee <seth.forshee@canonical.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] platform/x86: Add driver for Apple gmux device
Date: Mon, 12 Mar 2012 10:40:00 -0500 [thread overview]
Message-ID: <20120312154000.GC12322@ubuntu-macmini> (raw)
In-Reply-To: <20120312152224.GA13916@srcf.ucam.org>
On Mon, Mar 12, 2012 at 03:22:24PM +0000, Matthew Garrett wrote:
> On Mon, Mar 12, 2012 at 10:18:52AM -0500, Seth Forshee wrote:
>
> > Why do you presume it works under Windows? Boot camp installs a pile of
> > drivers for Windows, one of those could be a driver for the backlight. I
> > don't know either way. But it's pretty clear that MacOS is using the
> > gmux for the backlight when it is present from the reverse engineering
> > work done by others.
>
> The only reason to provide it at all is for Windows - it's never going
> to be used under OS X.
I'm not so sure. The MacBook Pro 8,1 and 8,2 seem to use the same BIOS
implementation -- the version numbers and DSDTs are identical. The 8,1
has only Intel graphics, no gmux, and a working acpi_video0 backlight
under Linux. The 8,2 has hybrid ATI/Intel, a gmux w/ working backlight
control, and acpi_video0 does not work.
So while I'm not sure, I can't rule out that the acpi_video backlight
might be provided specifically for the 8,1 and that OS X is using it.
Unfortunately I don't have an 8,1 that I can play with to try and work
it out.
Seth
next prev parent reply other threads:[~2012-03-12 15:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 20:34 [PATCH] platform/x86: Add driver for Apple gmux device Seth Forshee
2012-02-22 14:37 ` [PATCH v2] " Seth Forshee
2012-02-29 17:46 ` Grant Likely
2012-02-29 17:53 ` Seth Forshee
2012-02-29 18:43 ` Grant Likely
2012-02-29 19:50 ` Seth Forshee
2012-02-29 21:23 ` Grant Likely
2012-02-29 22:08 ` Seth Forshee
2012-02-29 22:32 ` Grant Likely
2012-02-29 22:56 ` Seth Forshee
2012-03-01 9:19 ` Corentin Chary
2012-03-01 14:53 ` Seth Forshee
2012-03-01 15:15 ` Corentin Chary
2012-03-05 22:06 ` Seth Forshee
2012-03-05 22:10 ` Josh Boyer
2012-03-05 22:37 ` Seth Forshee
2012-03-06 12:52 ` Josh Boyer
2012-03-12 14:21 ` Matthew Garrett
2012-03-12 14:57 ` Seth Forshee
2012-03-12 15:07 ` Matthew Garrett
2012-03-12 15:18 ` Seth Forshee
2012-03-12 15:22 ` Matthew Garrett
2012-03-12 15:40 ` Seth Forshee [this message]
2012-03-15 15:47 ` Seth Forshee
2012-03-15 16:09 ` Matthew Garrett
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=20120312154000.GC12322@ubuntu-macmini \
--to=seth.forshee@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=platform-driver-x86@vger.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