From: Rich Felker <dalias@libc.org>
To: linux-sh@vger.kernel.org
Subject: Re: Availability of SH hardware?
Date: Fri, 25 Mar 2016 22:42:07 +0000 [thread overview]
Message-ID: <20160325224207.GW21636@brightrain.aerifal.cx> (raw)
In-Reply-To: <20160317032441.GA22517@brightrain.aerifal.cx>
On Fri, Mar 25, 2016 at 09:31:05PM +0100, John Paul Adrian Glaubitz wrote:
> On 03/17/2016 10:10 AM, John Paul Adrian Glaubitz wrote:
> > 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].
>
> So, while reading the SH4 page in the Debian wiki [1], I stumbled
> accross another very interesting SH4 machine, the NextVOD from
> Taiwan [2] (Chinese name: 網樂通).
>
> The specs [3] look very promising:
>
> * SH7105 CPU running at 600 MHz (other sources claim 450 MHz)
> * 256 MiB RAM
> * 8 GiB Flash storage (through an internal USB stick)
> * Ethernet
> * USB 2.0
> * HDMI
> * AV out
>
> Apparently Paul Liu (another Debian guy from Taiwan I know personally)
> has or had such a device as well. At least he's got a filesystem image
> in his Debian webspace [4].
>
> I will get in touch with him. Maybe he can help us acquire multiple
> boxes from Taiwan for little money.
This sounds really interesting. Do you know what cpu model it actually
has? I tried to lookup SH7105 and it seems to be a model of SH2, which
would not run Debian and almost certainly would not go up to 600 MHz.
Rich
next prev parent reply other threads:[~2016-03-25 22:42 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
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 [this message]
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=20160325224207.GW21636@brightrain.aerifal.cx \
--to=dalias@libc.org \
--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 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).