From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: linux-sh@vger.kernel.org
Subject: Re: Availability of SH hardware?
Date: Thu, 17 Mar 2016 09:10:26 +0000 [thread overview]
Message-ID: <56EA7482.9050304@physik.fu-berlin.de> (raw)
In-Reply-To: <20160317032441.GA22517@brightrain.aerifal.cx>
Hi Rich!
On 03/17/2016 04:24 AM, Rich Felker wrote:
> I'm working on the J-Core (currently J2) open hardware revival of the
> SH architecture and don't have any original SH hardware (except
> perhaps embedded in old appliances). Does anyone have pointers (direct
> add-to-cart'able links) to where SH dev boards are still available, or
> even better, any old hardware lying around that's not being used that
> you'd be willing to donate?
I have acquired SuperH hardware in the past and I have good contacts
to people in Japan. I will help you getting a board, but it may take
a while.
Since Renesas dropped support for SuperH completely, they don't have
any evaluation boards left. In fact, I own the last board that they
had in stock.
So, with Renesas out of the picture, sources for SuperH hardware would
be either open source people in Japan who used to work for Renesas -
I know, for fact, that Renesas hired lots of people in Japan to work
on SuperH support in Linux - or third-party companies like emtrion [1]
or Alpha Project in Japan [2]. Another option would be getting an
old LANDisk device which can also be used to run Debian's sh4 port [3].
I have already forwarded your mail to a friend in the Japanese Debian
community and asked him to post a mail in Japanese on their mailing
lists asking for people who are willing to donate hardware.
We will find something for you :).
Adrian
> [1] https://www.emtrion.de/en/legacy_products.html
> [2] http://www.apnet.co.jp/product/superh/
> [3] http://www.iodata.jp/product/nas/personal/hdl-u/
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2016-03-17 9:10 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 3:24 Availability of SH hardware? Rich Felker
2016-03-17 9:10 ` John Paul Adrian Glaubitz [this message]
2016-03-17 17:21 ` Rich Felker
2016-03-23 7:50 ` Geert Uytterhoeven
2016-03-23 9:52 ` John Paul Adrian Glaubitz
2016-03-23 10:01 ` John Paul Adrian Glaubitz
2016-03-23 10:05 ` Magnus Damm
2016-03-23 10:11 ` John Paul Adrian Glaubitz
2016-03-23 16:09 ` Rich Felker
2016-03-23 16:17 ` Geert Uytterhoeven
2016-03-24 8:50 ` Magnus Damm
2016-03-24 9:01 ` John Paul Adrian Glaubitz
2016-03-24 11:40 ` Yoshinori Sato
2016-03-24 21:18 ` Magnus Damm
2016-03-24 22:00 ` Rich Felker
2016-03-24 23:52 ` Magnus Damm
2016-03-25 1:54 ` Rob Landley
2016-03-25 2:04 ` Rob Landley
2016-03-25 11:12 ` John Paul Adrian Glaubitz
2016-03-25 11:19 ` John Paul Adrian Glaubitz
2016-03-25 20:31 ` John Paul Adrian Glaubitz
2016-03-25 22:42 ` Rich Felker
2016-03-25 22:51 ` John Paul Adrian Glaubitz
2016-03-25 23:02 ` John Paul Adrian Glaubitz
2016-03-26 9:29 ` John Paul Adrian Glaubitz
2016-03-26 9:51 ` Yoshinori Sato
2016-03-26 21:18 ` Zoltan HERPAI
2016-03-26 21:37 ` John Paul Adrian Glaubitz
2016-03-28 14:17 ` John Paul Adrian Glaubitz
2016-03-29 4:17 ` Rob Landley
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=56EA7482.9050304@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=linux-sh@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.