From: Vladimir Olovyannikov <vladimir.olovyannikov@broadcom.com>
To: Laszlo Ersek <lersek@redhat.com>, edk2-devel@lists.01.org
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: Re: Using a generic PciHostBridgeDxe driver for a multi-PCIe-domain platform
Date: Tue, 30 May 2017 13:23:18 -0700 [thread overview]
Message-ID: <eb92759a6bb62c5f1025f69a8405907c@mail.gmail.com> (raw)
In-Reply-To: <4b898f0d-dbbf-20ea-120e-927ebb786b35@redhat.com>
> -----Original Message-----
> From: Laszlo Ersek [mailto:lersek@redhat.com]
> Sent: May-30-17 1:17 PM
> To: Vladimir Olovyannikov; edk2-devel@lists.01.org
> Cc: Ard Biesheuvel
> Subject: Re: [edk2] Using a generic PciHostBridgeDxe driver for a
> multi-PCIe-
> domain platform
>
> On 05/30/17 21:04, Vladimir Olovyannikov wrote:
>
> > So basically my PciHostBridgeLib should treat hostbridges as
> > rootbridges with different segments in this case?
>
> In my opinion, yes.
>
> I would actually put it as
>
> treat the set of sole root bridges on all the host bridges as multiple
> root bridges on a single host bridge, just with different segment
> numbers
>
> The separate segment numbers should be mapped to the separate ECAM
> windows in your PciSegmentLib instance, in my opinion.
OK, got it. Thanks a lot for your help!
>
> Thanks,
> Laszlo
prev parent reply other threads:[~2017-05-30 20:22 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
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 [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-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=eb92759a6bb62c5f1025f69a8405907c@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