> This problem was the reason why I added the callsign validity check in the
> listen code. I was annoyed because every now and then a garbled callsign
Which is great, but only removes the symptom, not the cause.
> > I have a PT or PackeTwin card. The device drivers for both a very similar.
> > I remember seeing some dramitic warnings in the packetwin driver code for
> > NOS, perhaps it is time to re-read them again. I would be nice if Don was
> > active.
>
> Wasn't the PT driver modified from the PI driver?
No, the NOS PT driver is radically different (in some areas) to the others.
The reason why I am so interested in hearing from any non-GPL users of the
PT code was that while the kernel interfacing was the same, the code for the
SCC was different. Memory is a little hazy, but I believe the original
version of the PT driver did not have this problem.
And do you know what is really annoying? For me to get a better PT device
driver, all I needed was for PacComm to say "yeah ok" and I'd be set, if
they own the copyright now that is. Then I could use some of the NOS code.
> The PI driver has had this problem at least as long as I have used my PI2
> card with Linux.
That's because the PI driver has been essentially the same, there are two
versions of the PT driver...
...and a hard drive failure finished off the first!
- Craig vk2xlz
-- // /\ | | | Craig Small VK2XLZ @home: papsugsm@kerailya.tunkki.fi ||==||===|==|=| [44.136.13.17] @play: fpqkm@eurociber.es \\ \/ | | | @work: exr@mail.dy.fi