public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Anders Rune Jensen <anders-VYFdHW3tBKJknbxzx/v8hQ@public.gmane.org>
To: linux-laptop-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [ACPI] Toshiba Tecra vs ACPI
Date: Tue, 26 Aug 2003 08:49:58 +0200	[thread overview]
Message-ID: <867k50oquh.fsf@gnulinux.dk> (raw)
In-Reply-To: <BF1FE1855350A0479097B3A0D2A80EE009FCAD-N2PTB0HCzHJF3Yvz3xaN/VDQ4js95KgL@public.gmane.org> (Len Brown's message of "Thu, 21 Aug 2003 20:30:23 -0400")

[-- Attachment #1: Type: text/plain, Size: 1329 bytes --]

"Brown, Len" <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> writes:

> Does anybody have a Toshiba Tecra that boots an ACPI-enabled kernel?

I have a Tecra 8200 that boots 2.6.0-test4-mm1 just fine. I've
included the dmidecode output, the acpidmp and a dmesg. The bios
should be the latest available (1.6 from 2002). I normally run apm
though but have been running acpi before with 2.4 kernels.

> If yes, can you send me the output from dmidecode so that I can identify
> the BIOS date?
> http://www.nongnu.org/dmidecode/  (I'd also be intersted in the output
> of acpidmp)
>
> I've found that the Tecra 8100 has AML bugs that we can't handle
> (missing return statements when they are required).  And we will not be
> able to handle them any time soon (w/o a DSDT over-ride).
>
> So I'm thinking about black-listing the 8100 by default; and the 8000
> and 8200 may be right behind it.  Unfortunately, the DMI info for the
> 8100 has an empty product name under system information, where one would
> expect to see "Tecra 8100".  So I'm thinking about disabling ACPI by
> default on all systems with DMI BIOS vendor "TOSHIBA", BIOS Release Date
> <= 10/07/2002 -- the date of the latest BIOS for the 8100; and Base
> Board product name "Portable PC".
>
> Thanks,
> -Len

-- 
Anders Rune Jensen
http://www.gnulinux.dk/~arj/


[-- Attachment #2: dmesg --]
[-- Type: application/octet-stream, Size: 4197 bytes --]

[-- Attachment #3: dmi --]
[-- Type: application/octet-stream, Size: 519 bytes --]

[-- Attachment #4: acpidmp --]
[-- Type: application/octet-stream, Size: 30738 bytes --]

      parent reply	other threads:[~2003-08-26  6:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-22  0:30 Toshiba Tecra vs ACPI Brown, Len
     [not found] ` <BF1FE1855350A0479097B3A0D2A80EE009FCAD-N2PTB0HCzHJF3Yvz3xaN/VDQ4js95KgL@public.gmane.org>
2003-08-26  6:49   ` Anders Rune Jensen [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=867k50oquh.fsf@gnulinux.dk \
    --to=anders-vyfdhw3tbkjknbxzx/v8hq@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=linux-laptop-u79uwXL29TY76Z2rM5mHXA@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