On Mon, Mar 6, 2017 at 10:22 PM, Dan Smith via chirp_devel chirp_devel@intrepid.danplanet.com wrote:
(Sorry for the delayed response)
Not knowing if the images from the various Vendors were 100% compatible, the model number was appended to the end of the data. The appended model number was then used to identify which Vendor/Model the image was from.
Changing the driver to use an alias for the non-Retevis variants, removed the Model variable that was used to match the images back to the correct Vendor/Model.
All the owners of the WLN and Zastone radios need to do is download from their radios again and save to a new image and everything should be OK. It is just that their currently saved images will have to be manually selected to be upload to their radios.
Okay, you're just talking about the RT22 driver behavior specifically, right? Not "all drivers that use Alias" right?
So you're saying we should revert that patch and add the one new model as a proper subclass yes?
--Dan
Yes. Jut the RT22 driver. I am still gun shy from dealing various Baofeng UV-5R variant firmware versions.
If I recall, the RT22 driver uses ranges for the upload and the areas of memory that could cause issues are skipped during the upload. So now I believe that should be OK.
The problem with not longer detecting a saved image for non-RT22 has presented itself, though.
http://chirp.danplanet.com/issues/4577
All that should be needed is to download from the radio and save as a native image. It will just show in the tab as a Retevis RT22 and pre-select that for the name when saving. No different than any other aliased radio.
Jim