From: Andre Schwarz <andre.schwarz@matrix-vision.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] MPC837x PCIe no link
Date: Fri, 04 Mar 2011 17:27:12 +0100 [thread overview]
Message-ID: <4D7112E0.30603@matrix-vision.de> (raw)
All,
sorry to bother you again.
After my harddisk died I'm porting my latest 8377 work to TOT.
Unfortunately I'm lacking some commits that haven't been pushed to backup.
But everything's fine so far and the system is up and running, except PCIe.
Using the "old" binary left on the server PCIe has been working fine :
U-Boot 2010.12-rc1-00596-gcef659f-dirty (Nov 22 2010 - 17:22:20) MPC83XX
...
PCIE1: link
and the Wifi card is present and usable by Linux.
=> pci 2
Scanning PCI devices on bus 2
BusDevFun VendorId DeviceId Device Class Sub-Class
_____________________________________________________________
02.00.00 0x168c 0x001c Network controller 0x00
With latest code running on the *same piece of hardware*
U-Boot 2011.03-rc1-00129-g1ce1ed1-dirty (Mar 04 2011 - 16:31:40) MPC83XX
I get "PCIE1: No link"
Dumping SerDes (e3000 + e3100) and PCIe core (400-7ff) registers shows
now difference between both versions.
Any ideas what might be responsible for the link not being established ?
Regards,
Andr?
MATRIX VISION GmbH, Talstrasse 16, DE-71570 Oppenweiler
Registergericht: Amtsgericht Stuttgart, HRB 271090
Geschaeftsfuehrer: Gerhard Thullner, Werner Armingeon, Uwe Furtner
next reply other threads:[~2011-03-04 16:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 16:27 Andre Schwarz [this message]
2011-03-05 7:55 ` [U-Boot] MPC837x PCIe no link Baidu Liu
2011-03-06 13:27 ` Schwarz, Andre
2011-03-10 15:38 ` Andre Schwarz
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=4D7112E0.30603@matrix-vision.de \
--to=andre.schwarz@matrix-vision.de \
--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