From: Patrick Ouellette <ne4po@arrl.net>
To: Bernard Pidoux F6BVP <f6bvp@free.fr>
Cc: List for LINUX ROSE/FPAC network switch <fpac@f6fbb.org>,
List for the LINUX version of FBB <xfbb@f6fbb.org>,
linux-hams <linux-hams@vger.kernel.org>
Subject: Re: kernel 2.6.24.3 patches for AX25
Date: Fri, 28 Mar 2008 12:21:40 -0400 [thread overview]
Message-ID: <20080328162140.GC22445@flying-gecko.net> (raw)
In-Reply-To: <47EC2AC6.7020509@free.fr>
On Fri, Mar 28, 2008 at 12:16:22AM +0100, Bernard Pidoux F6BVP wrote:
>
> Hi All,
>
> Participating in AX25, ROSE, FPAC, and LinFBB debugging, I want to share
> with you the recent progress accomplished with Linux kernel.
>
> While the code is not yet fully debugged, there have been significant
> progress and I summarized them into two patches that, when applied to
> kernel 2.6.24.3, lead to a much more stable system.
>
> The two patches must be applied one after the other.
>
> First one is here :
> http://f6bvp.free.fr/logiciels/ax25/patch-2.6.24.3-net_rose_ax25
>
> I have already reported it to a few OMs running FPAC application.
> It was here :
> http://f6bvp.free.fr/logiciels/rose-fpac/patch-2.6.24.3.ax25.tgz
>
> Do not try to apply the first patch if the original kernel source have
> been already patched.
>
> Second patch is here :
> http://f6bvp.free.fr/logiciels/ax25/patch-2.6.24.3-net_rose_ax25_plus_plus
>
> I am running patched kernels on three different architectures with AX25
> applications and the systems are quite stable.
> One of them has even a core2 duo CPU and the kernel was compiled with
> SMP option for multiple CPUs.
>
Could you share what particular problems the patches address? Maybe
send the changelog entries to the list?
Thanks & 73,
Pat NE4PO
--
Patrick Ouellette pat@flying-gecko.net
ne4po (at) arrl (dot) net Amateur Radio: NE4PO
"Crank the amp to 11, this needs more cowbell - and a llama wouldn't hurt either"
"Your arguments are an odd mix of overly optimistic on one side and overly
pessimistic on the other"
next prev parent reply other threads:[~2008-03-28 16:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4787000B.3000606@exemail.com.au>
[not found] ` <47911A1A.5010107@ccr.jussieu.fr>
[not found] ` <47911E64.4080201@exemail.com.au>
[not found] ` <000901c85a23$f00a6f30$d01f4d90$@rr.com>
[not found] ` <47913227.3070504@exemail.com.au>
[not found] ` <620c90570801182002w7575fe39j4e94d982b945a24a@mail.gmail.com>
[not found] ` <479179C8.70505@exemail.com.au>
[not found] ` <4791CC2F.5060307@ccr.jussieu.fr>
[not found] ` <47926437.3020005@exemail.com.au>
[not found] ` <47928684.8090108@ccr.jussieu.fr>
[not found] ` <47B2292A.7020001@free.fr>
[not found] ` <47B22D82.1060206@exemail.com.au>
[not found] ` <47B30AC4.9050306@earthlink.net>
[not found] ` <47C07B3B.4000700@free.fr>
[not found] ` <47CD71B7.6060606@earthlink.net>
[not found] ` <47D3B37C.5050901@free.fr>
2008-03-27 23:16 ` kernel 2.6.24.3 patches for AX25 Bernard Pidoux F6BVP
2008-03-28 2:39 ` IT2 Stuart Blake Tener, USNR
2008-03-28 18:19 ` Pidoux
2008-03-28 16:21 ` Patrick Ouellette [this message]
2008-03-28 21:31 ` Pidoux
2008-03-28 23:59 ` Tihomir Heidelberg - 9a4gl
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=20080328162140.GC22445@flying-gecko.net \
--to=ne4po@arrl.net \
--cc=f6bvp@free.fr \
--cc=fpac@f6fbb.org \
--cc=linux-hams@vger.kernel.org \
--cc=xfbb@f6fbb.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