From: Stephan von Krawczynski <skraw@ithnet.com>
To: Andrew Walrond <andrew@walrond.org>
Cc: andreas@xss.co.at, luming.yu@intel.com,
marcelo.tosatti@cyclades.com, linux-kernel@vger.kernel.org
Subject: Re: ACPI: problem on ASUS PR-DLS533
Date: Sun, 18 Jan 2004 18:00:38 +0100 [thread overview]
Message-ID: <20040118180038.32de2918.skraw@ithnet.com> (raw)
In-Reply-To: <200401181601.58105.andrew@walrond.org>
On Sun, 18 Jan 2004 16:01:58 +0000
Andrew Walrond <andrew@walrond.org> wrote:
> > Alas, in my experience chances are high that any bug report
> > of this kind vanishes in the dungeons of a vendors internal
> > bug report escalation strategy... (Does anyone know a direct
> > technical contact at ASUS?)
> >
>
> I've tried contacting ASUS several times with this issue as I have lots of
> their dual P3 and dual Xeon servers, but end up butting a brick wall, so If
> somebody does have a useful Asus contact, please step forward!
Just a short (general) note on that:
I find it amazing how some companies manage to ignore valuable input, because
even good companies can always get better through listening to customers. Alas
good companies can get real bad if they don't. So take a customers' choice:
stop buying their products if they don't listen to you in case of problems.
This is market, you always have another choice.
Are we _really_ sure this is a BIOS issue? What's the ACPI-maintainers opinion?
I can't really comment technically, I have no deep knowledge about ACPI ...
Regards,
Stephan
next prev parent reply other threads:[~2004-01-18 17:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-18 4:23 Yu, Luming
2004-01-18 11:42 ` Andreas Haumer
2004-01-18 16:01 ` Andrew Walrond
2004-01-18 17:00 ` Stephan von Krawczynski [this message]
[not found] <BF1FE1855350A0479097B3A0D2A80EE0020ADE84@hdsmsx402.hd.intel.com>
2004-01-18 18:19 ` Len Brown
-- strict thread matches above, loose matches on Subject: below --
2004-01-18 4:18 Yu, Luming
2004-01-18 9:01 ` Andrew Walrond
2004-01-12 5:14 Yu, Luming
2004-01-15 18:14 ` Andrew Walrond
2004-01-16 10:30 ` Marcelo Tosatti
2004-01-16 11:25 ` Stephan von Krawczynski
2004-01-16 13:14 ` Andreas Haumer
2004-01-16 13:22 ` Stephan von Krawczynski
2004-01-16 12:07 ` Andrew Walrond
2004-01-07 10:50 Yu, Luming
2004-01-07 12:35 ` Stephan von Krawczynski
2004-01-07 22:58 ` Marcelo Tosatti
2003-12-23 12:04 Andreas Haumer
2003-12-23 14:48 ` Andrew Walrond
2003-12-23 15:21 ` Andreas Haumer
2004-01-07 10:37 ` Stephan von Krawczynski
2004-01-07 14:30 ` Andrew Walrond
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=20040118180038.32de2918.skraw@ithnet.com \
--to=skraw@ithnet.com \
--cc=andreas@xss.co.at \
--cc=andrew@walrond.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luming.yu@intel.com \
--cc=marcelo.tosatti@cyclades.com \
/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
all inboxes | Powered by JetHome®