[RTEMS Project] #2067: Algorithm to determine max. PCI bus number is incorrect

RTEMS trac trac at rtems.org
Wed Dec 24 03:30:27 UTC 2014


#2067: Algorithm to determine max. PCI bus number is incorrect
----------------------+----------------------------
 Reporter:  strauman  |       Owner:  joel.sherrill
     Type:  defect    |      Status:  new
 Priority:  highest   |   Milestone:  4.11
Component:  bsps      |     Version:  4.10
 Severity:  normal    |  Resolution:
 Keywords:            |
----------------------+----------------------------

Comment (by Till Strauman <strauman@…>):

 In [changeset:"2573e698d1a5f2e481b5b0520a949c4f590bacbd/rtems"]:
 {{{
 #!CommitTicketReference repository="rtems"
 revision="2573e698d1a5f2e481b5b0520a949c4f590bacbd"
 pc386: scan all functions of multi-function PCI devices

  The current 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.

  This commit makes sure that the scan
  is extended to all functions of multi-function
  devices.

  See #2067
 }}}

--
Ticket URL: <http://devel.rtems.org/ticket/2067#comment:5>
RTEMS Project <http://www.rtems.org/>
RTEMS Project


More information about the bugs mailing list