From: Andrey Borzenkov <arvidjaar@mail.ru>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Thomas Renninger <trenn@suse.de>, Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH] toshiba_acpi: fingers off backlight if video.ko is serving this functionality
Date: Sat, 15 Nov 2008 20:05:04 +0300 [thread overview]
Message-ID: <200811152005.05031.arvidjaar@mail.ru> (raw)
In-Reply-To: <20081115165415.GA9117@srcf.ucam.org>
[-- Attachment #1: Type: text/plain, Size: 1505 bytes --]
On Saturday 15 November 2008, Matthew Garrett wrote:
> On Sat, Nov 15, 2008 at 07:30:57PM +0300, Andrey Borzenkov wrote:
> > On Thursday 13 November 2008, Matthew Garrett wrote:
> > > On Thu, Nov 13, 2008 at 07:58:09AM +0300, Andrey Borzenkov wrote:
> > >
> > > > - exposing two knobs for the *same* thing confuses user level tools; you never
> > > > know which one is used and they compete behind your back
> > >
> > > How do they compete?
> >
> > In my case user level program (kpowersave) decided to use video.ko for
> > brightness control (or, may be, it used them both). Which gave me 2 levels
> > instead of 8. And there is no way to control it, at least known to me.
>
> Right. But that doesn't mean they're competing, as such. If you set the
> brightness via toshiba_acpi
I probably have problems with expressing myself as non-native English
speaker.
I am not interested in setting values via echoing into sysfs file. I
am interested in my desktop brightness control working out of the box.
And desktop driver control has no way to select, which of two sysfs
files to use. Nor do I understand why I have to create this problem
of selecting right driver when I already have possibility to avoid it.
If you think exposing both knobs is non-issue, why are all those patches
for other vendor drivers included in the kernel in the first place?
> to a value that isn't supported via the
> acpi driver, what value does the acpi backlight claim to be at?
>
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-11-15 17:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-08 13:37 [PATCH] toshiba_acpi: fingers off backlight if video.ko is serving this functionality Andrey Borzenkov
2008-11-11 20:04 ` Len Brown
2008-11-12 23:41 ` Thomas Renninger
2008-11-13 1:32 ` Matthew Garrett
2008-11-13 4:58 ` Andrey Borzenkov
2008-11-13 11:11 ` Matthew Garrett
2008-11-15 16:30 ` Andrey Borzenkov
2008-11-15 16:54 ` Matthew Garrett
2008-11-15 17:05 ` Andrey Borzenkov [this message]
2008-11-15 17:11 ` Matthew Garrett
2008-11-15 17:17 ` Andrey Borzenkov
2008-11-15 17:20 ` Matthew Garrett
2008-11-15 18:42 ` Andrey Borzenkov
2008-11-15 18:49 ` Matthew Garrett
2008-11-16 12:51 ` Henrique de Moraes Holschuh
2008-11-16 21:44 ` Thomas Renninger
2008-11-17 2:07 ` Henrique de Moraes Holschuh
2008-11-27 5:19 ` Len Brown
2008-11-27 11:39 ` Video.ko-vs-toshiba.ko-more-brightness-levels-win Thomas Renninger
2008-11-27 11:39 ` [PATCH 1/2] ACPI: acpi_video_backlight_support return found generic video brightness levels Thomas Renninger
2008-11-27 12:08 ` Thomas Renninger
2008-11-27 11:39 ` [PATCH 2/2] Video.ko vs toshiba.ko - more brightness levels win Thomas Renninger
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=200811152005.05031.arvidjaar@mail.ru \
--to=arvidjaar@mail.ru \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=trenn@suse.de \
/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