public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Nate Lawson <nate-Y6VGUYTwhu0@public.gmane.org>
To: William Morgan <wmorgan-xW3KcqxHEMnk1uMJSBkQmQ@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: acpi on new gateway laptops
Date: Mon, 17 Nov 2003 10:54:51 -0800 (PST)	[thread overview]
Message-ID: <20031117104936.N60907@root.org> (raw)
In-Reply-To: <20031117183900.GA32570-xW3KcqxHEMnk1uMJSBkQmQ@public.gmane.org>

On Mon, 17 Nov 2003, William Morgan wrote:
> Excerpts (reformatted) from Nate Lawson's mail of 17 Nov 2003 (EST):
> > Your DSDT attempts to access regions before there is an attached EC to
> > service the calls to that space, yes.  So the two approaches are to
> > provide an ECDT or change the DSDT to not reference those spaces early
> > in boot.  The problem with the latter option is that those accesses
> > may be crucial to initializing your laptop.  So if you remove them, it
> > may start up in a partially initialized state.  It's probably cleaner
> > to provide an ECDT.
>
> Thanks for your reply! That's the sentiment others have expressed as
> well---the easiest thing to do is provide an ECDT. Unfortunately, we're
> not really sure how to do this, and no one seems able (or willing!) to
> say.
>
> The ACPI spec describes the contents of the table, but it's not clear to
> me how, exactly, what the "processor relative address of the embedded
> controller command/status register, in generic address structure format"
> is supposed to be. How can we discover all these gory details about the
> EC?

Get the data from the DSDT.  Dump it with acpidmp, search for PNP0C09,
then write down the resources.  Mine is below:

                Device (EC)
                {
                    Name (_HID, EisaId ("PNP0C09"))
                    Name (_UID, 0x00)
                    Name (_GPE, 0x1C)
                    ...
                    Name (_CRS, ResourceTemplate ()
                    {
                        IO (Decode16, 0x0062, 0x0062, 0x01, 0x01)
                        IO (Decode16, 0x0066, 0x0066, 0x01, 0x01)
                    })
                }

This corresponds to a GPE of 0x1c, control reg 0x66, data reg 0x62.  Below
is the correct ECDT for this EC:

  ECDT: Length=82, Revision=1, Checksum=5,
        OEMID=IBM, OEM Table ID=TP-1A, OEM Revision=0x1160,
        Creator ID=IBM, Creator Revision=0x1
        EC_CONTROL=0x66:0[8] (IO)
        EC_DATA=0x62:0[8] (IO)
        UID=0, GPE_BIT=0x1c
        EC_ID=\_SB.PCI0.LPC.EC

Note that I develop FreeBSD so Linux may have slightly different ways of
defining things.

-Nate


-------------------------------------------------------
This SF. Net email is sponsored by: GoToMyPC
GoToMyPC is the fast, easy and secure way to access your computer from
any Web browser or wireless device. Click here to Try it Free!
https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl

  parent reply	other threads:[~2003-11-17 18:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-12 23:23 acpi on new gateway laptops William Morgan
     [not found] ` <20031112232315.GD430-xW3KcqxHEMnk1uMJSBkQmQ@public.gmane.org>
2003-11-12 23:33   ` William Morgan
     [not found]     ` <20031112233328.GE430-xW3KcqxHEMnk1uMJSBkQmQ@public.gmane.org>
2003-11-13  0:10       ` Ducrot Bruno
     [not found]         ` <20031113001013.GE32464-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2003-11-13 17:03           ` William Morgan
     [not found]             ` <20031113170333.GA2336-xW3KcqxHEMnk1uMJSBkQmQ@public.gmane.org>
2003-11-18 15:11               ` Ducrot Bruno
     [not found]                 ` <20031118151139.GA32464-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2003-11-20 21:42                   ` William Morgan
2003-11-17 18:25   ` Nate Lawson
     [not found]     ` <20031117183900.GA32570@masanjin.net>
     [not found]       ` <20031117183900.GA32570-xW3KcqxHEMnk1uMJSBkQmQ@public.gmane.org>
2003-11-17 18:54         ` Nate Lawson [this message]
     [not found]           ` <20031117104936.N60907-Y6VGUYTwhu0@public.gmane.org>
2003-11-17 19:37             ` William Morgan
     [not found]               ` <20031117193719.GB32570-xW3KcqxHEMnk1uMJSBkQmQ@public.gmane.org>
2003-11-17 20:07                 ` Nate Lawson
     [not found]                   ` <20031117120555.E61216-Y6VGUYTwhu0@public.gmane.org>
2003-11-18 10:35                     ` Ducrot Bruno
     [not found]                       ` <20031118103549.GZ32464-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2003-11-20 21:36                         ` William Morgan
2003-12-08 23:19             ` Casey Harkins
     [not found]               ` <Pine.LNX.4.44.0312081716110.5824-100000-j0XSImJ06nG869pVMd/zofZ8FUJU4vz8@public.gmane.org>
2003-12-09  1:56                 ` Casey Harkins
     [not found]                   ` <Pine.LNX.4.44.0312081938000.6722-100000-j0XSImJ06nG869pVMd/zofZ8FUJU4vz8@public.gmane.org>
2003-12-12 17:11                     ` Casey Harkins
     [not found]                       ` <Pine.LNX.4.44.0312121109510.32380-100000-j0XSImJ06nG869pVMd/zofZ8FUJU4vz8@public.gmane.org>
2003-12-12 18:01                         ` Sérgio Monteiro Basto

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=20031117104936.N60907@root.org \
    --to=nate-y6vguytwhu0@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=wmorgan-xW3KcqxHEMnk1uMJSBkQmQ@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