| 1 |
Mail from <[email protected]>, 02/06/01 |
| 2 |
|
| 3 |
Stephane mentioned the hamlib project to the |
| 4 |
linradio.sourceforge.net developers a few weeks |
| 5 |
ago. I believe my reply was routed to |
| 6 |
/dev/[email protected]. Anyway I have |
| 7 |
put some notes and early untested code at: |
| 8 |
|
| 9 |
http://linradio.sourceforge.net/hamlib.html |
| 10 |
|
| 11 |
|
| 12 |
Here are some winradio-specific issues: |
| 13 |
- Winradios are simple (henceforth cheap) receivers. The software |
| 14 |
driver does a lot of work that you would normally expect to see in |
| 15 |
an embedded controller. The driver is about 100KB of C. |
| 16 |
- Receivers come with ISA, PCMCIA and RS232 interfaces. |
| 17 |
- The protocol varies a lot across the model range. |
| 18 |
- Most models barely have an internal state. They can't even tell |
| 19 |
which frequency they are tuned to. |
| 20 |
- With most models, frequency sweeping must be done in software. This |
| 21 |
requires real-time tricks with RS232 (currently suboptimal). |
| 22 |
- High-end models have a DSP (not supported with Linux). |
| 23 |
|
| 24 |
We are currently providing two abstractions for all of this: |
| 25 |
- A kernel module which provides /dev/winradioX devices and ioctl API |
| 26 |
(radio_ioctl.h). |
| 27 |
- A user-mode driver which has problems with security (being root to |
| 28 |
use ISA receivers) and RS232 performance. |
| 29 |
|
| 30 |
The best approach is to create a hamlib-X.Y.Z/winradio/winradio.c file |
| 31 |
that wraps our ioctl API (toolkit/driver/radio_ioctl.h) into a "struct |
| 32 |
rig_caps". |
| 33 |
|