All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Matthias Grimm <matthiasgrimm@users.sourceforge.net>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org, 407671@bugs.debian.org
Subject: Re: kernel 2.6.18: Confusion about Macintosh backlight configuration
Date: Tue, 23 Jan 2007 06:52:40 +1100	[thread overview]
Message-ID: <1169495560.1582.5.camel@localhost.localdomain> (raw)
In-Reply-To: <20070122160518.2c2275bf.matthiasgrimm@users.sourceforge.net>

On Mon, 2007-01-22 at 16:05 +0100, Matthias Grimm wrote:
> On Mon, 22 Jan 2007 14:33:35 +1100
> Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
> 
> > > Which solution you prefer is up to you but I would be glad if at least
> > > solution #1 could be realised.
> > 
> > For now, at least, what prevents you from having all enabled and have
> > pbbuttonsd still call PMU_IOC_GRAB_BACKLIGHT ?
> 
> Nothing. Pbbuttonsd does so by now but this wouldn't help if someone set
> CONFIG_PMAC_BACKLIGHT_LEGACY to off. 
> 
> I check this out with debian, hoping you will find a smart solution for
> this in the future. I think the debian people getting aware of this
> backwards compatibility problem now and there is hope they will fix it
> for etch.

Yes, debian should keep CONFIG_PMAC_BACKLIGHT_LEGACY enabled.

Ben.

      reply	other threads:[~2007-01-22 19:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-20 14:06 kernel 2.6.18: Confusion about Macintosh backlight configuration Matthias Grimm
2007-01-22  3:33 ` Benjamin Herrenschmidt
2007-01-22 15:05   ` Matthias Grimm
2007-01-22 19:52     ` Benjamin Herrenschmidt [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=1169495560.1582.5.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=407671@bugs.debian.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=matthiasgrimm@users.sourceforge.net \
    --cc=paulus@samba.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.