public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Pedro Falcato" <pedro.falcato@gmail.com>
To: "Tiger Liu(BJ-RD)" <TigerLiu@zhaoxin.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"yoshinoyatoko@163.com" <yoshinoyatoko@163.com>
Subject: Re: [edk2-devel] PciBus scan: Does it support scan from EndBusNum to StartBusNum?
Date: Wed, 22 Feb 2023 01:22:02 +0000	[thread overview]
Message-ID: <CAKbZUD291NGdFUtgzyueRP3qDkvoCswfTY0ADQ3rdXFHb7HVtw@mail.gmail.com> (raw)
In-Reply-To: <effd2f65aaee4e49a4ba7c11959e10b0@zhaoxin.com>

On Wed, Feb 22, 2023 at 1:10 AM Tiger Liu(BJ-RD) <TigerLiu@zhaoxin.com> wrote:
>
> Hi, Pedro:
> Thanks for your reply!
>
> For example:
> There are 4 root bridges in a server motherboard, named them as : RP-A / RP-B / RP-C / RP-D
> RP-A : PCI Bus num range is 0 ~0x40 (hardware pre-configured)
> RP-B : PCI Bus num range is 0x40 ~0x80 (hardware pre-configured)
> RP-C : PCI Bus num range is 0x80 ~0xA0 (hardware pre-configured)
> RP-D : PCI Bus num range is 0xA0 ~0xE0 (hardware pre-configured)
>
> Usually, we create pci root bridge instances with sequence RP-A / RP-B / RP-C / RP-D.
> So, Pci bus driver scan pci root bridge sequence is RP-A/RP-B/RP-C/RP-D.
>
> So, could I rewrite pci root bridge driver with different root bridge report sequence?
> For example:
> I let pci root bridge driver create RP-D's pci root bridge io protocol first, and then RP-C / RP-B / RP-A, and so pci bus briver could scan RP-D's pci bus range first?

Hi,

>From a brief look at
MdeModulePkg/Bus/Pci/PciHostBridgeDxe/PciHostBridge.c, it does seem
that it should enumerate in the order the root bridges were given by
PciHostBridgeGetRootBridges.
I don't know if this reflects your internal code. If so, I would try
just swapping the bridges in your PciHostBridgeGetRootBridges
implementation.

Although since I'm lacking details, I'll assume you really shouldn't
do this? I'm failing to see what purpose this can have, apart from
some other code that needs to be fixed.

-- 
Pedro

  reply	other threads:[~2023-02-22  1:22 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-05 11:32 [edk2-devel] Python368.efi failed to run in shell environment Yoshinoya
2022-10-05 16:28 ` Michael D Kinney
2022-10-11 10:20   ` Yoshinoya
2022-10-18  9:04     ` Jayaprakash, N
2022-10-19  8:30       ` Yoshinoya
2022-10-19 13:16         ` Jayaprakash, N
2022-10-20  3:06           ` Yoshinoya
2022-10-20  3:18             ` Jayaprakash, N
2022-11-08  3:16 ` [edk2-devel] Access 64bit address space in 32bit mode Yoshinoya
2022-11-09 17:20   ` Andrew Fish
2022-11-09 18:58     ` vincent zimmer
2022-11-09 20:14       ` Andrew Fish
2023-02-18  0:55         ` [edk2-devel] PciBus scan: Does it support scan from EndBusNum to StartBusNum? Yoshinoya
2023-02-20  4:28           ` Yoshinoya
2023-02-21  1:27           ` Yoshinoya
2023-02-21  2:47             ` Yoshinoya
2023-02-21 19:18           ` Pedro Falcato
2023-02-22  1:10             ` Tiger Liu(BJ-RD)
2023-02-22  1:22               ` Pedro Falcato [this message]
2023-05-23  9:55           ` [edk2-devel] PciHostBridge: dynamic pcie bus limit assignment Yoshinoya
2022-11-09 20:40     ` [edk2-devel] Access 64bit address space in 32bit mode Brian J. Johnson
2023-01-03  9:04       ` [edk2-devel] PciBus driver: support pcie 4.0 bus/device enumeration ? Yoshinoya

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=CAKbZUD291NGdFUtgzyueRP3qDkvoCswfTY0ADQ3rdXFHb7HVtw@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