linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
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 14:10:29 -0700	[thread overview]
Message-ID: <520014C5.4060703@ovro.caltech.edu> (raw)
In-Reply-To: <5200143F.9010307@ovro.caltech.edu>

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 PCI slot into two PCI slots. You
could then plug your analyzer into the second slot.

For $30 it might be worth a shot ...

Cheers,
Dave

  reply	other threads:[~2013-08-05 21:10 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 [this message]
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
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=520014C5.4060703@ovro.caltech.edu \
    --to=dwh@ovro.caltech.edu \
    --cc=agust@denx.de \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=petela@gocougs.wsu.edu \
    /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;
as well as URLs for NNTP newsgroup(s).