[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [linrad] Linrad01-12
- Subject: RE: [linrad] Linrad01-12
- From: "Robert McGwier" <rwmcgwier@xxxxxxxxxxxxxxx
- Date: Mon, 2 Feb 2004 22:40:22 -0000
It should be possible, especially under Linux, to have
graphics painting and signal processing on separate threads.
The signal processing is on the highest priority thread
and the screen gets repainted when it can. You can force
a repaint every N tries or M msec, etc.
[mailto:owner-linrad@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of Leif Åsbrink
Sent: Monday, February 02, 2004 9:16 PM
Subject: [linrad] Linrad01-12
After upgrading from a 600MHz PIII to a 2.6GHz PIV I
found some problems with Linrad.
1) The serial interface to the WSE converters was intended
to have a timing from the system clock. A simple bug caused
this to not function, causing timing ti be determined by
processor speed. Did not work on the PIV;)
2) When receiving large bandwidth (SSB/AM/FM) the
update rate for graphs becomes the limiting factor.
00-12 has slightly more efficient graphics that update
the screen less frequently. An AM station at 6 kHz
bandwidth that used 90% of the available CPU resources
on Linrad01-11 now uses about 10% of the CPU time.
3) When running Linrad on a computer with small memory,
the error messages indicating no more memory available
do not work in old Linrad versions if the swap file is
enabled. The Linux kernel just allocates memory on the hard
disk. Linrad-01.12 uses memory locking to ensure Linrad and
it's data will not be swapped. If locking fails an "out of
memory" will tell the operator to select less demanding
Bug reports are welcome.
Leif / SM5BSZ