public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] U-Boot allocating PCI I/O space from 0 (Was: pata_sl82c105 can not	reserve IO region)
Date: Sat, 02 Dec 2006 19:33:37 +0300	[thread overview]
Message-ID: <4571AAE1.1020609@ru.mvista.com> (raw)
In-Reply-To: <45718F55.4080903@ru.mvista.com>

Hello.

Sergei Shtylyov wrote:

>     Well, I'm having a very related issue with the U-Boot on MPC85xx: recently 
> I've noticed that it started allocating PCI I/O space from 0 (while the older 
> versions started from 0x1000). The IDE core can't tolerate this, giving me 
> such messages on bootup:

> PDC20269: inconsistent baseregs (BIOS) for port 0, skipping

> when I have Promise Ultra133TX2 card inserted into PCI alone. I've looked thru 
> the U-Boot sources and commit history but failed to locate the change that led 
> to this...

    It's actually much worse than just that. When I also plug in some other 
PCI card so Ultra133TX2 doesn't get the zero addresses anymore, I'm getting this:

eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin
<saw@saw.sw.com.sg> and others
eth3: Invalid EEPROM checksum 0xfffe, check settings before activating this
device!
eth3: OEM i82557/i82558 10/100 Ethernet, 00:00:00:00:FF:FF, IRQ 52.
[...]
PDC20269: 100% native mode on irq 51
     ide2: BM-DMA at 0x0060-0x0067, BIOS settings: hde:pio, hdf:pio
PDC20269: simplex device: DMA disabled
ide3: PDC20269 Bus-Master DMA disabled (BIOS)

    I've just verified that both these cards are working OK in x86 box
As for the simplex message, I've encountered this some months ago and it was 
caused by invalid programming of the MPC85xx bridge PCI/X outbound translation 
address register for the I/O space or at least by the non-zero value of the 
bus I/O address in the "ranges" property of the bridge device node in the 
device tree... I'm somewhat confused now since I know that the relevant U-Boot 
code has been fixed but it looks like that made it only worse -- I was using 
the custom patched version of U-Boot before which missed that fix:

http://www.denx.de/cgi-bin/gitweb.cgi?p=u-boot.git;a=commitdiff;h=97074ed9655309b64231bc2cee69fe85399f8055

WBR, Sergei

  reply	other threads:[~2006-12-02 16:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20061130165202.GA23205@aepfle.de>
     [not found] ` <20061130171049.7b80a40c@localhost.localdomain>
     [not found]   ` <20061130184748.GA24071@aepfle.de>
     [not found]     ` <20061201183355.GA9701@aepfle.de>
     [not found]       ` <45707CF8.3090106@ru.mvista.com>
     [not found]         ` <1165010029.22108.10.camel@localhost.localdomain>
     [not found]           ` <20061201221525.7a741062@localhost.localdomain>
     [not found]             ` <1165011583.22108.17.camel@localhost.localdomain>
2006-12-02 14:36               ` [U-Boot-Users] U-Boot allocating PCI I/O space from 0 (Was: pata_sl82c105 can not reserve IO region) Sergei Shtylyov
2006-12-02 16:33                 ` Sergei Shtylyov [this message]
2006-12-26 20:53                   ` Sergei Shtylyov

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-all 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=4571AAE1.1020609@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=u-boot@lists.denx.de \
    /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