From: John Belmonte <john@neggie.net>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Jonathan Buzzard <jonathan@buzzard.me.uk>,
Charles@schwieters.org, linux-acpi@vger.kernel.org,
Richard Hughes <hughsient@gmail.com>
Subject: Re: experimental patch for toshiba_acpi
Date: Thu, 26 Feb 2009 08:12:11 -0500 [thread overview]
Message-ID: <a0c408570902260512t702b2575w417ef96dfa74a5bf@mail.gmail.com> (raw)
In-Reply-To: <20090225165152.GA5981@srcf.ucam.org>
On Wed, Feb 25, 2009 at 11:51 AM, Matthew Garrett <mjg59@srcf.ucam.org> wrote:
> On Wed, Feb 25, 2009 at 04:18:25PM +0000, Jonathan Buzzard wrote:
>
>> Because it makes far more sense to have a user mode program to drive the
>> features, and for the kernel to provide the necessary thin layer to
>> access the features.
>
> It makes sense for the kernel to provide a consistent abstraction of
> hardware functionality where possible. Almost every kernel driver could
> be rewritten in userspace - that doesn't make it a good idea.
That argument would be most applicable if we were talking about adding
some new /dev interface-- but we're not. Toshiba's HCI has been
around for a couple of decades; /dev/toshiba, which exposes it, has
been around for over 10 years; toshset, a useful and popular tool
which depends on /dev/toshiba, nearly as long as /dev/toshiba.
The proposed patch makes /dev/toshiba, and hence toshset, work on more
laptops-- it's a no-brainer to anyone with a practical mindset.
You've got Jonathan and Charles-- the two most-knowledgeable people on
Toshiba's firmware and /dev/toshiba in the free software community--
saying that it's not practical to jam all that functionality into the
kernel. Please listen to them.
Regards,
--John
next prev parent reply other threads:[~2009-02-26 13:12 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 [this message]
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
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=a0c408570902260512t702b2575w417ef96dfa74a5bf@mail.gmail.com \
--to=john@neggie.net \
--cc=Charles@schwieters.org \
--cc=hughsient@gmail.com \
--cc=jonathan@buzzard.me.uk \
--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