On Sun, Aug 11, 2013 at 7:32 PM, Benjamin Herrenschmidt
wrote:
> Do that help with e1000 as well ? IE. A bad clock might have caused
> malfunctions of the DMA for example...
No, it didn't help with the e1000. In fact, we have separate clocks
for the on-board components. This particular case was
On Thu, 2013-08-08 at 13:31 -0700, Peter LaDow wrote:
> For those that are interested, we did figure out what was going on.
> Turns out that the clock buffer driving the PCI connector was, well,
> less than adequate. With some cards, the load on the clock line was
> large enough that the clock was
Hi Pete,
For those that are interested, we did figure out what was going on.
Turns out that the clock buffer driving the PCI connector was, well,
less than adequate. With some cards, the load on the clock line was
large enough that the clock was in horrible shape. Fixing the clock
line and the
On Mon, Aug 5, 2013 at 7:01 PM, David Hawkins wrote:
> 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?
For those that are interested, we did figure out what was going on.
Turns out
On Mon, 5 Aug 2013 16:14:29 -0700
Peter LaDow wrote:
...
> 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 techni
Hi Pete,
On Mon, Aug 5, 2013 at 4:07 PM, Peter LaDow 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 ou
On Mon, Aug 5, 2013 at 4:07 PM, Peter LaDow 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
On Mon, Aug 5, 2013 at 1:27 PM, David Hawkins wrote:
> 2. Have you probed the PCI bus using a bus analyzer or scope?
Ok. I managed to find someone with a bus extender, and have connected
both our analyzer and card.
With a working card (the 82540EM based card), I see configuration
reads on 0x000
On Mon, Aug 5, 2013 at 2:08 PM, David Hawkins wrote:
> My analyzer has an extender card that you first plug in, and then
> plug the board into that ... any chance someone in your organization
> has one of those cards? Alternatively, confirm the board works in
> a machine that has more than one slo
Hi Pete,
Actually, before going down that route, I would get a PCI extender
that you can use to trace the traffic with your board. Does the
network card use 33MHz or 66MHz?
I wonder if something like this board:
http://www.logicsupply.com/products/pci122_dflex
can be used to make a single P
Hi Pete,
1. Have you checked the power supplies on the PCI board?
PCI boards can be powered from 3.3V or 5V, or both. I've had
old PCs that only supply one or the other rail, and various
evaluation boards that only supply 3.3V.
If you can put together a "working" x86 setup that
On Mon, Aug 5, 2013 at 1:27 PM, David Hawkins wrote:
> 1. Have you checked the power supplies on the PCI board?
>
>PCI boards can be powered from 3.3V or 5V, or both. I've had
>old PCs that only supply one or the other rail, and various
>evaluation boards that only supply 3.3V.
>
>
Hi Pete,
On Mon, Aug 5, 2013 at 11:25 AM, Anatolij Gustschin wrote:
Maybe this card needs bigger delay to respond after PCI reset. You can
try to re-build U-Boot with defined CONFIG_PCI_BOOTDELAY. Use 1000
for CONFIG_PCI_BOOTDELAY in the first step and if detection works,
try to decrease this
On Mon, Aug 5, 2013 at 11:25 AM, Anatolij Gustschin wrote:
> Maybe this card needs bigger delay to respond after PCI reset. You can
> try to re-build U-Boot with defined CONFIG_PCI_BOOTDELAY. Use 1000
> for CONFIG_PCI_BOOTDELAY in the first step and if detection works,
> try to decrease this value
On Mon, Aug 5, 2013 at 11:25 AM, Anatolij Gustschin wrote:
> Maybe this card needs bigger delay to respond after PCI reset. You can
> try to re-build U-Boot with defined CONFIG_PCI_BOOTDELAY. Use 1000
> for CONFIG_PCI_BOOTDELAY in the first step and if detection works,
> try to decrease this value
Dear Peter LaDow,
In message
you wrote:
> I have a PCI card (a Netgear FA331, vendor:device 100b:0020) that is
> failing to be detected by our PPC platform. This device works just
> fine in a PC, and other cards work just fine in the same PCI slot (we
> have an Intel 82540EM based card that wor
On Mon, 5 Aug 2013 10:58:01 -0700
Peter LaDow wrote:
> I have a PCI card (a Netgear FA331, vendor:device 100b:0020) that is
> failing to be detected by our PPC platform. This device works just
> fine in a PC, and other cards work just fine in the same PCI slot (we
> have an Intel 82540EM based c
I have a PCI card (a Netgear FA331, vendor:device 100b:0020) that is
failing to be detected by our PPC platform. This device works just
fine in a PC, and other cards work just fine in the same PCI slot (we
have an Intel 82540EM based card that works).
But for some reason, neither u-boot nor the k
18 matches
Mail list logo
