From: David Woodhouse <dwmw2@infradead.org>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, Matthew Garrett <mjg@redhat.com>
Subject: Re: [PATCH] gmux: Fix backlight set function
Date: Thu, 04 Oct 2012 11:53:59 +0100 [thread overview]
Message-ID: <1349348039.8070.5.camel@shinybook.infradead.org> (raw)
In-Reply-To: <CACxGe6ufKKHEYZGpcrnPJRqKVzKwkH4PEtnMS0RhH8V5ABfWFQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1081 bytes --]
On Fri, 2012-09-14 at 14:06 +0100, Grant Likely wrote:
> What patches are you running on top of mainline for the mbp8,3?
A slightly simpler answer: I'm running the Fedora 18 3.6 kernel, with
these two patches backported:
commit f462ed939de67c20528bc08f11d2fc4f2d59c0d5
Author: Matthew Garrett <mjg@redhat.com>
Date: Fri Jul 27 12:58:53 2012 -0400
efifb: Skip DMI checks if the bootloader knows what it's doing
commit a7d92035a1d64242cbc1f79577e66f230fe59732
Author: Matthew Garrett <mjg@redhat.com>
Date: Fri Jul 27 17:16:17 2012 -0400
x86, EFI: Calculate the EFI framebuffer size instead of trusting the firmware
The F18 kernel has Matthew's stuff to handle PCI ROMs already
backported, although it's broken; it still prioritises the
IORESOURCE_ROM_SHADOW bit and returns 0xC0000 when there is a ROM from
EFI. You'll have to fix that too, so it matches commit 463edf567.
It still fails the same way — the Intel driver never manages to display.
So I'm back on my 3.5.0-based build until I have some time to work it
out.
--
dwmw2
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 6171 bytes --]
prev parent reply other threads:[~2012-10-04 10:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 20:02 Grant Likely
2012-09-13 20:26 ` Seth Forshee
2012-09-13 20:31 ` Matthew Garrett
2012-09-13 20:35 ` David Woodhouse
2012-09-14 13:06 ` Grant Likely
2012-09-17 9:37 ` David Woodhouse
2012-10-04 10:53 ` David Woodhouse [this message]
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=1349348039.8070.5.camel@shinybook.infradead.org \
--to=dwmw2@infradead.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg@redhat.com \
--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
all inboxes | Powered by JetHome®