public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Hughes <hughsient@gmail.com>
To: Jonathan Buzzard <jonathan@buzzard.me.uk>
Cc: 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, 27 Feb 2009 16:49:09 +0000	[thread overview]
Message-ID: <1235753349.5444.53.camel@localhost.localdomain> (raw)
In-Reply-To: <1235663518.4770.197.camel@penguin.lifesci.dundee.ac.uk>

On Thu, 2009-02-26 at 15:51 +0000, Jonathan Buzzard wrote:
> Now if Toshiba who in part wrote the ACPI specification think this is
> the way to go, and the people who know the most about the HCI in the
> free software world also think this is the way to go, what are your
> qualifications to argue with them, given you have virtually no
> knowledge of the Toshiba HCI and would not appear to even own a
> Toshiba designed and manufactured laptop anyway.

I still own a Satellite Pro A10, model number PSA15E-03U7V-EN. I no
longer use it day-to-day, as it's so very slow compared to my T61.

I know exactly what HCI is, how it works, and have a good idea of what
it can do. I've written patches for the toshiba_acpi driver before for
the key mapping functionality.

In the meantime, you've insulted me enough for one email thread.

Len, I would agree with Matthew that the patch should not be merged, and
that any missing functionality should be added to the existing ACPI
driver.

Richard.



  parent reply	other threads:[~2009-02-27 16:50 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 [this message]
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=1235753349.5444.53.camel@localhost.localdomain \
    --to=hughsient@gmail.com \
    --cc=Charles@schwieters.org \
    --cc=john@neggie.net \
    --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