| |
VK7AX > LINHAM 20.07.08 08:27l 54 Lines 1900 Bytes #999 (0) @ WW
BID : VK7AX-2007LA
Read: GUEST
Subj: baycom_ser_fdx - fixed under 2.6
Path: IZ3LSV<IK2XDE<IS0FLO<CX2SA<VK7AX
Sent: 080720/0721Z @:VK7AX.#ULV.TAS.AUS.OC #:49434 [Ulverstone] FBB7.00g $:VK7A
From: VK7AX@VK7AX.#ULV.TAS.AUS.OC
To : LINHAM@WW
From: David Robb <ender(AT)paradise.gen.nz>
Date: Sat, 19 Jul 2008 10:50:51 +1200 (NZST)
To: linux-hams(AT)vger.kernel.org
So it seems that I might be the only person in the world who's still
attempting to use a Baycom bp-1 pocket modem under Linux, but oh well..
As a number of people noticed back in about 2005 (and some even earlier),
the baycom_ser_fdx driver hasn't worked under Linux 2.6 for a few years
(possibly ever).
Various people poked around (http://osdir.com/ml/hams/2005-05/msg00022.html)
and determined that there was some kind of packet corruption going on,
and that the CRC was mangled.
Well, after bashing my head against it a few times over the last few months
(I guess I was bored), and finally thinking that it mightn't be in the
baycom_ser_fdx driver that the problem actually was, I tracked it down to
the hdlcdrv code instead...
Someone called Micah actually figured this out in 2004, and submitted a patch,
but it never made it into the kernel
(at least in my 2.6.25.7 it's still broken):
http://linux.derkeiler.com/Mailing-Lists/Kernel/2004-11/2929.html
The CRC's overwriting some of the packet...
So anyway, applying the patch listed at that URL (1 line! Just one little line!)
my BP-1 now works again under 2.6.25.
Perhaps I'm strange for wanting this working in these days of high speed links,
but hey... it seems sad to have broken code and no support where there used
to be a functional device.
Anyway, share and enjoy.
--David ZL3UDR
***************************************************************
ABOVE IS A CROSS POST TO THE PACKET RADIO NETWORK IN AN EFFORT
TO PROMOTE FURTHER INTEREST IN HAM SOFTWARE USING LINUX
OPERATING SYSTEMS AND PACKET RADIO
Courtesy Tony VK7AX VK7AX(AT)VK7AX.#ULV.TAS.AUS.OC
***************************************************************
Read previous mail | Read next mail
| |
