From: "Steven R. Loomis" <srl295@gmail.com>
To: Nate Bargmann <n0nb@n0nb.us>
Cc: linux-hams@vger.kernel.org
Subject: Re: Discuss: Future of AX25, NETROM and ROSE in the kernel ?
Date: Sat, 18 Apr 2026 20:31:01 -0500 [thread overview]
Message-ID: <BBE715A7-E261-4A6D-A9CD-6B0D3CF72F1F@gmail.com> (raw)
In-Reply-To: <hsdnwdq2o2g26gbvm3wvychl5rp3eri7ggj7kkmple7yzm3kgz@u2pbkjyacqyw>
I have a dormant project [1] to add Node.js bindings for AX25 to be able to write Node.js apps directly on AX25.
My AX25 use is also dormant, but I would love to bring it back up someday.
User space makes a lot of sense for the reasons given.
Since maintenance is a question though, perhaps it’s a question of who would volunteer for making any change (beyond no change)?
> what could the AX25 stack in user space do that Direwolf cannot?
The AX25 stack would still attach to Direwolf so that connected AX25 apps could run.
[1]: https://github.com/srl295/node-ax25-seqpacket/blob/add-actual-stuff/lib/ax25-seqpacket.js
--
Steven R. Loomis
K6SPI
next prev parent reply other threads:[~2026-04-19 1:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-11 7:35 Discuss: Future of AX25, NETROM and ROSE in the kernel ? Hugh Blemings
2026-04-13 23:31 ` Dan Cross
2026-04-18 19:28 ` Dan Cross
2026-04-18 23:24 ` Nate Bargmann
2026-04-19 1:31 ` Steven R. Loomis [this message]
2026-04-19 2:02 ` jj
2026-04-19 4:01 ` Stuart Longland VK4MSL
2026-04-19 9:36 ` Hugh Blemings
2026-04-19 16:18 ` Steve Conklin
2026-04-21 6:28 ` Hugh Blemings
2026-04-21 12:06 ` Dan Cross
2026-04-21 14:43 ` Steven R. Loomis
2026-04-21 15:00 ` Andrew Lunn
2026-04-19 20:37 ` David Ranch
2026-04-21 19:29 ` Dan Cross
2026-04-26 3:17 ` Joshua McAdam
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=BBE715A7-E261-4A6D-A9CD-6B0D3CF72F1F@gmail.com \
--to=srl295@gmail.com \
--cc=linux-hams@vger.kernel.org \
--cc=n0nb@n0nb.us \
/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