From: Matti Aarnio <matti.aarnio@zmailer.org>
To: linux-hams@vger.kernel.org
Subject: mkiss kernel driver problems
Date: Thu, 1 Oct 2009 14:58:09 +0300 [thread overview]
Message-ID: <20091001115809.GC22922@mea-ext.zmailer.org> (raw)
Mostly the mkiss line discipline module seems to work, but..
mkiss: ax0: crc mode is auto.
mkiss: ax0: Switchting to crc-smack
that typo (extra 't') is obvious, but I am wondering,
why it has growing error counter:
ax0 Link encap:AMPR AX.25 HWaddr OH2MQK-1
UP BROADCAST RUNNING NOARP MTU:512 Metric:1
RX packets:9325 errors:152 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:10
RX bytes:622232 (607.6 KiB) TX bytes:0 (0.0 b)
I am feeding this interface from my own software via pty interface,
where the client side is turned on to KISS line discipline.
My own software is not complaining about incomplete writes,
thus I wonder what the kernel is doing ? Also my software
is sending on only AX.25 frames that it considers to be valid.
Does anybody remember how the mkiss.c is supposed to work?
73 de Matti, OH2MQK
next reply other threads:[~2009-10-01 11:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-01 11:58 Matti Aarnio [this message]
2009-10-01 14:33 ` mkiss kernel driver problems Matti Aarnio
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=20091001115809.GC22922@mea-ext.zmailer.org \
--to=matti.aarnio@zmailer.org \
--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;
as well as URLs for NNTP newsgroup(s).