[chirp_devel] [PATCH] [RFC] Add bitwise browser when developer options are enabled

[Marco IZ3GME]

Many thanks Dean!
I see is pretty easy to read, I find very helpfull to compare your code 
and mine side by side.

73 de IZ3GME Marco

On 04/03/2013 03:10, Dean Gibson AE7Q wrote:
> I also found an FT-897 layout in C++.   All is attached ...
>
> On 2013-03-03 11:39, Marco IZ3GME wrote:
>> Hi Dean!!
>> Here I am!
>> For what I've seen 857 and 897 share the very same memory mapping.
>>
>> Please send your code code to me: I already have written quite complete
>> mapping but, still, having something to compare can be of help and save
>> time.
>>
>> Many thanks
>> 73 de IZ3GME Marco
>>
>> On 03/03/2013 19:34, Dean Gibson AE7Q wrote:
>>> On 2013-03-03 09:58, Dan Smith wrote:
>>>>> Greatly appreciated: I'm working on the 857 settings, i'll test this
>>>>> patch for sure ;)
>>>>> I'll let you know my thoughts.
>>>> Cool, thanks :)
>>> I have a rather complete map of the FT-897D memory (which I understand
>>> is pretty much identical to the FT-857), and the FT-817ND as well.  The
>>> only problem is, it is in code written in Java, so I don't have clear
>>> bit-fields like I do in my C++ code for D-Star radios.  The Java code
>>> uses a table format describing the fields and the bit positions therein,
>>> using Java "enum"s, so the code isn't very clear to someone who is not
>>> familiar with that Java feature.
>>>
>>> If someone wants that (GPL v2) code, I have no problem providing it,
>>> with the understanding that I don't presently have the time to explain
>>> the code (flying weather is picking up).  It doesn't look too difficult
>>> to figure out.
>>>
>>> -- Dean
>>>
>>> ps: I used GPL v2 (without the "any later version" clause) in my code,
>>> because I don't particularly care for the idea that Richard Stallman
>>> could decide on a new GPL license, and have *users* arbitrarily adopt
>>> that, with unknown consequences to me.  I don't particularly mind v3 (I
>>> prefer v2;  I think it's a better license for my purposes), but I'm not
>>> comfortable with leaving the door open to any future revisions that he
>>> or anyone else at the FSF would create.  I don't believe that reverse
>>> engineering my code is a violation of the GPL v2 (at any rate I'll allow
>>> it in this circumstance), but I'd like to restrict its distribution to
>>> GPL v2 only.
>>>
>
>
>
> _______________________________________________
> chirp_devel mailing list
> chirp_devel at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
> Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
>