From: "Arminder Singh" <arminders208@outlook.com>
To: "Alexander D" <aenv067@gmail.com>, devel@edk2.groups.io
Subject: Re: [edk2-devel] [Question] How do you set PCIe host bridge address space granularity for a PCI host bridge defined with PciHostBridgeLib?
Date: Mon, 29 Jul 2024 17:19:11 -0700 [thread overview]
Message-ID: <4791.1722298751229097446@groups.io> (raw)
In-Reply-To: <32224.1721852890188999603@groups.io>
[-- Attachment #1: Type: text/plain, Size: 941 bytes --]
Hello, thanks for the clarification! Couple of questions.
1) when implementing PciHostBridgeLib, are we supposed to put host addresses (address the CPU uses after translation) in the Mem/MemAbove4G apertures or PCI/device addresses? (address the device uses before translation)
2) Does the 'Mem' aperture have to be a 32 bit address/limit from host perspective?
3) Does translation have to be 0 for Mem/MemAbove4G apertures in the PCI_ROOT_BRIDGE struct? Most example platforms do that, but I'm not sure if that's a requirement for PciHostBridgeLib or just convention.
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120071): https://edk2.groups.io/g/devel/message/120071
Mute This Topic: https://groups.io/mt/107528139/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
[-- Attachment #2: Type: text/html, Size: 1414 bytes --]
next prev parent reply other threads:[~2024-07-30 0:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-24 15:29 [edk2-devel] [Question] How do you set PCIe host bridge address space granularity for a PCI host bridge defined with PciHostBridgeLib? Arminder Singh
2024-07-24 20:28 ` Alexander D
2024-07-24 21:14 ` Alexander D
2024-07-30 0:19 ` Arminder Singh [this message]
2024-07-30 2:35 ` Alexander D
2024-08-05 17:58 ` Arminder Singh
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-list 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=4791.1722298751229097446@groups.io \
--to=devel@edk2.groups.io \
/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