From: Steven Whitehouse <steve@gw.chygwyn.com>
To: Ralf Baechle <ralf@uni-koblenz.de>
Cc: linux-hams@vger.kernel.org
Subject: Re: Status of AX.25 in 2.5 / 2.6
Date: Fri, 26 Jul 2002 13:50:45 +0100 (BST) [thread overview]
Message-ID: <200207261250.NAA32030@gw.chygwyn.com> (raw)
In-Reply-To: <20020726134216.A4126@dea.linux-mips.net> from "Ralf Baechle" at Jul 26, 2002 01:42:16 PM
Hi,
>
> Forgive if I'm missing any developments on this list; I've been (again ...)
> unsubscribed by one of Mati's scripts ...
>
> No substancial changes have been done to the AX.25 kernel stack in a extended
> period of time. As the result it is still doing crude stuff like globally
> enabling and disabling interrupts, has no understanding of shared skb, isn't
> fully multithreaded and probably plenty more problems I haven't spotted yet.
> Now that we're about to remove global cli() / sti() from the kernel this
> means the AX.25 stack will soon break entirely.
>
> Is there any ongoing development I'm not aware of? Just in case I've
> started doing some cleanup last night ...
>
> 73 de DO1GRB op Ralf
>
I started a little. Untested yet, but for what its worth:
http://www.chygwyn.com/~steve/kpatch/ax25/ax25-uid-2.5.25.diff
Please feel free to use as much/little as you like of this patch. It would
be nice to do enough tidying to these protocols that we can get rid of
things like deliver_to_old_ones() from the core code. I can't spare a
lot of time, but I'll help where I can.
I spoke to Dave Jones at the recent UKUUG conference and he mentioned that
it appeared that nobody was doing any work on AX.25 and associated
protocols which was why I started something. It would be a good idea to
drop him a line to let him know that you are working on it,
Steve.
G7RRM
next prev parent reply other threads:[~2002-07-26 12:50 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-26 11:42 Status of AX.25 in 2.5 / 2.6 Ralf Baechle
2002-07-26 12:16 ` Tomi Manninen OH2BNS
2002-07-26 12:50 ` Ralf Baechle DO1GRB
2002-09-27 16:36 ` mkiss problem in kernel 2.5 Arnau Sánchez
2002-07-26 12:50 ` Steven Whitehouse [this message]
2002-07-26 18:15 ` Status of AX.25 in 2.5 / 2.6 Ralf Baechle DO1GRB
2002-07-26 23:24 ` Craig Small
2002-07-27 1:07 ` Ralf Baechle DO1GRB
2002-07-27 11:10 ` Robert Jenkins
2002-07-27 13:38 ` Ken Koster
2002-07-28 13:15 ` Ralf Baechle DO1GRB
2002-07-28 17:19 ` Riley Williams
2002-07-30 8:24 ` Jason Flynn G7OCD
2002-07-28 19:10 ` Tomi Manninen
2002-07-28 22:43 ` Craig Small
2002-07-29 12:16 ` Tomi Manninen OH2BNS
2002-07-29 18:50 ` Iain Young - G7III
2002-07-30 9:44 ` Tomi Manninen OH2BNS
2002-07-31 17:53 ` Iain Young - G7III
2002-08-01 22:10 ` Ken Koster
2002-07-30 10:50 ` Craig Small
2002-07-29 20:43 ` Chuck Gelm
2002-07-29 14:49 ` Robert Jenkins
2002-07-29 15:27 ` Tomi Manninen OH2BNS
2002-07-29 17:45 ` Robert Jenkins
2002-07-29 18:07 ` Tomi Manninen
2002-07-30 8:14 ` Jason Flynn G7OCD
2002-07-30 9:38 ` Tomi Manninen OH2BNS
2002-07-29 20:52 ` Chuck Gelm
-- strict thread matches above, loose matches on Subject: below --
2002-07-29 23:44 Stewart Wilkinson
2002-07-30 9:14 ` Tomi Manninen OH2BNS
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=200207261250.NAA32030@gw.chygwyn.com \
--to=steve@gw.chygwyn.com \
--cc=Steve@ChyGwyn.com \
--cc=linux-hams@vger.kernel.org \
--cc=ralf@uni-koblenz.de \
/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