From: Clemens Koller <clemens.koller@anagramm.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] 85xx pci problems
Date: Fri, 30 Nov 2007 16:19:23 +0100 [thread overview]
Message-ID: <475029FB.8020409@anagramm.de> (raw)
In-Reply-To: <f87675ee0711300653p44f85d2cm3d2841db3d6f2c16@mail.gmail.com>
Hi, Robert!
robert lazarski schrieb:
> On Nov 30, 2007 9:46 AM, Kumar Gala <galak@kernel.crashing.org> wrote:
>>> We are putting the o-scope on the board to look for hardware issues.
>>> Any help on what to look for concerning PCI hardware issues or my TLB
>>> / device tree issues would be highly appreciated - we're running out
>>> of time!
>> maybe I missed it but what's the issue?
>>
>> - k
>>
>
> No cards are recognized. We can, for example, put a Intel pro 100
> ethernet card into a PC and see it recognized via lspci.
> Nothing we try shows any info for this card in dmesg or lspci, or any other card.
Make sure your clocks and resets are okay.
- Then put only one device after each other on the pci bus (if possible)
- check the IDSELects fit to the u-boot / kernel configuration
- check the INT{A,B,C,D} fits to the IRQn# mapping to the kernel / the correct IDSELs.
See the pci at e0008000 { ... } entry in the device tree.
This stuff has to fit to your hardware.
> We are looking for clues and another set of eyes to see if we have
> software or hardware issues, or some combination.
Yes, it's the combination ;-)
Regards,
Clemens Koller
__________________________________
R&D Imaging Devices
Anagramm GmbH
Rupert-Mayer-Stra?e 45/1
Linhof Werksgel?nde
D-81379 M?nchen
Tel.089-741518-50
Fax 089-741518-19
http://www.anagramm-technology.com
next prev parent reply other threads:[~2007-11-30 15:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-30 14:07 [U-Boot-Users] 85xx pci problems robert lazarski
2007-11-30 14:46 ` Kumar Gala
2007-11-30 14:53 ` robert lazarski
2007-11-30 15:01 ` Kumar Gala
2007-11-30 15:19 ` Clemens Koller [this message]
2007-11-30 15:02 ` Kumar Gala
2007-12-14 4:54 ` sivaji
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=475029FB.8020409@anagramm.de \
--to=clemens.koller@anagramm.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