[U-Boot-Users] RE: PCI bus/bridge mis-configuration

Brendan Beahan bbeahan at auspace.com.au
Fri Feb 14 01:05:04 CET 2003

I don't think the problem is present in the uboot-0.2.0 code.

I think my vendor extended the pciauto_setup_bars() function in ppcboot-1.1.6 to setup expansion ROM space as well as BARs.  This change introduced the bug which led to pci bus misconfiguration.
I've checked the code for uboot 0.2.0, and the equivalent function pciauto_setup_device() seems to deal with BARs only, not expansion ROM space, so I wouldn't expect similar problems with uboot.


Brendan Beahan
Senior Communications Engineer
Innovation House
First Ave, Technology Park
Mawson Lakes SA 5095
Tel +61 8 8260 8225
Fax +61 8 8260 8226
Web www.auspace.com.au

This email is for the intended addressee only. If you have received this e-mail in error, you are requested to contact the sender and delete the e-mail.
Nothing in this email shall bind Auspace Limited in any contract or obligation.


-----Original Message-----
From: Wolfgang Denk [mailto:wd at denx.de]
Sent: Thursday, 13 February 2003 5:41 PM
To: Brendan Beahan
Cc: u-boot-users at lists.sourceforge.net
Subject: Re: [U-Boot-Users] RE: PCI bus/bridge mis-configuration 

In message <A98C65978BCE2948BA1C01E8D5819B3E0B3F98 at nomax.auspace.com.au> you wrote:
> SOLVED !!!
> The problem lay in ppcboot.  An logical error when scanning the =

Two questions:

* Is the problem still present in the current U-Boot code?

* If so, where is your patch? ;-)

Best regards,

Wolfgang Denk

Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd at denx.de
See us @ Embedded World, Nuremberg, Feb 18-20, Hall 12.0 Booth 12-442

More information about the U-Boot mailing list