From: Thomas Renninger <trenn@suse.de>
To: Len Brown <lenb@kernel.org>
Cc: linux-acpi <linux-acpi@vger.kernel.org>,
Jonathan Woithe <jwoithe@physics.adelaide.edu.au>,
Carlos Corbacho <carlos@strangeworlds.co.uk>,
Corentin CHARY <corentincj@iksaif.net>,
Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
Mattia Dongili <malattia@linux.it>
Subject: Re: [PATCH 7/7] Who controls brightness functionality: vendor specific or generic video driver
Date: Wed, 16 Apr 2008 21:08:35 +0200 [thread overview]
Message-ID: <1208372915.1784.356.camel@queen.suse.de> (raw)
In-Reply-To: <1208372572.1784.352.camel@queen.suse.de>
On Wed, 2008-04-16 at 21:02 +0200, Thomas Renninger wrote:
> Who controls brightness functionality: vendor specific or generic video driver
>
> Depending on the capablity of ACPI graphics devices and whether they implement
> all necessary functions so that the generic ACPI video driver can control
> them, decide at driver load time whether a vendor specific device driver or
> the ACPI video driver should control the brighntess functionality.
This probably clashes with other patches.
I also forgot the eepc driver (and others?) which might also interfere
with the video driver?
Please review and if you like it tell me how this could get integrated
in the easiest way...
Thomas
next prev parent reply other threads:[~2008-04-16 19:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-16 19:02 [PATCH 7/7] Who controls brightness functionality: vendor specific or generic video driver Thomas Renninger
2008-04-16 19:08 ` Thomas Renninger [this message]
2008-04-16 21:01 ` Henrique de Moraes Holschuh
2008-04-17 19:32 ` Thomas Renninger
2008-04-19 11:03 ` Carlos Corbacho
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=1208372915.1784.356.camel@queen.suse.de \
--to=trenn@suse.de \
--cc=carlos@strangeworlds.co.uk \
--cc=corentincj@iksaif.net \
--cc=hmh@hmh.eng.br \
--cc=jwoithe@physics.adelaide.edu.au \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=malattia@linux.it \
/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