From: Pidoux <f6bvp@free.fr>
To: "IT2 Stuart Blake Tener, USNR" <teners@bh90210.net>
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 19:19:53 +0100 [thread overview]
Message-ID: <47ED36C9.2030901@free.fr> (raw)
In-Reply-To: <C411A862.1EEA6%teners@bh90210.net>
IT2 Stuart Blake Tener, USNR a écrit :
> Mr. Pidoux, et alia:
>
> Are these patches bound to become part of the Linux kernel in a future
> Linux Kernel release or are these patches not yet blessed to be put into the
> next Linux Kernel release or never will be?
>
>
> V/R and 73,
>
> Stuart, N3GWG
>
>
> On 3/27/08 4:16 PM, "Bernard Pidoux F6BVP" <f6bvp@free.fr> 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.
>>
>> To apply the patches, you need kernel 2.6.24.3 sources installed and it
>> is required that you have already succeeded in compiling the kernel with
>> ax25 module.
>>
>> Save the above files into directory /usr/src
>> cd into that directory.
>>
>> Kernel source directory is :
>>
>> /usr/src/linux-2.6.24.3
>>
>> Make the following symbolic links if not already present :
>> ln -s linux-2.6.24.3 linux
>> ln -s linux a
>> ln -s linux b
>>
>> Then apply the patches by typing the following commands :
>>
>> patch -p0 < patch-2.6.24.3-net_rose_ax25
>>
>> patch -p0 < patch-2.6.24.3-net_rose_ax25_plus_plus
>>
>>
>> note: in -p0 above 0 is a zero (not letter O).
>>
>> The cd into linux.
>> Type the command :
>>
>> make
>>
>>
>> When compilation is finished, type the command :
>>
>> make modules_install
>>
>> And finally, type :
>>
>> make install
>>
>> Then reboot your system.
>>
>> You are encouraged to send any bug report to linux-hams list.
>>
>>
>> 73 de Bernard, f6bvp
>>
Most of the AX25 patches above are to be incorporated in a future kernel
release.
They were discussed on netdev list and approved by Dave Miller.
There is on:y one that is not yet official, as it is very new and the
bug it addresses is not yet completily solved.
However, like all others, its purpose is to remove causes of kernel
panics or crash.
And it works.
By informing refered lists about these patches my goal was to help OMs
having crash problems when using intensively AX25 applications.
They may safely upgrade to kernel.2.6.24.3 and use the patches provided.
You can also wait a month or two and you will have those patch included
in kernel 2.6.25 or 2.6.26.
Other part of the patches are related to ROSE module and not yet in the
future kernels cooker.
I built it after months of intensive experiments, in order to improve
ROSE routing.
I submitted the patches for ROSE to linux development Netdev list and
Ralf DL5RB.
I hope that most of them will be accepted for they give us good results
with FPAC a packet router based on ROSE protocole.
73 de Bernard, f6bvp
--
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-03-28 18:19 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 [this message]
2008-03-28 16:21 ` Patrick Ouellette
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=47ED36C9.2030901@free.fr \
--to=f6bvp@free.fr \
--cc=fpac@f6fbb.org \
--cc=linux-hams@vger.kernel.org \
--cc=teners@bh90210.net \
--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