9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Henry Millican <henry@tehserv.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Inferno and the Parallella
Date: Tue,  4 Feb 2014 22:32:39 -0800	[thread overview]
Message-ID: <CAD+yg7Db4v3ynnw7UuN59c2pmR0fy5VEek9GgGNfZXm4VPT_1A@mail.gmail.com> (raw)
In-Reply-To: <CANZw+5e7g5Xnn0UHEshzuy=+90Nt94r-YJOPTHiYkxiZVfj2rQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1862 bytes --]

Parallella seems very cool. I'll probably pick one up when I have free
time.

I've worked with the Zynq chip on board, which is also great. For $99 it's
one hell of a dev board, considering you get an FPGA with hard ARM cores,
as well as the Ephiphany chip.

The Ephiphany processor fills in the gap between CPU and FPGA tasks in my
opinion. Things that would require complex state machines on an FPGA could
be done in parallel on the RISC cores very easily (and quickly). I can
imagine doing some image processing or something (that doesn't lend itself
well to FPGAs) of the like with this.

I'll be following you guys and may have time to contribute, but I am just a
hardware guy after all.
--

Henry


On Tue, Feb 4, 2014 at 10:20 PM, Shane Morris <edgecomberts@gmail.com>wrote:

> Oh, its ok. I like the GSoC idea. I just don't think I'm GSoC material,
> I'm hardware type, even if I will be a uni student this year going forward
> - "If it draws blood, its hardware" as the old maxim goes.
>
> The Parallella board is US$99, a far more modest investment in hardware
> than a GizmoBoard as I had previously suggested, and packs more power for
> the price, in terms of coding value. Whether it could be accepted as a
> coding project of the type for GSoC, a mentor for it found, and other
> logistical concerns are a issue for the GSoC organisers, but I suppose,
> could it happen?
>
> An abstract topic for the time being.
>
>
> On Wed, Feb 5, 2014 at 5:06 PM, <lucio@proxima.alt.za> wrote:
>
>> > Thoughts? Comments? Critique? Flames?
>>
>> I guess this is the real value of efforts like GSOC, if only they
>> could be extended to a much greater public either with an infinite
>> budget or by pushing a far more socially-aware ethos.
>>
>> I'll refrain from pontificating further.
>>
>> ++L
>>
>>
>>
>>
>

[-- Attachment #2: Type: text/html, Size: 2662 bytes --]

  reply	other threads:[~2014-02-05  6:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-04 21:43 Shane Morris
2014-02-05  5:26 ` lucio
2014-02-05  5:40   ` Shane Morris
2014-02-05  6:06 ` lucio
2014-02-05  6:20   ` Shane Morris
2014-02-05  6:32     ` Henry Millican [this message]
2014-02-05  6:40       ` Shane Morris
2014-02-05 10:57         ` Muhammad Junaid Muzammil
2014-02-05 12:46     ` erik quanstrom
2014-02-05 14:41       ` Shane Morris
2014-02-05 14:47         ` erik quanstrom
2014-02-05 15:40           ` Anthony Sorace
2014-02-05 15:59             ` Steven Stallion
2014-02-05 16:02               ` erik quanstrom
2014-02-05 18:03         ` Skip Tavakkolian
2014-02-05 19:32           ` Charles Forsyth
2014-02-05 20:13             ` Shane Morris

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=CAD+yg7Db4v3ynnw7UuN59c2pmR0fy5VEek9GgGNfZXm4VPT_1A@mail.gmail.com \
    --to=henry@tehserv.net \
    --cc=9fans@9fans.net \
    /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).