9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: smiley@icebubble.org
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Maybe a weird Plan 9 project.
Date: Sat, 30 Jul 2011 19:38:55 +0000	[thread overview]
Message-ID: <8639hnv9rk.fsf@cmarib.ramside> (raw)
In-Reply-To: <d9a77612420f8cbea5bbe9c9fe02547d@swcp.com> (ebo@sandien.com's message of "Fri, 29 Jul 2011 18:09:10 -0500")

EBo <ebo@sandien.com> writes:

> If you do get a 9p stack working on the Arduino let me know.  If/when
> you do I'll offer to contribute some stepper code that properly deals
> with motor accel/decel, speed limiting, etc.  I may even port a
> runtime polymorphic RS274* (g-code) interpreter I wrote a decade ago
> for it.  That would be fun to get a 9p sensor platform up and running.

I was thinking about writing 9P client/servers for Arduino.  Developing
for Arduino is SURPRISINGLY easy--at least on Linux--you just install
the gcc avr cross-compiler and avrdude, untar the Arduino library
source, tweak the Makefile, cut-and-paste some skeleton code, #include
standard stuff you want to use, run make, and use the open source
program avrdude to upload the image to the microcontroller over the FTDI
USB serial interface.  I've done a lot on Linux, and it really suprised
me how straightforward it was programming the Arduino.

I looked around to see if there was a canonical 9P implementation that I
could use as a starting point.  Alas, I found about a brazillian
different implementations, in about as many languages.  If there was
canonical 9P client/serever skeleton code (in C, pseudocode, or some
other language) with "fill-in-your handler" placeholders, it would be
really straightforward to implement 9P clients/servers on Arduino.

...with one caveat, related to underspecification of the 9P protocol,
which I will ask about in a separate thread: "9P specification: minimum
number of fids".



  reply	other threads:[~2011-07-30 19:38 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-29 13:44 David Leimbach
2011-07-29 13:48 ` EBo
2011-07-29 13:54   ` David Leimbach
2011-07-29 16:32     ` hiro
2011-07-29 17:22       ` David Leimbach
2011-07-29 20:08         ` EBo
2011-07-29 22:09           ` David Leimbach
2011-07-29 22:57             ` EBo
     [not found]           ` <CAJJ04x5D5yk0qdg6LyE0YGqjgaKHzFN6OScKCYyHmxf20Qy5DA@mail.gmail.c>
2011-07-31 13:26             ` erik quanstrom
2011-07-31 15:58               ` EBo
2011-07-31 16:58               ` smiley
2011-07-29 20:25 ` Bakul Shah
2011-07-29 20:34   ` Francisco J Ballesteros
2011-07-29 21:01     ` Bakul Shah
2011-07-29 23:23     ` EBo
2011-07-29 23:58       ` Nemo
2011-07-30  0:09         ` EBo
2011-07-30  9:34           ` Francisco J Ballesteros
2011-07-30 12:15             ` EBo
2011-07-30 17:08     ` Jack
2011-07-30 20:15       ` Bakul Shah
2011-07-29 23:09   ` EBo
2011-07-30 19:38     ` smiley [this message]
2011-07-30 22:12       ` ron minnich
2011-07-30 22:40         ` EBo
2011-08-02  4:50         ` Joseph Stewart
2011-08-02  4:54           ` ron minnich
2011-08-02  6:28           ` EBo
2011-07-30 22:54       ` EBo

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=8639hnv9rk.fsf@cmarib.ramside \
    --to=smiley@icebubble.org \
    --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).