From: David Boddie <david@boddie.org.uk>
To: 9fans@9fans.net
Subject: [9fans] Re: Solo factotum (was: Enterable namespaces: /proc/pid/$ns/srv)
Date: Tue, 30 Dec 2025 00:46:11 +0000 [thread overview]
Message-ID: <d52fe5f0399a38c73267c4f4a3d77f4f@boddie.org.uk> (raw)
On Mon, 29 Dec 2025, David Arroyo wrote:
>
> I'm trying to figure out how to serve 9P over USB, which I know very
> little about. My initial plan is to make the device a USB serial
> device that expects 9P, then try to mount the /dev/eiaUN device.
I would make it a USB serial device to start with and test that you
can send and receive data reliably, then implement something that
sends and receives 9P messages over that connection.
> However, nusb(4) states that the nusb/serial driver only works for two
> chips, so I'd have to add support for this one. That's not a problem,
> but am I going in the right direction?
Are those implementations of host drivers that talk to USB devices with
vendor-specific device classes or are they drivers for generic USB
serial
communications classes?
> There are a number of USB
> device classes, maybe a different one is more suitable to carrying 9P?
> If this works out it would be great if I could also mount it under
> Linux, with v9fs or 9pfuse, but that's not a priority.
I implemented a serial-like device for Inferno on a microcontroller that
hosts could talk to. I tested it with Inferno on Linux, so not running
on
native Inferno, but I could imagine that 9pi would be able to talk to
it.
See if you can get Plan 9 to talk to an existing USB serial device then
reimplement something similar with the new device.
David
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Te5078cfc0acc3fdf-M74f4551d01a534cd2b655275
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next reply other threads:[~2025-12-30 2:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-30 0:46 David Boddie [this message]
2025-12-30 9:18 ` [9fans] Re: Solo factotum (was: Enterable namespaces: /proc/pid/$ns/srv) David Arroyo
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=d52fe5f0399a38c73267c4f4a3d77f4f@boddie.org.uk \
--to=david@boddie.org.uk \
--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).