Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: "Øyvind Hanssen" <oyvind@cs.uit.no>
To: linux-hams@vger.kernel.org
Subject: AX.25 kernel module development
Date: Tue, 8 Apr 2003 14:36:15 +0200	[thread overview]
Message-ID: <200304081436.15919.oyvind@cs.uit.no> (raw)

Please excuse me if this has been discussed before.. 

There are some talk here about that the AX.25 Linux kernel code is broken. 
There has been attempts to create patches for the kernel; some are good but
arent (yet) included in the mainstream kernel, and there has been a serious 
attempt to rewrite the kernel stack as well (?) And it seems to be some 
uncertainty wrt. what is happening in Linux 2.5 (?)

It seem complicated to maintain patches for the Linux kernel the 
way it has been done, and I notice that someone has even suggested to 
implement the whole thing in userspace instead, at least to make it easier
to develop new protocols and drivers... 

What about keeping the core AX.25 stuff and drivers in kernel but split it
out from the mainstream Linux codebase and do the development in a separate
project instead; like e.g. the ALSA project has done until now? I guess 
that it would be easier to compile, maintain and add features to such 
a package than getting patches accepted for the mainstream Linux kernel. 

It is possible that a small part must remain in the kernel (socket API?), but
we shouldnt need to change this part too often. 

73 de LA7ECA, Øyvind
-
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

             reply	other threads:[~2003-04-08 12:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-08 12:36 Øyvind Hanssen [this message]
2003-04-08 13:30 ` AX.25 kernel module development M Taylor

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=200304081436.15919.oyvind@cs.uit.no \
    --to=oyvind@cs.uit.no \
    --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