From: Matti Aarnio <matti.aarnio@zmailer.org>
To: Jim Kusznir <jkusznir@gmail.com>
Cc: linux-hams@vger.kernel.org
Subject: Re: Linux Packet Interface Hardware
Date: Wed, 16 Jun 2010 04:24:52 +0300 [thread overview]
Message-ID: <20100616012452.GN898@mea-ext.zmailer.org> (raw)
In-Reply-To: <AANLkTim2kyUNlW4OOJc42U_CUFzFw1Ox0OhoymamsOTz@mail.gmail.com>
On Tue, Jun 15, 2010 at 04:43:45PM -0700, Jim Kusznir wrote:
>
> Hi all:
>
> I'm in the process of designing some kinda-embedded applications that
> will need to employ packet "compatibility layers" to allow access of
> packet radios.
>
> In one application, I'm proposing relacing a node stack with a linux
> box, some interface (subject of this e-mail), and the existing radios
> with their audio (discriminator if appropriate), tx line, squelch
> line, etc. Other applications may not be as demanding as the nodes,
> but similar. In essence, I'm looking for a device to connect to the
> equivalent of the 6-pin mini-din connector used for "data" on most
> modern radios and linux.
>
> I'm familiar with the state of the art back in the late '90's. I also
> realize that not a lot has necessarily changed since then....
> However, I suspect something may have.
>
> the solution should be capable of running several different packet
> interfaces, and at 9600 or 1200 baud. These interfaces should turn
> into linux axX interfaces.
I would suggest making it an USB device with "BPQether" type of interface.
At USB level it would look like a _generic_ ( = no extra drivers )
ethernet, but it would understand only BPQether type of packets, and
therefore would not get to transmit just anything that system happens
to send on its way.
There would be need for unique serial numbers ( = "mac address" ) for
the devices. Anything would be good as long as first byte of MAC
address has its lowest bit clear (the multicast indicator)
(Even prefix "BPQ" = 0x42, 0x50, 0x51 )
See "man bpqparams" for the control interface.
To implement a control command channel, like to set ptt delays, etc.
that could be an AX.25 frame with destination call of 'NOCALL' (the
classical misconfiguration token) and an UI frame with control data.
Speed would be fixed, but nothing prevents having multiple virtual
ethernet interfaces in same USB device, each with their own speeds.
As a bonus, this same hardware could be plugged on Windows as well
without any special drivers. If the settings are correct, then on
windows a BPQ32 suite will be able to drive it too - and you get
even more people interested in that device.
> Thanks!
> --Jim, K7LL
73 de Matti, OH2MQK
next prev parent reply other threads:[~2010-06-16 1:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-15 23:43 Linux Packet Interface Hardware Jim Kusznir
2010-06-16 1:19 ` Ray Wells
2010-06-16 1:24 ` Matti Aarnio [this message]
2011-02-15 18:36 ` Jim Kusznir
2010-06-16 2:05 ` Dave Platt
2010-06-16 12:45 ` Curt, WE7U
2010-06-16 16:16 ` Jim Kusznir
2010-06-16 16:46 ` Curt, WE7U
2010-06-16 23:25 ` Jim Kusznir
2010-06-17 12:49 ` Curt, WE7U
2010-06-21 6:17 ` walter harms
2010-06-16 22:29 ` Matti Aarnio
2010-06-16 23:53 ` Dave Platt
2010-06-16 22:29 ` Dave Platt
2010-06-16 22:49 ` Matti Aarnio
2010-06-16 23:33 ` Curt, WE7U
2010-06-17 0:02 ` Dave Platt
-- strict thread matches above, loose matches on Subject: below --
2010-06-17 2:24 Andrew Errington
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=20100616012452.GN898@mea-ext.zmailer.org \
--to=matti.aarnio@zmailer.org \
--cc=jkusznir@gmail.com \
--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