From: Pavel Machek <pavel@ucw.cz>
To: Michael_E_Brown@Dell.com
Cc: mjg59@srcf.ucam.org, akpm@osdl.org, Matt_Domsch@Dell.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [RESEND] Add Dell laptop backlight brightness display
Date: Sun, 12 Feb 2006 18:26:08 +0100 [thread overview]
Message-ID: <20060212172607.GA1609@openzaurus.ucw.cz> (raw)
In-Reply-To: <35C9A9D68AB3FA4AB63692802656D9EC9277C0@ausx3mps303.aus.amer.dell.com>
Hi!
> You can get and set laptop brighness on Dell with the proper SMI call.
>
> To do the proper SMI call requires parsing SMBIOS structure 0xDA, a
> vendor-proprietary structure, and getting the SMI index and io port and
> magic values. Then, you need to know how to setup the registers and
> input/output buffers for the call. All of this is already present in
> libsmbios.
Perhaps authors of libsmbios could help here?
> Reading nvram is not a valid way to get brighness unless you also do
> similar work (parse specific vendor-proprietary SMBIOS structures) to
> ensure that you are reading the correct location. This location is
> subject to change from BIOS to BIOS and machine to machine. The fact
> that you may have observed it in the same location on a few laptops does
> not change this fact.
Well, folks reverse-engineering your machines had no idea until now...
> In fact, I have the same objection to the I8K driver in the kernel. It
> has hardcoded SMI calls, that are subject to change. There is a proper
> way to get the correct IO ports to make this safe, but it is not
> currently being done.
Could you or someone at Dell submit patches to correct this?
--
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
next prev parent reply other threads:[~2006-02-18 12:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-07 16:34 Michael_E_Brown
2006-02-07 17:20 ` Matthew Garrett
2006-02-12 17:26 ` Pavel Machek [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-20 16:45 Michael_E_Brown
2006-02-20 16:53 ` Pavel Machek
2006-02-23 5:17 ` Michael E Brown
2006-02-07 17:23 Michael_E_Brown
2006-02-07 3:43 Michael E Brown
2006-02-07 4:09 ` Matthew Garrett
2006-02-06 19:15 [PATCH] Make DMI code store chassis type Matthew Garrett
2006-02-06 19:18 ` [PATCH] Add HP laptop backlight brightness display Matthew Garrett
2006-02-06 19:19 ` [PATCH] Add Dell " Matthew Garrett
2006-02-07 0:37 ` [PATCH] [RESEND] " Matthew Garrett
2006-02-07 3:37 ` Dmitry Torokhov
2006-02-07 12:32 ` Matthew Garrett
2006-02-07 13:06 ` Richard Purdie
2006-02-07 13:23 ` Matthew Garrett
2006-02-07 13:37 ` Richard Purdie
2006-02-07 13:55 ` Matthew Garrett
2006-02-07 14:54 ` Richard Purdie
2006-02-08 9:06 ` Pavel Machek
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=20060212172607.GA1609@openzaurus.ucw.cz \
--to=pavel@ucw.cz \
--cc=Matt_Domsch@Dell.com \
--cc=Michael_E_Brown@Dell.com \
--cc=akpm@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome