From: Bruce Ellis <bruce.ellis@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Fwd: New Chip (SEAforth 40C18) - New Challenge
Date: Tue, 7 Apr 2009 08:46:10 +1000 [thread overview]
Message-ID: <775b8d190904061546u792406a6p442108f4b271dbca@mail.gmail.com> (raw)
In-Reply-To: <49DA4321.9060608@proweb.co.uk>
What a shame - tho there is a certain charm in owning a custom
computer that can't be replicated. Hopefully there will be a firesale
of stuff. There can't be many in the wild, mine is serial number 30 -
what's your Jeff?
brucee
On Tue, Apr 7, 2009 at 4:00 AM, maht <mattmobile@proweb.co.uk> wrote:
>
> SeaForth is dead already
>
> http://colorforth.com/vTPL.htm
>
> http://colorforth.com/S40.htm
>
>
> Bruce Ellis wrote:
>>
>> Please share your experience.
>>
>> http://groups.google.com/group/casella
>>
>> brucee
>>
>> On Thu, Mar 19, 2009 at 8:45 PM, Pavel Klinkovsky
>> <pavel.klinkovsky@gmail.com> wrote:
>>
>>>
>>> I am playing with the FORTHdrive (SEAforth-24 chip) for half a year.
>>> We are testing it for a signal processing.
>>>
>>> I can confirm it is a wonderful chip.
>>> But it needs a little bit different view to the programming. ;-)
>>>
>>> Pavel
>>>
>>>
>>>
>>
>>
>>
>
>
>
next prev parent reply other threads:[~2009-04-06 22:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a5903cce-4631-4d53-ab29-54a5b8b66361@x29g2000prf.googlegroups.com>
2009-03-19 3:37 ` Bruce Ellis
2009-03-19 4:36 ` David Leimbach
2009-03-19 4:47 ` Bruce Ellis
2009-03-19 6:21 ` Jeff Sickel
2009-03-19 6:30 ` Bruce Ellis
2009-03-19 9:45 ` Pavel Klinkovsky
2009-03-20 2:50 ` Bruce Ellis
2009-04-06 18:00 ` maht
2009-04-06 18:54 ` Jeff Sickel
2009-04-06 22:46 ` Bruce Ellis [this message]
2009-04-07 9:07 ` Robert Raschke
2009-04-07 10:48 ` Alexander Clouter
2009-04-07 14:24 ` maht
2009-04-07 14:52 ` Robert Raschke
2009-04-07 15:04 ` maht
2009-03-30 9:15 ` [9fans] Fwd: New Chip (SEAforth 40C18) - New Icarus Sparry
2009-03-30 12:07 ` Bruce Ellis
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=775b8d190904061546u792406a6p442108f4b271dbca@mail.gmail.com \
--to=bruce.ellis@gmail.com \
--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).