From: Bruno Ducrot <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
To: Stefan Seyfried
<seife-T+3qhDtrTvDv8lqoKu5MV4HBZQ1bDw0s@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Re: ACPI_STRICT_COMPLIANCE (was RE: RE: ACPI -- Workaround forbroken DSDT)
Date: Mon, 16 Feb 2004 13:49:46 +0100 [thread overview]
Message-ID: <20040216124946.GO13262@poupinou.org> (raw)
In-Reply-To: <20040216083435.GA23640-l0tNAEGuAhhzZ8+rp42Dbp9+tswZ0GTaehPwdyo5hKaELgA04lAiVw@public.gmane.org>
On Mon, Feb 16, 2004 at 09:34:35AM +0100, Stefan Seyfried wrote:
> On Fri, Feb 13, 2004 at 01:50:43AM +0100, Bruno Ducrot wrote:
>
> > The 'toshiba return bug' is something like that:
> >
> > Method(FOO) {
> > return (0)
> > }
> >
> > Method(BAR) {
> > FOO()
> > }
> >
> > If ACPI is pedantic, BAR return nothing.
>
> Well, but it is a bug, so it _should_ fail with "acpi=strict", shouldn't it?
Yes.
> If "acpi=strict" is omitted, the bug can be worked around and the buyers of
> this crap can be happy.
Problem is that I don't know for what flavour of the no-named AML
interpreter that bug will be hit. So at least the acpi=not_strict need
to be more fine grained.
--
Bruno Ducrot
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
-------------------------------------------------------
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
prev parent reply other threads:[~2004-02-16 12:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 0:08 ACPI_STRICT_COMPLIANCE (was RE: RE: ACPI -- Workaround forbroken DSDT) 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
[not found] ` <20040216083435.GA23640-l0tNAEGuAhhzZ8+rp42Dbp9+tswZ0GTaehPwdyo5hKaELgA04lAiVw@public.gmane.org>
2004-02-16 12:49 ` Bruno Ducrot [this message]
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=20040216124946.GO13262@poupinou.org \
--to=ducrot-kk6yzipjem5g9huczpvpmw@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=seife-T+3qhDtrTvDv8lqoKu5MV4HBZQ1bDw0s@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