From: "Ni, Ruiyu" <ruiyu.ni@intel.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: edk2-devel-01 <edk2-devel@lists.01.org>
Subject: Re: PciSegmentInfoLib instances
Date: Mon, 28 May 2018 02:55:53 +0000 [thread overview]
Message-ID: <734D49CCEBEEF84792F5B80ED585239D5BD0C8CB@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <110011b4-f9cc-9f8b-53f8-f12cfe7416b2@redhat.com>
No. There is no such instance.
My understanding:
Segment is just to separate the PCI devices to different groups.
Each group of devices use the continuous BUS/IO/MMIO resource.
Each group has a BASE PCIE address that can be used to access PCIE configuration in MMIO way.
So with the above understanding, even a platform which has single segment can be implemented as
a multiple segments platform.
Thanks/Ray
> -----Original Message-----
> From: edk2-devel <edk2-devel-bounces@lists.01.org> On Behalf Of Laszlo
> Ersek
> Sent: Wednesday, May 23, 2018 3:38 PM
> To: Ni, Ruiyu <ruiyu.ni@intel.com>
> Cc: edk2-devel-01 <edk2-devel@lists.01.org>
> Subject: [edk2] PciSegmentInfoLib instances
>
> Hi Ray,
>
> do you know of any open source, non-Null, PciSegmentInfoLib instance?
> (Possibly outside of edk2?)
>
> More precisely, it's not the PciSegmentInfoLib instance itself that's of
> particular interest, but the hardware and the platform support code that
> offer multiple PCIe segments.
>
> Thanks
> Laszlo
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2018-05-28 2:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-23 7:37 PciSegmentInfoLib instances Laszlo Ersek
2018-05-28 2:55 ` Ni, Ruiyu [this message]
2018-05-28 20:36 ` Bill Paul
2018-06-01 20:04 ` Brian J. Johnson
2018-06-01 20:50 ` Andrew Fish
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=734D49CCEBEEF84792F5B80ED585239D5BD0C8CB@SHSMSX104.ccr.corp.intel.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