From: Anthony Sorace <anothy@eden.rutgers.edu>
To: 9fans@cse.psu.edu, pip@stricca.org
Subject: Re: [9fans] Mitsubishi's M32R
Date: Mon, 14 Aug 2000 13:56:30 -0400 [thread overview]
Message-ID: <200008141756.NAA12567@er7.rutgers.edu> (raw)
thanks for the info, disapointing though it may be.
//any particular reason for liking the M32R/D ?
no reason, really. i'm just cleaning up a room in my
house, and i've got one of these, perhaps the "very
sweet dev board" you mentioned. it's got two PCICIA
slots and a serial connector, as well as 87-pin and
58-pin connectors that i can't immediatly identify.
i've got no documentation for the board (don't even
know what voltage it wants for power), and i'm not
ever real eager to dump hardware (i've also got two
730+'s and a 630 in the same room, as well as a
non-working Alpha AXP board, an ARM7500 development
board, and lots of SUN stuff of varying vintage).
: anothy;
next reply other threads:[~2000-08-14 17:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-14 17:56 Anthony Sorace [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-08-14 21:44 pip
2000-08-13 16:38 Anthony Sorace
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=200008141756.NAA12567@er7.rutgers.edu \
--to=anothy@eden.rutgers.edu \
--cc=9fans@cse.psu.edu \
--cc=pip@stricca.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;
as well as URLs for NNTP newsgroup(s).