From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>,
<linuxppc-dev@lists.linuxppc.org>
Subject: Re: 2.4 - buttons, temperature, ictc
Date: Tue, 17 Jul 2001 12:19:01 +0200 [thread overview]
Message-ID: <20010717101901.21603@smtp.adsl.oleane.com> (raw)
In-Reply-To: <5.1.0.14.2.20010717110248.03890268@mail.netsurf.de>
>I object to putting anything you marked with CONFIG_PMAC_VOLUME into the
>kernel, it's worse enough we have CONFIG_PMAC_BACKLIGHT in there. I'll
>merge your "input_report_key" into my 2.5 adbhid.c source though, thx.
>
>With 2.5 even CONFIG_PMAC_BACKLIGHT in adbhid.c will go away and you _have_
>to use the event devices then, so you better start using them _now_. Taking
>kernel bloating shortcuts is not the way to go IMHO.
Right, all this belongs to userland. I might include part of this
patch in 2.4 so we have the feature working now, but for 2.5, I'd
rather use the event devices for both backlight and volume, and
have pmud handle them.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-07-17 10:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-17 5:45 2.4 - buttons, temperature, ictc Joseph P. Garcia
2001-07-17 7:18 ` Geert Uytterhoeven
2001-07-17 8:18 ` Joseph P. Garcia
2001-07-17 9:11 ` Franz Sirl
2001-07-17 10:19 ` Benjamin Herrenschmidt [this message]
2001-07-17 14:40 ` Michael Schmitz
2001-07-17 20:29 ` Joseph P. Garcia
-- strict thread matches above, loose matches on Subject: below --
2001-07-17 10:32 Iain Sandoe
2001-07-18 11:11 Iain Sandoe
2001-07-18 12:43 ` Joseph P. Garcia
2001-07-18 12:52 ` Bastien Nocera
2001-07-18 18:00 ` Joseph P. Garcia
2001-07-18 20:13 ` Michael Schmitz
2001-07-18 20:10 ` Michael Schmitz
2001-07-18 21:11 ` Bastien Nocera
2001-07-18 21:44 ` Michael Schmitz
2001-07-19 9:06 ` Bastien Nocera
2001-07-19 9:28 ` Michael Schmitz
2001-07-18 21:29 ` Bastien Nocera
2001-07-18 13:34 Iain Sandoe
2001-07-18 13:45 Iain Sandoe
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=20010717101901.21603@smtp.adsl.oleane.com \
--to=benh@kernel.crashing.org \
--cc=Franz.Sirl-kernel@lauterbach.com \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).