From: Geert Uytterhoeven <geert@linux-m68k.org>
To: linux-sh@vger.kernel.org
Subject: Re: Availability of SH hardware?
Date: Wed, 23 Mar 2016 07:50:40 +0000 [thread overview]
Message-ID: <CAMuHMdW8fUWkMR_iWDtUQUM8p3ARD4UAShou-Z84k-yQO2uGcA@mail.gmail.com> (raw)
In-Reply-To: <20160317032441.GA22517@brightrain.aerifal.cx>
Hi Rich.
On Thu, Mar 17, 2016 at 6:21 PM, Rich Felker <dalias@libc.org> wrote:
> Am I correct that the chips are still available, just not as part of
> eval/dev boards, so that in theory, if someone wanted to, they could
> make their own board? Or are they completely out of distribution? I
> ask mainly from a standpoint of gauging the theoretical possibility of
> new users for the original SH models.
Unlike SH dev boards, Digi-Key seems to have several SH SoCs in stock:
http://www.digikey.be/product-search/en/integrated-circuits-ics/embedded-microcontrollers/2556109?k=&pv506Q&pv506R&pv506S&pv506y&pv506”&pv506T&pv506U&pv506V&pv506p&pv506W&pv506\x137&pv506’&FVÿf40027%2Cfff800cd&mnonly=0&newproducts=0&ColumnSort=0&page=1&stock=1&quantity=0&ptm=0&fid=0&pageSizeP0
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2016-03-23 7:50 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 [this message]
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=CAMuHMdW8fUWkMR_iWDtUQUM8p3ARD4UAShou-Z84k-yQO2uGcA@mail.gmail.com \
--to=geert@linux-m68k.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).