From: Jason Flynn G7OCD <jason.flynn@btinternet.com>
To: Riley Williams <Riley@Williams.Name>
Cc: M Taylor <mctylr@privacy.nb.ca>,
John Ackermann N8UR <jra@febo.com>,
linux-hams@vger.kernel.org
Subject: Re: Responses to my Kenwood D7 question
Date: Sun, 11 Aug 2002 18:14:05 +0100 [thread overview]
Message-ID: <3D569B5D.2020506@btinternet.com> (raw)
In-Reply-To: Pine.LNX.4.21.0208111720040.8397-100000@Consulate.UFP.CX
Riley Williams wrote:
> Does anybody have details of precicely what sort of functions are
> implemented in the KISS mode that is implemented in the TH-D7 ???
> If so, perhaps somebody can write code for the Linux kernel that
> works around whatever limitations it has.
Basically, it's not 8bit clean. I can't see a workaround for this.
This is the story:
In the D7E (note E) mark 1 the TX didn't work. I complained a bit
about this and after a while Kenwood UK told me there would be a
mark 2 because alot of people wanted to use DAMA in Europe (and
most DAMA slaves were PC based?) so they would 'fix' KISS.
So I got on a trial with them.. After a few revisions they got
to this:
1) TX in KISS mode fixed. Good.
2) Note arrives with beta handset from Kenwood JP something like
this :
" To 'make room' for this in the ROM, we had to remove Transparent
Mode from non-KISS mode. Also while in KISS mode can't send binary"
So I told them, that unless it was KISS as in they proper spec then
there was no point in releasing it. They told me they already commited
to a mask for new PROMS. So now I had a handy with a built in TNC
that
1) STILL can't do KISS
2) Can't send binary when not in KISS mode... so I was stuck with
7+/YAPP/UUE etc :-(
After that, I sold mine.
J
next prev parent reply other threads:[~2002-08-11 17:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-03 12:47 Responses to my Kenwood D7 question John Ackermann N8UR
2002-08-04 16:27 ` M Taylor
2002-08-11 16:23 ` Riley Williams
2002-08-11 17:14 ` Jason Flynn G7OCD [this message]
2002-08-11 17:38 ` Riley Williams
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=3D569B5D.2020506@btinternet.com \
--to=jason.flynn@btinternet.com \
--cc=Riley@Williams.Name \
--cc=jra@febo.com \
--cc=linux-hams@vger.kernel.org \
--cc=mctylr@privacy.nb.ca \
/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