From c3e9dfd93fbf975c0ced53fdb93f37b38fcb8482 Mon Sep 17 00:00:00 2001 From: Nate Bargmann Date: Mon, 22 Aug 2011 21:32:35 -0500 Subject: [PATCH] Remove "$Id:" CVS tag as it is no longer used. --- kenwood/ts2k.c | 1 - kit/fifisdr.c | 3 +-- microtune/microtune.cc | 5 ++--- microtune/microtune.h | 1 - microtune/module_4702.c | 1 - microtune/module_4937.c | 1 - yaesu/README.ft890 | 8 +++---- yaesu/README.ft920 | 46 ++++++++++++++++++++--------------------- 8 files changed, 28 insertions(+), 38 deletions(-) diff --git a/kenwood/ts2k.c b/kenwood/ts2k.c index 5b389ed54..15295b39e 100644 --- a/kenwood/ts2k.c +++ b/kenwood/ts2k.c @@ -62,7 +62,6 @@ * Hamlib Kenwood backend - main file * Copyright (c) 2000-2002 by Stephane Fillod * - * $Id: ts2k.c,v 1.8 2009-02-03 23:22:58 azummo Exp $ */ diff --git a/kit/fifisdr.c b/kit/fifisdr.c index 911808390..1beff6490 100644 --- a/kit/fifisdr.c +++ b/kit/fifisdr.c @@ -1,5 +1,4 @@ -/* $Id: $ - * +/* * Hamlib KIT backend - FiFi-SDR Receiver(/Tuner) description * Copyright (c) 2010 by Rolf Meeser * diff --git a/microtune/microtune.cc b/microtune/microtune.cc index 8fa5e82a2..21995d677 100644 --- a/microtune/microtune.cc +++ b/microtune/microtune.cc @@ -2,7 +2,6 @@ * Hamlib Microtune backend - main file * Copyright (c) 2003 by Stephane Fillod * - * $Id: microtune.cc,v 1.3 2003-10-20 20:34:02 fillods Exp $ * * This library is free software; you can redistribute it and/or modify * it under the terms of the GNU General Public License as published by @@ -139,7 +138,7 @@ int microtune_set_freq(RIG *rig, vfo_t vfo, freq_t freq) { double actual_freq; bool status; - + struct microtune_priv_data *priv = (struct microtune_priv_data *)rig->state.priv; status = priv->board->set_RF_freq((double)freq, &actual_freq); @@ -153,7 +152,7 @@ int microtune_set_freq(RIG *rig, vfo_t vfo, freq_t freq) int microtune_get_freq(RIG *rig, vfo_t vfo, freq_t *freq) -{ +{ struct microtune_priv_data *priv = (struct microtune_priv_data *)rig->state.priv; *freq = priv->actual_freq; diff --git a/microtune/microtune.h b/microtune/microtune.h index fd66e9812..200852b6f 100644 --- a/microtune/microtune.h +++ b/microtune/microtune.h @@ -2,7 +2,6 @@ * Hamlib Microtune backend - main header * Copyright (c) 2001-2003 by Stephane Fillod * - * $Id: microtune.h,v 1.4 2003-10-20 20:34:02 fillods Exp $ * * This library is free software; you can redistribute it and/or modify * it under the terms of the GNU General Public License as published by diff --git a/microtune/module_4702.c b/microtune/module_4702.c index 385448398..4e8a1916a 100644 --- a/microtune/module_4702.c +++ b/microtune/module_4702.c @@ -2,7 +2,6 @@ * Hamlib microtune backend - 4702 file * Copyright (c) 2003 by Stephane Fillod * - * $Id: module_4702.c,v 1.1 2003-10-20 20:34:02 fillods Exp $ * * This library is free software; you can redistribute it and/or modify * it under the terms of the GNU General Public License as published by diff --git a/microtune/module_4937.c b/microtune/module_4937.c index b7cef7563..0e1fb9a5b 100644 --- a/microtune/module_4937.c +++ b/microtune/module_4937.c @@ -2,7 +2,6 @@ * Hamlib microtune backend - 4937 file * Copyright (c) 2003 by Stephane Fillod * - * $Id: module_4937.c,v 1.5 2003-10-20 20:34:02 fillods Exp $ * * This library is free software; you can redistribute it and/or modify * it under the terms of the GNU General Public License as published by diff --git a/yaesu/README.ft890 b/yaesu/README.ft890 index ee69800ed..8badf87ad 100644 --- a/yaesu/README.ft890 +++ b/yaesu/README.ft890 @@ -1,8 +1,6 @@ Quirks, known bugs, and other notes. ==================================== -$Id: README.ft890,v 1.1 2003-04-05 04:13:52 n0nb Exp $ - In this document I'll try to describe the behavior of the Yaesu FT-890 transceiver with Hamlib. Some of these are limitations of the radio while others are programming trade-offs with Hamlib. @@ -13,10 +11,10 @@ behavior with each call. rig_set_rit * RIG_VFO_* value is respected so the rig VFO may be changed with this call. - * To "zero" the RIT pass a value > 0 or < 10 with this call. The - digit will be dropped as resolution is 10 Hz minimum and the + * To "zero" the RIT pass a value > 0 or < 10 with this call. The + digit will be dropped as resolution is 10 Hz minimum and the clarifier offset set to 0 Hz. - + General notes. As with most all Yaesu radios the radio must be polled by the application for status updates, i.e. no transceive mode in CAT. diff --git a/yaesu/README.ft920 b/yaesu/README.ft920 index 40d6967aa..76fd5acec 100644 --- a/yaesu/README.ft920 +++ b/yaesu/README.ft920 @@ -1,8 +1,6 @@ Quirks, known bugs, and other notes. ==================================== -$Id: README.ft920,v 1.3 2003-01-19 04:47:59 n0nb Exp $ - In this document I'll try to describe the behavior of the Yaesu FT-920 transceiver with Hamlib. Some of these are limitations of the radio while others are programming trade-offs with Hamlib. @@ -11,13 +9,13 @@ This document is organized by Hamlib function calls and documents observed behavior with each call. rig_set_mode - * No matter the status of the main display, MEM or VFO, display + * No matter the status of the main display, MEM or VFO, display will be set to VFO mode if RIG_VFO_A or RIG_VFO_VFO is passed. - * If radio is in MEM or MEM TUNE state, main display mode can be - changed when RIG_VFO_MEM or RIG_VFO_MAIN is passed. + * If radio is in MEM or MEM TUNE state, main display mode can be + changed when RIG_VFO_MEM or RIG_VFO_MAIN is passed. * When RIG_VFO_CURR is passed, the display will be set per the VFO stored by the last rig_get_vfo call. - * Modes DATA USB and DATA FM cannot be set at this time + * Modes DATA USB and DATA FM cannot be set at this time (Hamlib limitation). See below. * My FT-920 does not support USB/LSB narrow so attempting to set a narrow passband with these modes will return an Invalib @@ -29,34 +27,34 @@ rig_get_mode * DATA LSB is mapped to RIG_MODE_RTTY. * I would like to hear from anyone who gets a narrow passband value in USB/LSB mode returned. - + rig_set_freq - * When passed RIG_VFO_A or RIG_VFO_VFO the main display is forced + * When passed RIG_VFO_A or RIG_VFO_VFO the main display is forced to VFO mode and then the frequency is set. * When passed RIG_VFO_B or RIG_VFO_SUB, the sub display frequency is set. - * When passed RIG_VFO_MEM, or RIG_VFO_MAIN, the main display - frequency is set regardless of whether the main display is in + * When passed RIG_VFO_MEM, or RIG_VFO_MAIN, the main display + frequency is set regardless of whether the main display is in memory (thus activating MEM Tune) or VFO mode. * When RIG_VFO_CURR is passed, the display will be set per the VFO stored by the last rig_get_vfo call. * RIG_TARGETABLE_ALL is properly handled (I think). rig_get_freq - * When passed RIG_VFO_A or RIG_VFO_VFO, the radio returns the - frequency in the main VFO, even if the main display is in MEM or + * When passed RIG_VFO_A or RIG_VFO_VFO, the radio returns the + frequency in the main VFO, even if the main display is in MEM or MEM Tune. * When passed RIG_VFO_B or RIG_VFO_SUB, the sub-display frequency is returned. - * When passed RIG_VFO_MEM or RIG_VFO_MAIN, the current main display + * When passed RIG_VFO_MEM or RIG_VFO_MAIN, the current main display frequency is returned regardless of main display mode. * When passed RIG_VFO_CURR, the display will be read per the VFO stored by the last rig_get_vfo call. rig_set_vfo - * When called with RIG_VFO_A or RIG_VFO_VFO, the radio appears to - do nothing, however, rig_state->current_vfo will be updated. - * When called with RIG_VFO_B, the radio will swap the main and sub + * When called with RIG_VFO_A or RIG_VFO_VFO, the radio appears to + do nothing, however, rig_state->current_vfo will be updated. + * When called with RIG_VFO_B, the radio will swap the main and sub displays, the same as if the front panel A<>B button is pressed. * No provision exists to make VFO-B (sub display) the active RX through CAT. @@ -66,7 +64,7 @@ rig_get_split but Hamlib only supports an indication that the radio is split. * The VFO value passed is not used by the ft920 backend lib. FIXME: Is this a problem? - + rig_set_split * When called with RIG_SPLIT_OFF the radio will make TX A active if TX B was active, otherwise no change. @@ -74,15 +72,15 @@ rig_set_split TX A was active, otherwise no change. * The FT-920 has no capability to change the active RX to RX B (sub display) through CAT. Thus if VFO-B is active RX/TX the setting - RIG_SPLIT_ON will make no visible change on the radio. + RIG_SPLIT_ON will make no visible change on the radio. * The VFO value passed is not used by the ft920 backend lib. FIXME: Is this a problem? - + rig_set_split_freq * Backend simply wraps rig_set_freq--calling app needs to specify target VFO to set frequency. Should backend determine split and set "proper" VFO? - + rig_get_split_freq * Backend simply wraps rig_get_freq--calling app needs to specify target VFO to set frequency. Should backend determine split @@ -92,7 +90,7 @@ rig_set_split_mode * Backend simply wraps rig_set_mode--calling app needs to specify target VFO to set frequency. Should backend determine split and set "proper" VFO? - + rig_get_split_mode * Backend simply wraps rig_get_mode--calling app needs to specify target VFO to set frequency. Should backend determine split @@ -101,14 +99,14 @@ rig_get_split_mode rig_set_rit * Hamlib specificies that passing 0 as the RIT frequency disables RIT. Thus there is no way to meet the spec and mimic the front - panel RIT off function whilst keeping the RIT offset on the + panel RIT off function whilst keeping the RIT offset on the display. The Hamlib spec causes behavior analogous to shutting RIT off and then pressing the Clear button. * There is no direct way to set RIT offset of VFOB/SUB. However, rig_set_vfo can be used to swap VFO B and main, then set RIT, then call rig_set_vfo to swap VFO B and main. FIXME: Should backend do this automatically? - + rig_get_rit * Backend returns clarifier offset regardless of whether RIT is on. * vfo is honored and stored RIT is returned. @@ -116,7 +114,7 @@ rig_get_rit rig_set_xit * Hamlib specificies that passing 0 as the XIT frequency disables XIT. Thus there is no way to meet the spec and mimic the front - panel XIT off function whilst keeping the XIT offset on the + panel XIT off function whilst keeping the XIT offset on the display. The Hamlib spec causes behavior analogous to shutting XIT off and then pressing the Clear button. * There is no direct way to set XIT offset of VFOB/SUB. However,