hamlib-developer

[Hamlib-developer] TS-570D now reads filters properly

[Pierre F. <pf...@du...>]

Hello Fellow Hams,

Well, I figured out what was giving me fits, and I have now added the code to 
the TS-570 backend to read and properly report the filter settings.  The 
thing that had me stymied for a bit was in the .priv structure for the 570D 
kenwood_get_mode and kenwood_set_mode were defined rather than the 570 
specific functions ts570_get_mode/set_mode.  It was correctly laid out for 
the TS-570S, and I hadn't noticed the 570D section.  Anyway, it now works ... 
so how should I propogate the changes to the code base?

Thanks for your help and suggestions,

Pierre KC0IGY

Re: [Hamlib-developer] TS-570D now reads filters properly

[Stephane F. <f8...@fr...>]

On Tue, Feb 17, 2004, Pierre Fogal wrote:
> Well, I figured out what was giving me fits, and I have now added the code to 
> the TS-570 backend to read and properly report the filter settings.  The 
> thing that had me stymied for a bit was in the .priv structure for the 570D 
> kenwood_get_mode and kenwood_set_mode were defined rather than the 570 
> specific functions ts570_get_mode/set_mode.  It was correctly laid out for 
> the TS-570S, and I hadn't noticed the 570D section.  Anyway, it now works ... 
> so how should I propogate the changes to the code base?

A clean patch in unified format against cvs is best:   cvs diff -u
If you're not using cvs, then a diff -u against a reference version is fine.

For small patches, you can share them on the list.
Bigger patches should be gzipped, and sent to the maintainer of the
backend for commit after inspection.

Thanks
Stephane