Patch with support for disabling transmit on memory channels

[Google Code Exporter]

I've got a small patch to add support for disabling transmit on the UV-5R 
(tested on the UV-5RA) on a channel-by-channel basis. 

I've added support for specifying "-" in the TX offset field of a config file 
channel line to mean "disable transmit." 

If the parser sees a "-," the TX offset will be set to the max frequency, which 
will make the TX frequency passed to setup_channel() greater than the max 
frequency. 

If setup_channel() gets an out of valid range TX frequency, it will set the 
frequency in the radio to 0xffffffff, which appears to be the Baofeng's code to 
disable transmit on the channel. See http://chirp.danplanet.com/issues/211 for 
a discussion of this. I've confirmed that setting this does disable TX on my 
UV-5RA. 

On the config generation side, if the radio or .img contains a frequency of 
1666666650 Hz, equivalent to 0xffffffff, the config printer will output "-" 
instead of a computed offset. 

Here's the comparison on Github of my branch with your master: 
https://github.com/casebeer/baoclone/compare/disabled-transmit

The branch with the change is "disabled-transmit:" 
https://github.com/casebeer/baoclone/tree/disabled-transmit

Please let me know if there's anything you'd like me to change about this, or 
that you'd like clarification on. 

Thanks, 

Chris

Original issue reported on code.google.com by [e-mail] on 23 Sep 2013 at 11:43

[Google Code Exporter]

This issue was closed by revision bee94d9ba2fc.

Original comment by [e-mail] on 27 Sep 2013 at 4:36

• Changed state: Fixed

[Google Code Exporter]

Patch checked in as bee94d9 (with minor modifications). Thanks, Chris!

Original comment by [e-mail] on 27 Sep 2013 at 4:38