All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Len Brown <lenb@kernel.org>,
	linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [PATCH] Rationalise ACPI backlight implementation
Date: Sun, 27 Jan 2008 21:10:13 -0800	[thread overview]
Message-ID: <20080127211013.1ddaa6a1.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080128012549.GA24166@srcf.ucam.org>

On Mon, 28 Jan 2008 01:25:50 +0000 Matthew Garrett <mjg59@srcf.ucam.org> wrote:

> On Sat, Jan 26, 2008 at 10:00:45PM -0800, Andrew Morton wrote:
> > - Create a new /sys node with a new name which has the new semantics.
> 
> The semantics are the same as they always have been - values between 0 
> and max_brightness are valid values. If you've made assumptions about 
> what max_brightness is, then that's a bug in the userspace application 
> rather than a change in the semantics of the interface.
> 

WTH?  My (utterly comedic chase-crap-around-the-tree) brightness script
was:

(
0 sh -c "echo $1 > /proc/acpi/sony/brightness"
0 sh -c "echo $1 > /proc/acpi/sony/brightness_default"
0 sh -c "echo $1 > /sys/class/backlight/sony/brightness"
0 sh -c "echo $1 > /sys/class/backlight/thinkpad_screen/brightness"
) 2>/dev/null

And yes, I had an rc.local command which assumed that 7 (later 8) is max
brightness.

You cannot seriously tell me that if we are to change this range from 0-8
up to 0-100 then this is not a backwards-incompatible change in
semantics.

My /sys/class/backlight/ directory is presently empty.  Rather than trying
to find out why, I think I'll just collapse in laughter.

Guys, sort it out, please.


  reply	other threads:[~2008-01-28  5:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-26  2:03 [PATCH] Rationalise ACPI backlight implementation Matthew Garrett
2008-01-14  1:51 ` Matthew Garrett
2008-01-22  8:33 ` Zhang Rui
2008-01-22 11:46   ` Matthew Garrett
2008-01-22 12:39     ` Henrique de Moraes Holschuh
2008-01-24 21:44 ` Len Brown
2008-01-27  2:06   ` Matthew Garrett
2008-01-27  6:00   ` Andrew Morton
2008-01-28  1:25     ` Matthew Garrett
2008-01-28  5:10       ` Andrew Morton [this message]
2008-01-28  5:28         ` Matthew Garrett
2008-01-28 15:51         ` Henrique de Moraes Holschuh
2008-02-02  3:46         ` Len Brown
2008-02-02 11:30           ` Henrique de Moraes Holschuh
2008-02-06 10:09             ` Romano Giannetti
2008-02-06 10:09               ` Romano Giannetti
2008-02-02  3:43 ` Len Brown

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=20080127211013.1ddaa6a1.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.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.