From: Yoshinori Sato <ysato@users.sourceforge.jp>
To: linux-sh@vger.kernel.org
Subject: Re: Availability of SH hardware?
Date: Thu, 24 Mar 2016 11:40:15 +0000 [thread overview]
Message-ID: <87wpos9k9s.wl-ysato@users.sourceforge.jp> (raw)
In-Reply-To: <20160317032441.GA22517@brightrain.aerifal.cx>
On Thu, 17 Mar 2016 12:24:41 +0900,
Rich Felker wrote:
>
> One of my goals in taking on maintainership of arch/sh is to gradually
> replace all of the hard-coded legacy board/subtype support with device
> tree based board descriptions, and clean up the related board support
> infrastructure in arch/sh to be more in line with how things are done
> on other archs these days. However the ability to make and test these
> changes depends on having some actual hardware to work with.
>
> 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'm especially interested in getting an SH-X3 board since it seems to
> be the only model with existing SMP support, and moving it over to
> device tree would eliminate the need for keeping around the
> non-device-tree SMP register_smp_ops and cross-core cache invalidation
> infrastructure, which are low-hanging fruit for refactoring/cleanup.
> But really anything would be great to have.
>
> Rich
> --
> To unsubscribe from this list: send the line "unsubscribe linux-sh" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
I got HDL-U (aka LANDISK). And setup latest u-boot / kernel.
So we can testing real SH4 hardware.
--
Yoshinori Sato
<ysato@users.sourceforge.jp>
next prev parent reply other threads:[~2016-03-24 11:40 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 [this message]
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=87wpos9k9s.wl-ysato@users.sourceforge.jp \
--to=ysato@users.sourceforge.jp \
--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).