From: Ralf Baechle DL5RB <ralf@linux-mips.org>
To: John Ronan <jronan@tssg.org>
Cc: aa6qn@aa6qn.sytes.net, Linux-Hams <linux-hams@vger.kernel.org>
Subject: Re: 2.6.14-r4 crashing
Date: Thu, 27 Oct 2005 10:51:23 +0100 [thread overview]
Message-ID: <20051027095123.GA17645@linux-mips.org> (raw)
In-Reply-To: <DED598BC-2481-467C-8410-7AD36375989D@tssg.org>
On Tue, Oct 25, 2005 at 09:46:25PM +0100, John Ronan wrote:
> I had unending difficulties when trying netrom and kernel 2.6... in
> the end I gave up and am running 2.4 now for stability.
>
> Linux version 2.4.29 (root@ei3rcw) (gcc version 3.3.5 (Debian
> 1:3.3.5-8)) #5 Fri Apr 15 13:37:45 IST 2005
>
> to be exact.
AX.25 in 2.4 isn't stable without extra patches either. There's a
patchset known as 9a4gl floating around which most users are quite happy
with - without 2.4 for serious use such as a mailbox or digipeater is
a no go.
At this late stage in the software lifecycle of 2.4 I won't try to
polish these patches into a shape that would make them acceptable for
kernel.org anymore - but if anybody else is interested I'd certainly give
my maintainer's approval.
Oh, and I've declared NET/ROM my next victim for a code overhaul now
that pure AX.25 in 2.6 seems stable enough for month of uptime and all
the important driver work except support for the PR-430 in the 6pack
driver has been submitted and accepted upstream.
73,
Ralf
prev parent reply other threads:[~2005-10-27 9:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-22 1:18 2.6.14-r4 crashing aa6qn
2005-10-22 8:52 ` jarmo
2005-10-22 12:52 ` Ralf Baechle DL5RB
2005-10-22 12:46 ` Ralf Baechle DL5RB
2005-10-22 18:42 ` aa6qn
2005-10-23 11:49 ` aa6qn
2005-10-24 11:19 ` Ralf Baechle DL5RB
2005-10-25 16:09 ` aa6qn
2005-10-25 20:46 ` John Ronan
2005-10-27 9:51 ` Ralf Baechle DL5RB [this message]
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=20051027095123.GA17645@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=aa6qn@aa6qn.sytes.net \
--cc=jronan@tssg.org \
--cc=linux-hams@vger.kernel.org \
/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