From: Faye Pearson <faye-6JSjyQ0Qj1ReoWH0uzbU5w@public.gmane.org>
To: Duncan Gibb
<duncangibb-zbhw9Kw21rH/AQmYMRTMl1aTQe2KTcn/@public.gmane.org>
Cc: "Cagle,
John (ISS-Houston)" <john.cagle-VXdhtT5mjnY@public.gmane.org>,
Darren Benham <dbenham-FG1iuTdj8bisTnJN9+BGXg@public.gmane.org>,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: HP-Compaq laptops and Linux ACPI (was RE: redhat comment about intel not taking patches?)
Date: Thu, 13 Feb 2003 17:41:46 +0000 [thread overview]
Message-ID: <20030213174146.GB5405@clara.net> (raw)
In-Reply-To: <1045154118.14935.64.camel-h9eRTumTmmZjMu4AB9qoK9F8XQ1HzYRO@public.gmane.org>
Duncan Gibb [duncangibb-zbhw9Kw21rH/AQmYMRTMl1aTQe2KTcn/@public.gmane.org] wrote:
> However, I, as your customer, think that if HP advertises a product as
> ACPI-compliant - which you do - and is (through Compaq) a co-author of
> the specification with which you're claiming compliance - which you are
> - then it's not too much to ask that this claim be true - which
> unfortunately, it isn't.
And the way to communicate that is to change your supplier. My last
laptop was a Compaq. My current laptop is a Sony. I'm not saying that
the sony has a perfect ACPI implementation but I haven't had to override
the BIOS DSDT to get working battery/ac status.
Hopefully John will take some of this feedback back to HP/Compaq.
Faye
--
Faye Pearson,
Covert Development
ClaraNET Ltd. Tel 020 7903 3000
-------------------------------------------------------
This SF.NET email is sponsored by: FREE SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
next prev parent reply other threads:[~2003-02-13 17:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-13 4:11 redhat comment about intel not taking patches? Cagle, John (ISS-Houston)
[not found] ` <C50AB9511EE59B49B2A503CB7AE1ABD10440E3DB-Iar2LzuD2f6P0FQRY6S+e9kSKC0Mw0DFJ8am2ALHCgk@public.gmane.org>
2003-02-13 7:58 ` Darren Benham
2003-02-13 11:11 ` Dave Jones
2003-02-13 12:45 ` redhat comment about intel not taking patches? - Compaq Hardware Troy Schultz
[not found] ` <1045140314.14099.5.camel-QUVSR2uV0NY@public.gmane.org>
2003-02-13 16:22 ` Chris Howells
2003-02-13 20:36 ` Alan Cox
[not found] ` <1045168611.6493.7.camel-MMxVpc8zpTQVh3rx8e9g/fyykp6/JSeS3vcXtXqGYxw@public.gmane.org>
2003-02-14 9:23 ` Duncan Gibb
2003-02-13 16:35 ` HP-Compaq laptops and Linux ACPI (was RE: redhat comment about intel not taking patches?) Duncan Gibb
[not found] ` <1045154118.14935.64.camel-h9eRTumTmmZjMu4AB9qoK9F8XQ1HzYRO@public.gmane.org>
2003-02-13 17:41 ` Faye Pearson [this message]
2003-02-14 2:30 ` Luming
[not found] ` <20030214023027.43928.qmail-9BQvNTzFdpmA/QwVtaZbd3CJp6faPEW9@public.gmane.org>
2003-02-14 9:17 ` Duncan Gibb
[not found] ` <1045214222.14935.125.camel-h9eRTumTmmZjMu4AB9qoK9F8XQ1HzYRO@public.gmane.org>
2003-02-17 2:07 ` Luming
[not found] ` <20030217020732.72828.qmail-uB9Tpqv8kgqA/QwVtaZbd3CJp6faPEW9@public.gmane.org>
2003-02-17 8:32 ` Duncan Gibb
2003-02-13 18:10 ` Richard Black
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=20030213174146.GB5405@clara.net \
--to=faye-6jsjyq0qj1reowh0uzbu5w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=dbenham-FG1iuTdj8bisTnJN9+BGXg@public.gmane.org \
--cc=duncangibb-zbhw9Kw21rH/AQmYMRTMl1aTQe2KTcn/@public.gmane.org \
--cc=john.cagle-VXdhtT5mjnY@public.gmane.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