From: "Daniela Engert" <dani@ngrt.de>
To: "Kathy Frazier" <kfrazier@mdc-dayton.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Linux and PCI bridge
Date: Thu, 28 Aug 2003 11:02:43 +0200 (CDT) [thread overview]
Message-ID: <20030828090209.E6FFC2823B@mail.medav.de> (raw)
In-Reply-To: <PMEMILJKPKGMMELCJCIGEEDNCEAA.kfrazier@mdc-dayton.com>
On Wed, 27 Aug 2003 09:51:21 -0500, Kathy Frazier wrote:
>- Can anyone recommend any tools that would be useful in debugging this?
>I've started looking at a couple of PCI bus analyzers, but I'm not sure that
>it will allow me to detect anything with respect to the bridge or the FSB.
In the past couple of years, probably the most valuable asset in
developping both the hardware and the software of our PCI boards has
been the VMetro PCI bus analyzer/excerciser. The analyzer allows us to
watch and trace all PCI signals/cycles in real time, while the
excerciser gives us the capability to probe/drive all mem/io/config
address ranges which are visible from the bus which the bus analyzer
board is sitting on. This excludes everything beyond the PCI bus domain
unless you are able to hook an additional signal to one of the general
purpose trace inputs.
In fact, I'd never ever develop a driver for whichever OS you like
without such a tool - it spoils you ;-) As it turned out, it's even
more valuable in software development than hardware development.
Ciao,
Dani
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Daniela Engert, systems engineer at MEDAV GmbH
Gräfenberger Str. 32-34, 91080 Uttenreuth, Germany
Phone ++49-9131-583-348, Fax ++49-9131-583-11
prev parent reply other threads:[~2003-08-28 9:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-27 14:51 Kathy Frazier
2003-08-28 9:02 ` Daniela Engert [this message]
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=20030828090209.E6FFC2823B@mail.medav.de \
--to=dani@ngrt.de \
--cc=kfrazier@mdc-dayton.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®