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
Dat
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? I'm
> using the radeon blos loading patch and I've got the nasty direct io
> writes in grub.cfg to disable the radeon before booting into the
> kernel so that X picks up the i915
On Thu, Sep 13, 2012 at 9:35 PM, David Woodhouse wrote:
> On Thu, 2012-09-13 at 21:02 +0100, Grant Likely wrote:
>> In commit 7e30ed6b, "gmux: Add generic write32 function", the new
>> gmux_write32() function didn't include the io offset when writing
>> registers. This means that backlight update
On Thu, 2012-09-13 at 21:02 +0100, Grant Likely wrote:
> In commit 7e30ed6b, "gmux: Add generic write32 function", the new
> gmux_write32() function didn't include the io offset when writing
> registers. This means that backlight update writes never go to the
> right
> place. This patch fixes it.
>
Sorry, I am literally catching up on these right now.
--
Matthew Garrett | mj...@srcf.ucam.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please
On Thu, Sep 13, 2012 at 09:02:35PM +0100, Grant Likely wrote:
> In commit 7e30ed6b, "gmux: Add generic write32 function", the new
> gmux_write32() function didn't include the io offset when writing
> registers. This means that backlight update writes never go to the right
> place. This patch fixes
6 matches
Mail list logo
