[RTEMS Project] #2067: Algorithm to determine max. PCI bus number is incorrect
RTEMS trac
trac at rtems.org
Wed Dec 24 03:31:56 UTC 2014
#2067: Algorithm to determine max. PCI bus number is incorrect
----------------------+----------------------------
Reporter: strauman | Owner: joel.sherrill
Type: defect | Status: closed
Priority: highest | Milestone: 4.11
Component: bsps | Version: 4.10
Severity: normal | Resolution: fixed
Keywords: |
----------------------+----------------------------
Changes (by gedare):
* status: new => closed
* resolution: => fixed
Old description:
> The algorithm scans all PCI busses (0..ff)
> and all devices (0..31) on each bus for bridges
> and determines the maximum of all subordinate
> busses encountered.
>
> However, the algorithm does not scan all functions
> present in multi-function devices -- I have a PCI express
> root complex (82801H) where multiple (non-zero index)
> functions are 'PCI bridges' whose subordinate bus number is
> missed by the original algorithm.
>
> The attached patch makes sure that the scan
> is extended to all functions of multi-function
> devices.
New description:
The algorithm scans all PCI busses (0..ff)
and all devices (0..31) on each bus for bridges
and determines the maximum of all subordinate
busses encountered.
However, the algorithm does not scan all functions
present in multi-function devices -- I have a PCI express
root complex (82801H) where multiple (non-zero index)
functions are 'PCI bridges' whose subordinate bus number is
missed by the original algorithm.
The attached patch makes sure that the scan
is extended to all functions of multi-function
devices.
--
Comment:
Patch reformatted to fix whitespace and applied to master and release
branches 4.10 and 4.9
--
Ticket URL: <http://devel.rtems.org/ticket/2067#comment:6>
RTEMS Project <http://www.rtems.org/>
RTEMS Project
More information about the bugs
mailing list