From: Ducrot Bruno <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
To: "Li, Shaohua" <shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: ACPI/ECDT on gateway 200x notebook
Date: Wed, 7 Jan 2004 11:54:24 +0100 [thread overview]
Message-ID: <20040107105424.GM14031@poupinou.org> (raw)
In-Reply-To: <571ACEFD467F7749BC50E0A98C17CDD8E84E7B-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
On Wed, Jan 07, 2004 at 09:04:25AM +0800, Li, Shaohua wrote:
> Yes, the patch may resolve some problems, but it is just a workaround. I guess a possible solution is if ECDT is lacked, scan namespace to get EC device's info, such as GPE, IO ports, then use these info to automatically make a fake ECDT. Because getting info doesn't involve any operating on EC device, it's feasible. A problem is if a system has more than 1 EC, how do we?
>
Yes, exactly. Anyway, io ports 0x62, 0x66 are the legacy access
for the "main" EC. Perhaps checking those ports and initilializing
that one only may be OK?
--
Ducrot Bruno
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
next prev parent reply other threads:[~2004-01-07 10:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 1:04 ACPI/ECDT on gateway 200x notebook Li, Shaohua
[not found] ` <571ACEFD467F7749BC50E0A98C17CDD8E84E7B-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-01-07 10:54 ` Ducrot Bruno [this message]
[not found] ` <20040107105424.GM14031-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2004-01-13 15:26 ` Greg Sarjeant
-- strict thread matches above, loose matches on Subject: below --
2004-01-14 2:23 Yu, Luming
[not found] ` <3ACA40606221794F80A5670F0AF15F8401720CCA-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-01-30 17:13 ` William Morgan
2004-01-12 5:39 Yu, Luming
2004-01-07 11:57 Yu, Luming
[not found] ` <3ACA40606221794F80A5670F0AF15F8401720C89-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-01-07 12:40 ` Ducrot Bruno
2004-01-04 2:01 Rich Ibbotson
[not found] ` <3FF773E5.5070102-aYIB8uWIUb2Vn7q6wjsIow@public.gmane.org>
2004-01-04 2:07 ` Casey Harkins
[not found] ` <Pine.LNX.4.44.0401032005180.7785-100000-j0XSImJ06nG869pVMd/zofZ8FUJU4vz8@public.gmane.org>
2004-01-06 18:34 ` Ducrot Bruno
[not found] ` <20040106183426.GJ14031-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2004-01-07 0:39 ` Rich Ibbotson
[not found] ` <3FFB552F.8030508-aYIB8uWIUb2Vn7q6wjsIow@public.gmane.org>
2004-01-07 10:49 ` Ducrot Bruno
[not found] ` <20040107104941.GL14031-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2004-01-07 16:47 ` Greg Sarjeant
[not found] ` <20040107114742.1f2de5b1.greg-QNIYhHqVzB9kr2E5YSwMOQ@public.gmane.org>
2004-01-07 17:17 ` Ducrot Bruno
[not found] ` <20040107171708.GQ14031-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2004-01-07 17:21 ` Greg Sarjeant
2004-01-07 17:12 ` Greg Sarjeant
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=20040107105424.GM14031@poupinou.org \
--to=ducrot-kk6yzipjem5g9huczpvpmw@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=shaohua.li-ral2JQCrhuEAvxtiuMwx3w@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