I'm not well versed in C. I was hoping to be able to map out the memory locations, and modify an existing driver. And I'm very unsure of any dangers to my hardware, so I'd like a little better understanding in that area. I mean, at some point I have to try writing to my radio, and I'm not sure what the worst case scenario is there or how to avoid it.
On Thu, Jan 04, 2018 at 09:57:36AM -0800, Silverfox wrote:
I don't think you need constrain yourself to a regional area to accomplish what you want to do but I suggest that if you are not well versed in C development and knowledgable to use data collection and debug techniques, you will have a hard time moving forward. I am not saying "don't try it" but you should be aware of the requisites. 73, Alan - W6ARH
-----Original Message----- From: chirp_devel-bounces@intrepid.danplanet.com [mailto:chirp_devel-bounces@intrepid.danplanet.com] On Behalf Of Rob Owens via chirp_devel Sent: Thursday, January 4, 2018 9:40 AM To: chirp_devel@intrepid.danplanet.com Subject: [chirp_devel] any Chirp developers in NJ, NY, or PA?
I now have three radios that are not supported by Chirp. Nobody has stepped up to add support, so I'm trying to teach myself how to do it. But I'm sure my learning curve would be much quicker if I had somebody experienced to work with for a day or so.
Is there anybody near northwestern New Jersey who would be willing to help me get started? I'm not looking for someone to do the work for me, just somebody to help remove the cloud of uncertainty I'm stuck in.
-Rob _______________________________________________ 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