From: Stephen Frost <sfrost@snowman.net>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: linux-mips@fnet.fr, linux-mips@oss.sgi.com
Subject: Re: linux 2.4.8: The DECstation 5000/2x0 NVRAM module driver
Date: Thu, 6 Sep 2001 08:34:45 -0400 [thread overview]
Message-ID: <20010906083444.W11136@ns> (raw)
In-Reply-To: <Pine.GSO.3.96.1010906141756.28792A-100000@delta.ds2.pg.gda.pl>; from macro@ds2.pg.gda.pl on Thu, Sep 06, 2001 at 02:31:45PM +0200
[-- Attachment #1: Type: text/plain, Size: 988 bytes --]
* Maciej W. Rozycki (macro@ds2.pg.gda.pl) wrote:
> Hi,
>
> I've prepared a syntactic update to the DECstation 5000/2x0 NVRAM module
> driver for linux 2.4.8. There are no functional changes at the moment.
> The driver patch and supplementary changes are available at:
> 'ftp://ftp.ds2.pg.gda.pl/pub/macro/drivers/ms02-nv/'.
>
> I'm looking for a tester with a DECstation 5000/200 and a MS02 NVRAM
> module. I'm going to improve the module detection code in the next
> version to make it less firmware-dependent. This is needed to support
> multiple modules as well as single modules in non-standard slots. I need
> to make sure I can rely on bus error exceptions just like in the /240.
Welp, I've got a DECstation 5000/200 but no clue what (if any)
NVRAM module it has. How can I find out? :) I havn't booted
the thing up in quite a while so I'm not even sure it's exactly
functional, but I've been looking for an excuse to play with it.
Stephen
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-09-06 12:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-06 12:31 linux 2.4.8: The DECstation 5000/2x0 NVRAM module driver Maciej W. Rozycki
2001-09-06 12:34 ` Stephen Frost [this message]
2001-09-06 13:17 ` Maciej W. Rozycki
2001-09-07 9:44 ` Florian Lohoff
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=20010906083444.W11136@ns \
--to=sfrost@snowman.net \
--cc=linux-mips@fnet.fr \
--cc=linux-mips@oss.sgi.com \
--cc=macro@ds2.pg.gda.pl \
/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