[chirp_devel] Request Guidance to Add CHIRP Support for the Baofeng UV-5RAX 150/220 MHz Radio
Dan Smith
Sat May 4 13:51:34 PDT 2013
> No. This makes no sense because it won't work. Once an image is
> uploaded from another model, these first bytes will be replaced. :(
You mean if someone takes a VHF/UHF image and blows it into a VHF/220
radio?
Sounds like we should always read the first chunk of data from the
radio before we push an image out to it and fail if it doesn't match
what we want. We do this now for the firmware version, right? (see
do_upload() and _get_radio_firmware_version().
I think the right thing to do is subclass the main radio driver for the
220, and stash the byte that we expect to see for each in their
respective classes, so we can compare the driver being used to what the
radio returns.
Also, we'd need to modify match_model() so that it would load files
with the correct driver.
--
Dan Smith
www.danplanet.com
KK7DS
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: not available
Url : http://intrepid.danplanet.com/pipermail/chirp_devel/attachments/20130504/f51ef7a0/attachment-0001.bin
More information about the chirp_devel
mailing list