Correct - I'll try out the approach that I outlined and included that in the next patch, with the other fixes.



On Sat, Apr 25, 2015 at 7:30 AM, Dan Smith <dsmith@danplanet.com> wrote:
> For the auto file identification, I was going to try looking at the
> frequency ranges in the image file for identification.  These are
> non-overlapping between the three models, and they are in a fixed
> location in the image file.   Eg.   The 144 mhz models has a settable
> tx/rx range between 132 and 152 Mhz (or close to this), the 220 Mhz
> model has 200-250 mhz, etc.
>
> The file sizes are the same, AFAIK, for all three, so I can't use that
> approach.  The image files don't have a consistent or usable "id string"
> to help identity them ( I did a od/hex dump and reviewed what's there),
> at least for the two radios ( 2 meter and 220 mhz models) that I have.

Sure, I thought that you were indicating that you couldn't provide
identification for this driver. Sounds like you should be able to use
file size to rule all the other models out and use band limits to
distinguish within the 9000 line among the sub-models, right?

Thanks!

--Dan


_______________________________________________
chirp_devel mailing list
chirp_devel@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers