From: Pavel Machek <pavel-AlSwsSmVLrQ@public.gmane.org>
To: "Cagle, John (ISS-Houston)" <john.cagle-VXdhtT5mjnY@public.gmane.org>
Cc: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Nate Lawson <nate-Y6VGUYTwhu0@public.gmane.org>,
"Scott T. Smith" <scott-j3vAvQ9dNB9ByuSxxbvQtw@public.gmane.org>,
ACPI Developers
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
Robert Moore
<robert.moore-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Andrew Grover
<andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: ACPI_STRICT_COMPLIANCE (was RE: RE: ACPI -- Workaround forbroken DSDT)
Date: Thu, 19 Feb 2004 23:48:35 +0100 [thread overview]
Message-ID: <20040219224834.GH467@openzaurus.ucw.cz> (raw)
In-Reply-To: <C50AB9511EE59B49B2A503CB7AE1ABD10661123D-Iar2LzuD2f6P0FQRY6S+e9kSKC0Mw0DFJ8am2ALHCgk@public.gmane.org>
Hi!
> > think we can put under this umbrella also.
>
> I agree. This should make a lot of users happy, since the distro's will
> work out-of-the-box without modification (at least on those machines
> with known workarounds implemented in the ACPI driver), yet the OEMs can
> still test for strict compliance by recompiling the kernel. Better than
> that would be a kernel command line option to do the same thing.
> ACPI_STRICT=ON?
You know how OEMs test their hardware? They stick distro
CD in, and if it boots, it must be okay :-(.
At least command line option would be good, we can't
really expect oems to recompile.
Pavel
--
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
next prev parent reply other threads:[~2004-02-19 22:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-11 18:04 ACPI_STRICT_COMPLIANCE (was RE: RE: ACPI -- Workaround forbroken DSDT) Cagle, John (ISS-Houston)
[not found] ` <C50AB9511EE59B49B2A503CB7AE1ABD10661123D-Iar2LzuD2f6P0FQRY6S+e9kSKC0Mw0DFJ8am2ALHCgk@public.gmane.org>
2004-02-11 19:35 ` Len Brown
2004-02-19 22:48 ` Pavel Machek [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-12 3:11 Yu, Luming
2004-02-12 5:33 Cagle, John (ISS-Houston)
[not found] ` <C50AB9511EE59B49B2A503CB7AE1ABD10661124D-Iar2LzuD2f6P0FQRY6S+e9kSKC0Mw0DFJ8am2ALHCgk@public.gmane.org>
2004-02-12 23:08 ` Bruno Ducrot
2004-02-12 6:32 Yu, Luming
[not found] ` <3ACA40606221794F80A5670F0AF15F8401CBB6AC-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-02-12 20:21 ` Len Brown
2004-02-13 0:08 Cagle, John (ISS-Houston)
[not found] ` <C50AB9511EE59B49B2A503CB7AE1ABD106611260-Iar2LzuD2f6P0FQRY6S+e9kSKC0Mw0DFJ8am2ALHCgk@public.gmane.org>
2004-02-13 0:50 ` Bruno Ducrot
[not found] ` <20040213005043.GE13262-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2004-02-16 8:34 ` Stefan Seyfried
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=20040219224834.GH467@openzaurus.ucw.cz \
--to=pavel-alswssmvlrq@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=john.cagle-VXdhtT5mjnY@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=nate-Y6VGUYTwhu0@public.gmane.org \
--cc=robert.moore-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=scott-j3vAvQ9dNB9ByuSxxbvQtw@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