From: Jean Delvare <khali@linux-fr.org>
To: "Moore, Robert" <robert.moore@intel.com>
Cc: "Brown, Len" <len.brown@intel.com>,
linux-acpi@vger.kernel.org, Pavel Machek <pavel@ucw.cz>
Subject: Re: ACPI requesting I/O ports?
Date: Sat, 3 Mar 2007 10:21:42 +0100 [thread overview]
Message-ID: <20070303102142.6d1ed107.khali@linux-fr.org> (raw)
In-Reply-To: <B28E9812BAF6E2498B7EC5C427F293A402021AFD@orsmsx415.amr.corp.intel.com>
Hi Robert,
On Fri, 2 Mar 2007 14:05:45 -0800, Moore, Robert wrote:
> Port addresses can be dynamically generated by the AML code and thus,
> there is no way that the ACPI subsystem can statically predict any
> addresses that will be accessed by the AML.
Can you please explain in greater details how "dynamical" it is? Any
real world example you could present?
Also, you say that port addresses _can_ be dynamically generated, which
suggests that some are not, so the ACPI subsystem could at least
properly request these ones?
Thanks,
--
Jean Delvare
prev parent reply other threads:[~2007-03-03 9:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-02 21:14 ACPI requesting I/O ports? Jean Delvare
2007-03-02 22:05 ` Moore, Robert
2007-03-03 9:21 ` Jean Delvare [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=20070303102142.6d1ed107.khali@linux-fr.org \
--to=khali@linux-fr.org \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=robert.moore@intel.com \
/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