From: Sylvain Munaut <tnt@246tnt.com>
To: Stefano Gaiotto <Stefano.Gaiotto@marconi.com>,
"linuxppc-embedded@lists.linuxppc.org"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: PCI scanning and devices initialization
Date: Wed, 18 Aug 2004 14:54:43 +0200 [thread overview]
Message-ID: <41235193.4020906@246tNt.com> (raw)
In-Reply-To: <OF8D823500.2A30CF0C-ONC1256EF4.0040DDB4@uk.marconicomms.com>
Stefano Gaiotto wrote:
>Dear colleagues,
>
>I'm trying to use a device connected to a PCI bus, more exactly a
>PCI/PCMCIA bridge
>with u-boot-1.1.1 and Linux (2.4.24 and 2.6.8) in a board with MPC8270.
>
>Both u-boot and Linux, during scanning procedure show me only the PCI
>bridge [1057/18c0] but I can't see the devices connected to the bus.
>
>I'm a novice with PCI bus and I'm not sure the board is good (is the first
>prototype) and so I'd like to know if scanning procedure should tell me the
>devices
>connected or I have to do some device initialization before I can see them
>during scanning.
>
>I suppose I should see them during scanning and then initialise them via
>PCI bus.
>
>If my assumption is true, shall I suppose my hardware is not good? Or
>anything else?
>
>
Hi
Yes, there may be something wrong with your hardware. I'm not familiar
with the MPC8270 PCI code but your devices should show up during scan.
At the PCI init, PCI devices don't yet have an address, so the host
detects them using configuration cycles. Theses uses a different
addressing scheme, using each address line as a kind of "chip select".
So the devices know the host is "talking" to it just by looking at it's
IDSEL line going asserted. If on your board the IDSEL isn't wired
properly then it won't work. Hopefully if that's the case, you can just
wire it by hand, it's not a high speed signal.
Also, I've come accross some simple FPGA implementation of PCI devices
that just didn't respond to config ...
Sylvain
PS: I'm not a PCI expert and that's just my understanding. There is
probably a lot of things that can go wrong.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-08-18 12:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-18 11:52 PCI scanning and devices initialization Stefano Gaiotto
2004-08-18 12:54 ` Sylvain Munaut [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-18 13:28 Juergen.Beisert
2004-08-20 11:30 Stefano Gaiotto
2004-08-20 13:55 ` Steve Boorman
2004-08-20 11:40 Stefano Gaiotto
2004-08-20 15:23 Stefano Gaiotto
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=41235193.4020906@246tNt.com \
--to=tnt@246tnt.com \
--cc=Stefano.Gaiotto@marconi.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.