From: David Hawkins <dwh@ovro•caltech.edu>
To: Peter LaDow <petela@gocougs•wsu.edu>
Cc: Anatolij Gustschin <agust@denx•de>, linuxppc-dev@lists•ozlabs.org
Subject: Re: Failure to detect PCI card
Date: Mon, 05 Aug 2013 19:01:04 -0700 [thread overview]
Message-ID: <520058E0.8080304@ovro.caltech.edu> (raw)
In-Reply-To: <CAN8Q1EfWOedMFKtFQbTmmydnLoLe24=c3Fo1Ao3sTdDmuYBJqQ@mail.gmail.com>
Hi Pete,
> On Mon, Aug 5, 2013 at 4:07 PM, Peter LaDow <petela@gocougs•wsu.edu> wrote:
>> However, replacing the 82540 based card with either a 3com 3C905TXM or
>> the Netgear FA331, there is no response on the 0x10 IDSEL line. Thus
>> it appears these cards are NOT responding to configuration reads. I
>> think I have to break out the scope and probe around for the 5V/3V. I
>> wouldn't think that the supplies are the issue since these are
>> universal cards, and as I understand it either 3V3 _or_ 5V can be
>> present, so these should work fine. Yet they aren't responding to PCI
>> configuration cycles.
It depends on what you define "Universal PCI" as :)
My definition is that the board works with either 5V or 3.3V PCI
signals. However, that definition does not tell you where the device
draws power from.
I suspect the lack of either the 5V or 3.3V power rail to the card
might be the problem.
Did you probe the PCI edge connect to see what supplies were present?
> A few more notes. I tried a variety of other cards, such as a PCI
> modem (WinMode, ack), a WinTV card, and a PCI based 802.11 card. All
> of them enumerate perfectly.
These could all be 3.3V cards ...
> Perhaps it is a BIOS option ROM like you suggested earlier. The
> 3c90xC reference manual I found
> (http://people.freebsd.org/~wpaul/3Com/3c90xc.pdf) mentions an option
> ROM (and there is an Atmel part stuffed). I can't find any technical
> information on the FA331 (yet), so I don't know about it.
>
> But regardless, wouldn't enumeration have to occur before any option
> ROM could even be used?
I've never had a card with an option ROM, so can't comment. I'd have
to look at the PCI spec. If you want me to look, let me know.
Cheers,
Dave
next prev parent reply other threads:[~2013-08-06 2:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 17:58 Failure to detect PCI card Peter LaDow
2013-08-05 18:25 ` Anatolij Gustschin
2013-08-05 20:12 ` Peter LaDow
2013-08-05 20:27 ` David Hawkins
2013-08-05 20:49 ` Peter LaDow
2013-08-05 21:08 ` David Hawkins
2013-08-05 21:10 ` David Hawkins
2013-08-05 22:11 ` Peter LaDow
2013-08-05 23:07 ` Peter LaDow
2013-08-05 23:14 ` Peter LaDow
2013-08-06 2:01 ` David Hawkins [this message]
2013-08-08 20:31 ` Peter LaDow
2013-08-08 22:10 ` David Hawkins
2013-08-12 2:32 ` Benjamin Herrenschmidt
2013-08-12 16:52 ` Peter LaDow
2013-08-06 20:03 ` Anatolij Gustschin
2013-08-05 18:32 ` Wolfgang Denk
2013-08-05 18:36 ` Peter LaDow
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=520058E0.8080304@ovro.caltech.edu \
--to=dwh@ovro$(echo .)caltech.edu \
--cc=agust@denx$(echo .)de \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=petela@gocougs$(echo .)wsu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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