From: M Taylor <mctylr@privacy.nb.ca>
To: Ray Heasman <nurf@spamcop.net>
Cc: linux-hams@vger.kernel.org
Subject: Re: KJD 2.3.9 patch on 2.5.29
Date: Mon, 5 Aug 2002 20:35:20 +0100 [thread overview]
Message-ID: <20020805203520.A5959@pull.privacy.nb.ca> (raw)
In-Reply-To: <1028570528.20010.51.camel@maze.mythral.org>; from nurf@spamcop.net on Mon, Aug 05, 2002 at 11:02:06AM -0700
On Mon, Aug 05, 2002 at 11:02:06AM -0700, Ray Heasman wrote:
> Hi Ralf,
>
> and 2.2 kernels (I have yet to get it to run for >24 hours on a 2.4
> kernel without a kernel panic, with my Baycom scc card and all my other
> ports). Yes, it nominally sends some packets around. No, it doesn't do
> it correctly.
Do you have an decoded Oops from a 2.4 kernel panic?
> I think Jens suggestion to do most everything in userspace with a tiny
> link into some useful kernel support is the right way to go.
>
> I do see the point of making the current code worthy of being included
> in a stable kernel, but I think the "next" ax25 stack should be mostly
> in userspace and reimplemented from the ground up.
I disagree with the idea of putting the AX.25 (and/or Net/ROM) network
protocol stacks into userspace. That would be a silly idea with no
benefit.
The idea of putting amateur radio device drivers (mkiss, BayCom, soundcard,
SCC, etc.) in userspace only makes sense for soundcard and perhaps BayCom,
because of the amount of CPU utilitization by these drivers. Since I don't
use BayCom I am not certain, but it may or may not use enough CPU to
make it sensible to put it into userspace. I suspect userspace soundcard
is safer. Why would you want mkiss, SCC or other drivers in userspace?
M Taylor
next prev parent reply other threads:[~2002-08-05 19:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-01 19:46 KJD 2.3.9 patch on 2.5.29 Iain Young - G7III
2002-08-01 21:33 ` Hans-Peter Zorn
2002-08-02 18:38 ` Iain Young - G7III
2002-08-02 0:32 ` Ralf Baechle DO1GRB
2002-08-02 18:28 ` Iain Young - G7III
2002-08-05 12:28 ` Ralf Baechle DO1GRB
2002-08-05 17:19 ` Iain Young - G7III
2002-08-05 18:16 ` Ralf Baechle DO1GRB
2002-08-05 19:16 ` Ralf Baechle DO1GRB
2002-09-12 17:41 ` Joaquin Seoane
2002-10-01 11:39 ` KJD 2.3.9 patch on 2.5.29 (NOT FOUND) Joaquin Seoane
2002-08-05 18:02 ` KJD 2.3.9 patch on 2.5.29 Ray Heasman
2002-08-05 19:11 ` Ralf Baechle DO1GRB
2002-08-05 19:35 ` M Taylor [this message]
2002-08-06 10:22 ` Ralf Baechle DO1GRB
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=20020805203520.A5959@pull.privacy.nb.ca \
--to=mctylr@privacy.nb.ca \
--cc=linux-hams@vger.kernel.org \
--cc=nurf@spamcop.net \
/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