Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: Richard Adams <pa3gcu@zeelandnet.nl>
To: linux-hams@vger.kernel.org
Subject: Re: soundmodem and fedora c3
Date: Thu, 10 Mar 2005 07:43:02 +0100	[thread overview]
Message-ID: <200503100743.02472.pa3gcu@zeelandnet.nl> (raw)
In-Reply-To: <422F2365.80902@cox.net>

On Wednesday 09 March 2005 17:25, you wrote:
> This was bothering me so I took another look.  I loaded my original FC3
>   .config into menuconfig.  Amateur radio support was not enabled.  I
> loaded the .config I am currently using and it definitely was enabled,
> so I must have had to turn it on when I enabled KISS.

There is no support for Ham protocols in Fedora3 kernels, you need to make 
your own kernel if you require ham radio support.

>
> I hope I didn't confuse the issues with my previous post.  I don't think
> you  need AX25 support in the kernel to use soundmodem, but if you want
> MKISS then you have to enable AX25 to get it (unless you manually edit
> .config, which is a really, really bad idea).

Well some say it is bad but most know its the easyest way to change things.
If you simply delete the section for AX25 support and its sub protocols and 
then run make oldconfig it will automaticly stop and ask you if you want AX25 
support in the kernel or as modules, when you select one or the other you 
will then be asked about netrom, rose, mkiss, scc drivers and the likes.
As soon as the last question has been answered the config process will fly on 
to the end.

Good or bad idea, well i´ve done it that way for years and never had problems.

> The reason I needed AX25 
> was that I have some other AX25 apps that require it.  I haven't tried
> routing between those devices and soundmodem, but I imagine you could do
> it with a pty/tty pair as Luc suggested.
>
> Jeff

Ron VE3DTT wrote.

> I still have a question which relates to the above postings by Richard Adams 
> and Jeff Camp. My boot configuration tells me that I don't have ham radio 
> support but menuconfig contains all asterisks in this area including ax.25, 
> tellimg me that this is built-in. Is this a contradiction or am I 
> misinterpreting it? Do I still have to re-build the kernel for ax.25 support 
> or am I simply looking at a configuration issue?

You may well have changed things yourself, but if you did not compile and 
install another kernel then you dont have AX25 support anywhere.

-
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:[~2005-03-10  6:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-09 14:41 soundmodem and fedora c3 Ron, VE3DTT
2005-03-09 16:25 ` Jeff Camp
2005-03-10  6:43   ` Richard Adams [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-03-08 17:35 Ron- VE3DTT
2005-03-08 17:42 ` Curt, WE7U
2005-03-08 17:44 ` Mike Markowski
2005-03-08 18:20 ` Jeff Camp
2005-03-08 20:07   ` Richard Adams
2005-03-08 20:13     ` Luc Langehegermann
2005-03-08 20:35       ` Curt, WE7U
2005-03-08 21:25     ` Jeff Camp
2005-03-09  6:35       ` Richard Adams
2005-03-08 18:55 ` oz6bl
2005-03-07 15:22 ronald schultz
2005-03-07 17:03 ` Curt, WE7U
2005-03-07 18:23   ` Tomi Manninen

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=200503100743.02472.pa3gcu@zeelandnet.nl \
    --to=pa3gcu@zeelandnet.nl \
    --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