From: Ralf Baechle <ralf@linux-mips.org>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] decstation: Document more MB ASIC register bits
Date: Fri, 13 Jun 2008 14:35:21 +0100 [thread overview]
Message-ID: <20080613133521.GD703@linux-mips.org> (raw)
In-Reply-To: <Pine.LNX.4.55.0806130015490.23634@cliff.in.clinika.pl>
On Fri, Jun 13, 2008 at 12:25:36AM +0100, Maciej W. Rozycki wrote:
> Document a few more register bits provided by the MB ASIC used on R4000SC
> (KN04) and R4400SC (KN05) CPU daughtercards with the DECstation.
>
> Reverse-engineered and not documented anywhere else to the best of my
> knowledge. Bit names appended to the last underscore the same as reported
> by the firmware in register dumps.
You realize that documentation the DECstation code endangers the safety of
your job as DECstation maintainer, do you ;-)
Queued for 2.6.27, thanks!
Ralf
next prev parent reply other threads:[~2008-06-13 13:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 23:25 [PATCH] decstation: Document more MB ASIC register bits Maciej W. Rozycki
2008-06-13 13:35 ` Ralf Baechle [this message]
2008-06-13 16:43 ` Maciej W. Rozycki
2008-06-13 16:52 ` Ralf Baechle
2008-06-14 15:50 ` Maciej W. Rozycki
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=20080613133521.GD703@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.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