From: "David S. Miller" <davem@davemloft.net>
To: sparclinux@vger.kernel.org
Subject: Re: Would a JTAG port help with sun4d SMP work?
Date: Thu, 28 Oct 2004 00:55:24 +0000 [thread overview]
Message-ID: <20041027175524.1ec2f579.davem@davemloft.net> (raw)
In-Reply-To: <b476569a041027060861767e78@mail.gmail.com>
On Wed, 27 Oct 2004 10:56:12 -0700
William Lee Irwin III <wli@holomorphy.com> wrote:
> The use of the JTAG would allow rather immediate and enormous advances
> if we had any notion of how to use it. I suspect this is not an entirely
> uncommon state of affairs, as I've heard that e.g. Exy00's all have open
> JTAG ports, none of which we have any notion of how to use AFAIK.
THe Ex000 JTAG's are driven by the registers mapped by
the arch/sparc64/kernel/central.c driver code.
The specific registers are defined in asm-sparc64/fhc.h
But that's where the information stops, sorry :-)
One thing I do remember is that only one board can be
declared as the JTAG master and do chain scans.
Each board type (CPU+MEM, SBUS, PCI, etc.) has different
layout and meanings of the scan chains.
You actually have to use this stuff to hotplug boards. OBP
is supposed to take care of it via special OBP prom calls but
some of those are buggy so you have to jumpstart the board
by hand using JTAG commands.
I would not be surprised if the sun4d JTAG programming is similar.
The UltraSPARC main bus, interrupt, streaming cache, and IOMMU
architecture is largely derived from the sun4d stuff.
prev parent reply other threads:[~2004-10-28 0:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-27 13:08 Would a JTAG port help with sun4d SMP work? Adam Hunt
2004-10-27 16:20 ` C.Newport
2004-10-27 17:56 ` William Lee Irwin III
2004-10-28 0:55 ` David S. Miller [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=20041027175524.1ec2f579.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=sparclinux@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 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.