From: "Lyndon Nerenberg (VE7TFX/VE6BBM)" <lyndon@orthanc.ca>
To: 9fans <9fans@9fans.net>, Bakul Shah <bakul@iitbombay.org>
Subject: Re: [9fans] building blocks speaking 9p
Date: Fri, 28 Jan 2022 12:55:26 -0800 [thread overview]
Message-ID: <4409eb4324d31783@orthanc.ca> (raw)
In-Reply-To: <E4F13D45-9C44-487A-904D-31881DA01DF0@iitbombay.org>
Bakul Shah writes:
> - make it very easy to create hardware gadgets by
> providing a firmware/hardware building block that
> talks 9p on the host interface side & interfaces
> with device specific hardware.
Amen! I've been thinking about something like this for years.
My specific use case involves controlling radio transceivers.
Right now I do this with assorted Arduino hardware that speaks
GPIO and RS232 (mostly) to the radios, and RS232 to the upstream
"controller" host. This burns through a lot of serial ports on
the controller.
What I would prefer is to have all those Arduinos connected
to an RS485 multidrop, each exporting a 9p filesystem for the
control interface. Shoveling the data around on the RS485
"bus" just needs a simple frame wrapped around the 9p packets
that provides device addressing and a CRC. On the Plan9 side
this just becomes another network type, with ndb handling
the device addressing.
As others have mentioned, having a native Atmel C compiler would
be a real boon here, but there's no reason why this couldn't be
done with an Arduino 9P library. I haven't investigated if such
a thing exists, although I'm sure it does.
--lyndon
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Ta4e584a373b05553-M7e3fd4de0f3c256df6dbd436
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2022-01-28 20:55 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 22:57 Bakul Shah
2022-01-28 2:55 ` Thaddeus Woskowiak
2022-01-28 3:31 ` Lucio De Re
2022-01-28 5:16 ` Bakul Shah
2022-01-28 10:16 ` Lucio De Re
2022-01-28 19:01 ` Charles Forsyth
2022-01-28 21:26 ` Bakul Shah
2022-01-28 21:37 ` Eli Cohen
2022-01-28 20:54 ` Tony Mendoza
2022-01-28 20:59 ` Tony Mendoza
2022-01-28 21:03 ` ori
2022-01-28 21:07 ` Tony Mendoza
2022-01-28 21:06 ` Eli Cohen
2022-01-28 21:16 ` Tony Mendoza
2022-01-28 21:27 ` Eli Cohen
2022-01-28 21:33 ` david
2022-01-28 21:46 ` Tony Mendoza
2022-01-28 22:23 ` David Boddie
2022-01-29 1:04 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2022-01-29 2:08 ` David Boddie
2022-01-29 3:36 ` Tony Mendoza
2022-01-29 18:03 ` David Boddie
2022-01-29 2:32 ` Thaddeus Woskowiak
2022-01-29 20:04 ` [9fans] aiju boards Lyndon Nerenberg (VE7TFX/VE6BBM)
2022-01-28 19:32 ` [9fans] building blocks speaking 9p Kent R. Spillner
2022-01-28 4:54 ` ori
2022-01-28 20:55 ` Lyndon Nerenberg (VE7TFX/VE6BBM) [this message]
2022-01-29 9:16 ` Skip Tavakkolian
2022-01-29 11:56 ` Frank D. Engel, Jr.
2022-01-29 12:14 ` Frank D. Engel, Jr.
2022-01-29 12:30 ` Frank D. Engel, Jr.
2022-01-29 13:24 ` cinap_lenrek
2022-02-15 3:07 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2022-01-29 20:53 Lyndon Nerenberg (VE7TFX/VE6BBM)
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=4409eb4324d31783@orthanc.ca \
--to=lyndon@orthanc.ca \
--cc=9fans@9fans.net \
--cc=bakul@iitbombay.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).