From: Ducrot Bruno <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
To: NoZizzing OrDripping
<nozizzingordripping-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
Cc: Ducrot Bruno <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: ACPI trouble (AC module, etc.) with Toshiba 1115-S103
Date: Fri, 13 Dec 2002 23:22:01 +0100 [thread overview]
Message-ID: <20021213222201.GU4327@poup.poupinou.org> (raw)
In-Reply-To: <20021211065826.5869.qmail-ugbtuMWqwv6A/QwVtaZbd3CJp6faPEW9@public.gmane.org>
On Tue, Dec 10, 2002 at 10:58:26PM -0800, NoZizzing OrDripping wrote:
> --- Ducrot Bruno <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org> wrote:
...
>
> OK, I went thru the process of creating a modified
> ASL (diffs from the original attached) for this
> laptop.
> Basically, I cleaned up the original so that the
> errors
> from "iasl" went away.
>
> I now have a working AC module.
>
> This is a stopgap measure though, correct? The goal
> should be for the Linux kernel to support the existing
> AML in flash (the AML apparently comes from Microsoft)
No, it come from your BIOS. Microsoft make only a
interpreter for it, as for ACPI-CA.
> on these laptops. The BIOS on these machines is about
> as fresh as it gets (Nov, 2002). It seems to me that
> the Intel ASL compiler and interpreter needs to be
> changed/relaxed to accomodate what has become a
> defacto
> (de-gates-o) standard here.
>
> As a practical matter, I can't imagine non-programmer
> types having to modify their ASL code to make Linux
> work on their laptops, and I can't imagine that Ducrot
> wants to be the single, worldwide point, for modified
No, I don't want to. FreeBSD acpi team is good also for
this stuff as well.
> Would the ACPI developers be receptive if I made the
> changes necessary to allow the kernel ACPI code to
> accept the existing AML in my laptop as-is?
It's up to Intel ACPI guy to decide, but if I were them,
I will _not_ allow to do the same kind of bug as MS.
Imagine if they have to program as a MS developper...
--
Ducrot Bruno
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
next prev parent reply other threads:[~2002-12-13 22:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-10 6:59 ACPI trouble (AC module, etc.) with Toshiba 1115-S103 NoZizzing OrDripping
[not found] ` <20021210065922.31967.qmail-4GJ6zp1JX++A/QwVtaZbd3CJp6faPEW9@public.gmane.org>
2002-12-10 9:23 ` Ducrot Bruno
[not found] ` <20021210092357.GA29390-j6u/t2rXLliUoIHC/UFpr9i2O/JbrIOy@public.gmane.org>
2002-12-11 6:58 ` NoZizzing OrDripping
2002-12-11 12:41 ` Derek Broughton
[not found] ` <20021211065826.5869.qmail-ugbtuMWqwv6A/QwVtaZbd3CJp6faPEW9@public.gmane.org>
2002-12-13 22:22 ` Ducrot Bruno [this message]
2002-12-13 0:43 ` NoZizzing OrDripping
[not found] ` <20021213004316.39542.qmail-ugbtuMWqwv6A/QwVtaZbd3CJp6faPEW9@public.gmane.org>
2002-12-13 15:21 ` Ducrot Bruno
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=20021213222201.GU4327@poup.poupinou.org \
--to=ducrot-kk6yzipjem5g9huczpvpmw@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=nozizzingordripping-/E1597aS9LQAvxtiuMwx3w@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.