public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Derek Broughton <dbroughton-F3m4/jXepmf3fQ9qLvQP4Q@public.gmane.org>
To: ACPI Development - Sourceforge
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: ACPI trouble (AC module, etc.) with Toshiba 1115-S103
Date: Wed, 11 Dec 2002 08:41:41 -0400	[thread overview]
Message-ID: <00ce01c2a112$a79ddfe0$3746028e@bio.dfo.ca> (raw)
In-Reply-To: 20021211065826.5869.qmail@web14503.mail.yahoo.com

From: "NoZizzing OrDripping" <nozizzingordripping-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
>
> 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)

Not if it doesn't conform to the ACPI spec. I wouldn't have a clue if this
does - but MS is well known for going their own way.  If that was the case, then
the goal would be to get your PC vendor to get a correct DSDT - we shouldn't be
trying to make ACPI work with every possible broken BIOS.



-------------------------------------------------------
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/

  reply	other threads:[~2002-12-11 12:41 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 [this message]
     [not found]         ` <20021211065826.5869.qmail-ugbtuMWqwv6A/QwVtaZbd3CJp6faPEW9@public.gmane.org>
2002-12-13 22:22           ` Ducrot Bruno
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='00ce01c2a112$a79ddfe0$3746028e@bio.dfo.ca' \
    --to=dbroughton-f3m4/jxepmf3fq9qlvqp4q@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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