Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: Ray Wells <mvc@midcoast.com.au>
To: Chuck Hast <wchast@gmail.com>
Cc: linux-hams@vger.kernel.org
Subject: Re: 6pack query
Date: Mon, 31 Oct 2005 06:54:35 +1100	[thread overview]
Message-ID: <436524FB.1040203@midcoast.com.au> (raw)
In-Reply-To: <620c90570510300437w7c9b9a8cp5a9bcc738120d638@mail.gmail.com>


Chuck Hast wrote:

>On 10/29/05, Ray Wells <mvc@midcoast.com.au> wrote:
>  
>
>>Hello learned members of the list,
>>
>>I'm contemplating changing my KISS only EPROMs for 6PACK (to perhaps
>>improve matters on my 0k3 HF ports)
>>
>>The kernel (2.2.20) has been compiled to include 6PACK - compiled in,
>>not as a module.
>>
>>Given that there is no equivalent of kissparms for 6PACK, how does one
>>set parameters such as txd, slottime, etc?
>>
>>In my mind, given that spattach is symbolically linked to kissattach,
>>the parameters are set with kissparms in the same way as they are with
>>KISS TNCs.
>>
>>Am I correct in my thinking, or way off target?
>>    
>>
>
>Ray,
>I am running it and that appears to be the way it works. I have set up my
>kissparms and when i change them I can see the changes in the way the
>TNC operates.
>
>
>--
>Chuck Hast
>To paraphrase my flight instructor;
>"the only dumb question is the one you DID NOT ask resulting in my going
>out and having to identify your bits and pieces in the midst of torn
>and twisted metal."
>
>
>  
>
Thanks Chuck,

I appear to have guessed that part correctly. However, I may have bombed 
out in believing that spattach was "ready to go".

Upon close inspection of kissattach.c I find that a change as per 
/.../6pack.txt hasn't been implemented.

So, for my next question, if I make the change and recompile kissattach, 
and rename it spattach, can I still use the original kissattach for KISS 
applications?

Ray

  reply	other threads:[~2005-10-30 19:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-30  2:52 6pack query Ray Wells
2005-10-30 12:37 ` Chuck Hast
2005-10-30 19:54   ` Ray Wells [this message]
2005-10-30 21:35     ` Chuck Hast
2005-10-31 15:10       ` Iñaki Arenaza
2005-10-31 15:56         ` Ralf Baechle
2005-10-31 19:29           ` Iñaki Arenaza
2005-11-01 13:40             ` Ralf Baechle DL5RB
2005-11-01 14:20               ` Chuck Hast
2005-11-01 14:31                 ` Ralf Baechle DL5RB
2005-11-01 17:11                   ` Chuck Hast

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=436524FB.1040203@midcoast.com.au \
    --to=mvc@midcoast.com.au \
    --cc=linux-hams@vger.kernel.org \
    --cc=wchast@gmail.com \
    /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