From: Michael Tremer <michael.tremer@ipfire.org>
To: sig-arm@lists.ipfire.org
Subject: [SIG-ARM] ARM hardware now and the not so distant future
Date: Tue, 27 Mar 2012 17:24:27 +0200 [thread overview]
Message-ID: <1332861867.16190.28.camel@rice-oxley.tremer.info> (raw)
[-- Attachment #1: Type: text/plain, Size: 408 bytes --]
Hello,
I found an interesting blog entry which may be interesting to some of
you:
http://nullr0ute.com/2012/03/arm-hardware-now-and-the-not-so-distant-future/
It shows a very detailed list about what devices can be bought at the
moment and which one will be coming up in the near future. Most of them
are very expensive (> EUR 300) but as we can see, there is some movement
in the market. Yeah.
Michael
reply other threads:[~2012-03-27 15:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1332861867.16190.28.camel@rice-oxley.tremer.info \
--to=michael.tremer@ipfire.org \
--cc=sig-arm@lists.ipfire.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