From: Bakul Shah <bakul@iitbombay.org> To: 9fans <9fans@9fans.net> Subject: [9fans] building blocks speaking 9p Date: Thu, 27 Jan 2022 14:57:03 -0800 [thread overview] Message-ID: <E4F13D45-9C44-487A-904D-31881DA01DF0@iitbombay.org> (raw) The idea: - 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. - use a "universal" 9p driver on the host side that allows access to any such 9p device even from a shell. - provide a standard way to find out device capabilities. - together they provide a plug-and-play setup. Example: connect an LED and a current sensor to this 9p device, other necessary hardware, add a few config bits and plug this device kn]]into a host. Now you should be able to turn on/off the light or sense its state. Similarly you should be able to control a stepper motor servo, cameras, microphones, other actuators, sensors, IO etc. Eventually you should be able to snap together enough of these components to build larger assemblies such as a 3D printer. Another example: a "hub" to multiplex such downstream devices and make them available to a host. This will probably have to ride on USB first. A verilog implementation would be useful in an FPGA! Would this be a useful component? If such a thing were available, what would you want to build with it? Do you think 9p is the right protocol for this? Ideally - connect anything to anything - authenticated connections - drive the device through a shell script - no new low level drivers - self-identifying devices with help and command syntax - signicantly eases the task of creating new h/w devices. ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Ta4e584a373b05553-M35165d4278d95e41fd95b8f7 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next reply other threads:[~2022-01-27 22:57 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-27 22:57 Bakul Shah [this message] 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) 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=E4F13D45-9C44-487A-904D-31881DA01DF0@iitbombay.org \ --to=bakul@iitbombay.org \ --cc=9fans@9fans.net \ --subject='Re: [9fans] building blocks speaking 9p' \ /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
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).