public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Martin Filip <bugtraq@smoula.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Macbook Pro 5,5 nvidia backlight fix
Date: Mon, 5 Jul 2010 18:48:23 +0100	[thread overview]
Message-ID: <20100705174823.GA16764@srcf.ucam.org> (raw)
In-Reply-To: <4C321A0D.20008@smoula.net>

On Mon, Jul 05, 2010 at 07:44:45PM +0200, Martin Filip wrote:
> On 5.7.2010 19:25, Matthew Garrett wrote:
> > On Mon, Jul 05, 2010 at 05:27:00PM +0200, Martin Filip wrote:
> >> Maybe someone involved with this module can merge this one?
> > 
> > This is a really bad idea. You're hardcoding the location of PDISPLAY, 
> > which the kernel is at liberty to remap at boot time, and even then 
> > you're writing into the address space of a device that's controlled by 
> > another driver.
> well, I understand what you do not like. But I'm not capable of fixing
> this. Let's say I'm just reporting something that does not work and
> pointing out, that "this way it works for me for almost a year on
> different versions of kernel". Is there someone, who understands that?

Yes, which is why I added support for it to nouveau...

> > Does nouveau not handle this hardware properly?
> I'm user of nvidia binary drivers. I can try, but I doubt.

The graphics hardware is supposed to be under the control of the 
graphics driver. If your graphics driver is deficient then you'll really 
have to take that up with your vendor.

-- 
Matthew Garrett | mjg59@srcf.ucam.org

      parent reply	other threads:[~2010-07-05 17:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-05 15:27 Macbook Pro 5,5 nvidia backlight fix Martin Filip
2010-07-05 17:25 ` Matthew Garrett
     [not found]   ` <4C321A0D.20008@smoula.net>
2010-07-05 17:48     ` Matthew Garrett [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=20100705174823.GA16764@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=bugtraq@smoula.net \
    --cc=linux-kernel@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