Re: Discuss: Future of AX25, NETROM and ROSE in the kernel ?
Nate Bargmann <[email protected]> Sat, 18 Apr 2026 18:24:05 -0500
| Newsgroups | gmane.linux.hams |
|---|---|
| Organization | Amateur Radio! |
| Message-ID | <hsdnwdq2o2g26gbvm3wvychl5rp3eri7ggj7kkmple7yzm3kgz@u2pbkjyacqyw> |
--ctmyeapxocso36u3 Content-Type: text/plain; protected-headers=v1; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Subject: Re: Discuss: Future of AX25, NETROM and ROSE in the kernel ? MIME-Version: 1.0 * On 2026 18 Apr 14:29 -0500, Dan Cross wrote: > [Top-posting to make meta-commendary] >=20 > I wonder if other folks have thoughts, here? It doesn't bode well that > the discussion hasn't progressed. :-( Your reply was so comprehensive, there isn't much to add! A few years ago I had in mind to give using the kernel AX25 stack a go but reading various reports kind of turned me away. I had last done so in the late '90s or so as I recall. I did do some testing with Direwolf at the time instead. As a potential user it really makes no difference whether support is in the kernel proper or user space. From a maintainer's view, it's likely that putting the AX25 code entirely in user space (option 3) is the best practice these days. Let's face it. The kernel is no longer a niche hobby project but is very much an enterprise project. It makes sense to move the AX25 stack entirely into user space. Before doing so, what could the AX25 stack in user space do that Direwolf cannot? I know no one is suggesting this, but should an option four be considered where the AX25 code is dropped entirely from the kernel and potential users are directed to Direwolf or some such existing project? 73, Nate, N0NB --=20 "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Web: https://www.n0nb.us Projects: https://github.com/N0NB GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819 --ctmyeapxocso36u3 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABECAB0WIQSC1k9rDmfNQfaJu6b7LFEw1VqIGQUCaeQSlQAKCRD7LFEw1VqI GQlJAJ9yWS3RH+5qkXRlVzHLgaRxChbpDQCffVT78yFnuf8jhkJAIJTt6kLG5wk= =yh5C -----END PGP SIGNATURE----- --ctmyeapxocso36u3--