To: devel@acpica.org
Subject: Re: [Devel] Error in documentation of AcpiOsDerivePciId?
Date: Thu, 22 Apr 2010 14:50:20 +0200 [thread overview]
Message-ID: <4BD0460C.9080504@gmail.com> (raw)
In-Reply-To: 1271892788.7939.9.camel@localhost
[-- Attachment #1: Type: text/plain, Size: 1145 bytes --]
Hi Lin,
Many thanks for your explanantion, I understand now why the second
argument passed to AcpiOsDerivePciId is a handle to the (PCI_Config)
operation region.
But regarding the first argument of AcpiOsDerivePciId: the ACPICA
programmer reference says that: it is a handle to _the PCI device_.
My question is: which PCI device?
In my (possibly wrong) interpretation of the documentation, _the PCI
device_ is the device for which AcpiOsDerivePciId shall return an
updated Pci id.
However, as far as I understand the code of AcpiEvPciConfigRegionSetup
(in file evrgnini.c), _the PCI device_ turns out to be an ancestor of
the device for which AcpiOsDerivePciId shall return an updated Pci id.
This ancestor being the upstream PCI root bridge (or the ACPI root node
if none was found). This interpretation of _the PCI device_ is also
consistent with my understanding of the Linux implementation of
AcpiOsDerivePciId, which finds the updated PCI id by ``traversing'' the
PCI-to-PCI bridges that are on the branch from AcpiOsDerivePciId's first
argument to its second argument.
Thanks for your help,
Grégoire
next reply other threads:[~2010-04-22 12:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 12:50 [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-08-04 23:33 [Devel] Error in documentation of AcpiOsDerivePciId? Moore, Robert
2010-08-04 21:36 Moore, Robert
2010-08-02 0:29 Lin Ming
2010-08-01 11:31 Rudi
2010-04-23 12:44 Lin Ming
2010-04-21 23:33 Lin Ming
2010-04-20 16:10 Moore, Robert
2010-04-20 16:07
2010-04-20 14:51 Moore, Robert
2010-04-20 9:45
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=4BD0460C.9080504@gmail.com \
--to=devel@acpica.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.