mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: folkert <folkert@vanheusden.com>
To: linux-kernel@vger.kernel.org
Subject: problem with baycom driver
Date: Sat, 28 Jul 2012 23:38:33 +0200	[thread overview]
Message-ID: <20120728213832.GQ7638@belle.intranet.vanheusden.com> (raw)

Hi,

It seems the baycom driver (for ham radio) needs some attention.
The problems:
- the baycom_ser_hdx driver does not work at all: very occasionally it
  switches the radio to send and transmit the data, but that's only one
  in thousand
- the baycom_ser_fdx does seem to send, but only 1 or 2 packets, then
  something odd happens: the radio does transmit something but it is not
  recognizable as data. it sounds like a couple of ticks, not the
  recognizable modem sound. Important: if I do a sethdlc command, it
  again does send 1 or 2 valid packets!

The system on which I try it, is a 3.2GHz p4 (with HT) so I don't think
it is a problem with the system not keeping up.
The pc is a:
        Manufacturer: IBM
        Product Name: 8215F7G
        Version: ThinkCentre M52

Things are setup like this:
/bin/setserial /dev/ttyS0 uart none
/sbin/modprobe baycom_ser_fdx 'mode=ser12*' iobase=0x3f8 irq=4
/usr/bin/sethdlc -i bcsf0 -a txd 200 slot 100 ppersist 40 half
/sbin/ifconfig bcsf0 hw ax25 FH1GOU-1 up

I played a little with the txd and does not help. Using full or half
does not make a difference so far that it looks as if the first part of
the packet is missing if I full duplex mode but I'm not entirely sure of
that (no second modem setup).
I verified the problem by listening with a second radio.


Folkert van Heusden

             reply	other threads:[~2012-07-28 21:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-28 21:38 folkert [this message]
2012-08-02 20:02 ` problem with baycom driver - bisect help requested folkert
2012-08-02 20:32   ` folkert

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=20120728213832.GQ7638@belle.intranet.vanheusden.com \
    --to=folkert@vanheusden.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®