From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Vladimir Olovyannikov <vladimir.olovyannikov@broadcom.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: Using a generic PciHostBridgeDxe driver for a multi-PCIe-domain platform
Date: Tue, 30 May 2017 16:35:28 +0000 [thread overview]
Message-ID: <CAKv+Gu_f_7bSMymyZiC9QOAm-_RDJEn_oL_Y0r5z_42dy9m1uA@mail.gmail.com> (raw)
In-Reply-To: <4220315aed43c05b37b1b71a9eff432e@mail.gmail.com>
On 30 May 2017 at 16:23, Vladimir Olovyannikov
<vladimir.olovyannikov@broadcom.com> wrote:
> Hi,
>
> I've started PCIe stack implementation design for an armv8 aarch64
> platform.
> The platform's PCIe represents several host bridges, and each hostbridge
> has one rootbridge.
> They do not share any resources between each other.
> Looking into the PciHostBridgeDxe implementation I can see that it
> supports only one hostbridge, and there is a comment:
> // Most systems in the world including complex servers have only one Host
> Bridge.
>
> So in my case should I create my own PciHostBridgeDxe driver supporting
> multiple hostbridges and do not use the Industry standard driver?
> I am very new to it, and will appreciate any help or idea.
>
As far as I can tell, PciHostBridgeLib allows you to return an
arbitrary number of PCI host bridges, each with their own segment
number. I haven't tried it myself, but it is worth a try whether
returning an array of all host bridges on your platform works as
expected.
next prev parent reply other threads:[~2017-05-30 16:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-30 16:23 Using a generic PciHostBridgeDxe driver for a multi-PCIe-domain platform Vladimir Olovyannikov
2017-05-30 16:35 ` Ard Biesheuvel [this message]
2017-05-30 16:49 ` Vladimir Olovyannikov
2017-05-30 17:34 ` Bill Paul
2017-05-30 18:11 ` Vladimir Olovyannikov
2017-05-31 15:02 ` Johnson, Brian (EXL - Eagan)
2017-05-31 18:07 ` Kinney, Michael D
2017-05-30 18:32 ` Laszlo Ersek
2017-05-30 18:50 ` Laszlo Ersek
2017-05-30 19:04 ` Vladimir Olovyannikov
2017-05-30 20:17 ` Laszlo Ersek
2017-05-30 20:23 ` Vladimir Olovyannikov
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=CAKv+Gu_f_7bSMymyZiC9QOAm-_RDJEn_oL_Y0r5z_42dy9m1uA@mail.gmail.com \
--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