public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Yoshinoya" <yoshinoyatoko@163.com>
To: devel@edk2.groups.io
Subject: [edk2-devel] PciBus scan: Does it support scan from EndBusNum to StartBusNum?
Date: Tue, 21 Feb 2023 10:47:56 +0800 (CST)	[thread overview]
Message-ID: <6191f43c.1130.18671dedda8.Coremail.yoshinoyatoko@163.com> (raw)
In-Reply-To: <523c743c.7b4.18671950c08.Coremail.yoshinoyatoko@163.com>

[-- Attachment #1: Type: text/plain, Size: 134 bytes --]

Hi
Usually PciBus scan is from low bus num to high bus num.
     
So, does it support scan from end bus num to start bus num?


Thanks

[-- Attachment #2: Type: text/html, Size: 943 bytes --]

  reply	other threads:[~2023-02-21  2:48 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 [this message]
2023-02-21 19:18           ` Pedro Falcato
2023-02-22  1:10             ` Tiger Liu(BJ-RD)
2023-02-22  1:22               ` Pedro Falcato
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=6191f43c.1130.18671dedda8.Coremail.yoshinoyatoko@163.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