I created the uv6.py file last weekend. It is working and fairly complete.
Nice!
This radio doesn't have a keypad or display. So in a lot of ways this radio is quite similar to a UV-5R and in a lot of other ways it is quite different.
The memory layout that it uses is largely the same, but a few bytes here and there are used for different purpose in this radio than the others.
Can you give a few details of the differences? If it's, say, five bytes in memory that do different things then it might be best to keep the drivers unified and call out the differences. If it's fifty, then separate seems better. I'm sure you're making the right call here by having them separate, but we should just circle around and make sure that's what we want to do. It would be unfortunate to have to maintain two pieces of mostly-identical code going forward.
I've ripped out 99% of the structure and code from the uv5r.py that isn't used or necessary. I've also borrowed from other radios as well as cleaned up the code from what I've learn by 'hacking' on the uv5r.py file for the last 13 months.
Ripped out 99% of the non-overlapping code or 99% of the UV5 code entirely?
My plans were to submit the uv6.py file without the settings menus. Then follow that up with the Basic Settings after going over them one last time. And then the same of the additional menus. But I can try to combine this up if it is the right thing to do.
If they're going to be separate, then doing it incrementally, starting with minimal function is definitely fine with me.
--Dan