From: Charles@Schwieters.org
To: Len Brown <lenb@kernel.org>
Cc: Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
Richard Hughes <hughsient@gmail.com>,
Jonathan Buzzard <jonathan@buzzard.me.uk>,
John Belmonte <john@neggie.net>,
Matthew Garrett <mjg59@srcf.ucam.org>,
Charles@schwieters.org, linux-acpi@vger.kernel.org
Subject: Re: experimental patch for toshiba_acpi
Date: Fri, 13 Mar 2009 20:37:57 -0400 [thread overview]
Message-ID: <E1LiHt0-0002m2-2l@oaf.wireless> (raw)
In-Reply-To: <alpine.LFD.2.00.0903122102490.24376@localhost.localdomain>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Len Brown <lenb@kernel.org> wrote:
> However, I'm not excited about extending toshiba_acpi to
> include /dev/toshiba SMM interface that is already
> provided by the toshiba driver.
>
> I'd rather see the 'toshiba' driver (perhaps renamed to be toshiba_smm)
> extended so that it is the only driver to provide this interface.
>
no objection here. I'd just like to have a working solution.
> BTW. I notice that both toshiba_acpi and toshiba ship in Fedora
> and can load on my satellite pro. However, fedora doesn't ship
> toshset -- is toshiba and /dev/toshiba useful without it?
toshiba_acpi does provide support for a few of the bios settings through
entries in /proc/acpi/toshiba.
>
> Are new machines still using this interface, or it is going away over
> time?
>
It seems that most laptops in the Tecra and Portege lines have this
interface. Many (most?) of the recent Satellites have a Phoenix
Bios which do not support this interface. Most recently, it seems that
some toshiba machines have Insyde BIOS.
Charles
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ <http://mailcrypt.sourceforge.net/>
iD8DBQFJuvxlPK2zrJwS/lYRAtEGAJsEMSCMZvVe6FiFUF7QW2Zc2Y3I1ACfV3c0
bjBVX77ycCHz0qC6SF4wwhU=
=cx50
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2009-03-14 0:39 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 14:54 experimental patch for toshiba_acpi Charles
2009-02-25 15:24 ` Matthew Garrett
2009-02-25 16:18 ` Jonathan Buzzard
2009-02-25 16:51 ` Matthew Garrett
2009-02-25 17:12 ` Jonathan Buzzard
2009-02-25 17:28 ` Matthew Garrett
2009-02-25 17:53 ` Jonathan Buzzard
2009-02-25 17:59 ` Matthew Garrett
2009-02-25 20:18 ` Charles
2009-02-26 0:22 ` Jonathan Buzzard
2009-02-26 8:39 ` Richard Hughes
2009-02-26 10:34 ` Jonathan Buzzard
2009-02-26 12:52 ` Richard Hughes
2009-02-26 13:27 ` Jonathan Buzzard
2009-02-26 13:59 ` Richard Hughes
2009-02-26 15:49 ` Jonathan Buzzard
2009-02-25 17:33 ` Azael Avalos
2009-02-26 13:12 ` John Belmonte
2009-02-26 14:03 ` Richard Hughes
2009-02-26 15:51 ` Jonathan Buzzard
2009-02-26 16:01 ` Matthew Garrett
2009-02-27 16:49 ` Richard Hughes
2009-02-27 17:18 ` Jonathan Buzzard
2009-02-28 15:19 ` Henrique de Moraes Holschuh
2009-03-13 1:17 ` Len Brown
2009-03-14 0:37 ` Charles [this message]
2009-03-14 7:02 ` Andrey Borzenkov
2009-03-14 12:05 ` Matthew Garrett
-- strict thread matches above, loose matches on Subject: below --
2009-02-27 21:15 Andrey Borzenkov
2009-02-27 21:31 ` Charles
2009-02-28 6:13 ` Andrey Borzenkov
2009-02-28 18:00 ` Charles
2009-03-01 7:00 ` Andrey Borzenkov
2009-03-01 10:31 ` Charles
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=E1LiHt0-0002m2-2l@oaf.wireless \
--to=charles@schwieters.org \
--cc=hmh@hmh.eng.br \
--cc=hughsient@gmail.com \
--cc=john@neggie.net \
--cc=jonathan@buzzard.me.uk \
--cc=lenb@kernel.org \
--cc=linux-acpi@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