From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Matthias Grimm <matthiasgrimm@users.sourceforge.net>
Cc: linuxppc-dev@ozlabs.org, 407671@bugs.debian.org, paulus@samba.org
Subject: Re: kernel 2.6.18: Confusion about Macintosh backlight configuration
Date: Mon, 22 Jan 2007 14:33:35 +1100 [thread overview]
Message-ID: <1169436815.31479.4.camel@localhost.localdomain> (raw)
In-Reply-To: <20070120150614.0b62a3ef.matthiasgrimm@users.sourceforge.net>
> This will allow modern systems to be compiled only with
> CONFIG_PMAC_BACKLIGHT and a user space daemon does the rest. I hope my
> point could be seen. I would really appreciate if the configuration
> could be cleaned up.
>
> Other solutions could be:
>
> 2. If the sysfs backlight driver is opened switch kernel backlight keys
> handling off by calling PMU_IOC_GRAB_BACKLIGHT for machines that
> support the sysfs backlight interface.
>
> 3. Remove the kernel backlight keys control code from the kernel.
>
> 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 ?
In the long run, we might want something smarter indeed, not sure what
the best solution is... I like having the kernel control work always
when no daemon is there.
Among others, because we have this never solved problem where
occasionally, the internal flat panel doesn't sync properly and the only
way to get it back is to turn the backlight all the way down and back up
a few times until it "kicks in".
Ben.
next prev parent reply other threads:[~2007-01-22 3:33 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 [this message]
2007-01-22 15:05 ` Matthias Grimm
2007-01-22 19:52 ` Benjamin Herrenschmidt
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=1169436815.31479.4.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox