Hello again, I'm still learning my ways around git and was not sure how to add files to the repository control and submit those in form of patch. Could I ask you to add Signalyzer H2 (signalyzer-h2.cfg), Signalyzer H4 (signalyzer-h4.cfg) and Signalyzer LITE (signalyzer-lite.cfg) interface config files to ./tcl/interface .
Files are attached to this message. Many thanks, Oleg --- www.signalyzer.com On Tue, Oct 27, 2009 at 6:53 AM, Signalyzer ( www.signalyzer.com ) <[email protected]> wrote: > Hello David, > > Please find attached a subset of the Signalyzer H support that will > compile with released version of libftdi and not require proposed > libftdi mods. > > I sincerely hope they will make into 0.3.0 release. > > Best regards, > > (I apologize for duplicate message) > > Oleg > > > On Sun, Oct 25, 2009 at 8:02 PM, David Brownell <[email protected]> wrote: >> On Saturday 24 October 2009, Zach Welch wrote: >>> Thanks for being responsive to David's requests. While this patch looks >>> great for reviewing your new device's support, I think that we should >>> avoid pushing it to the repository. We should wait for the libftdi >>> patch to be committed and scheduled for some future release. >> >> Yeah. We want to avoid being dependent on other projects. >> >> However, if there's a subset that could merge unconditionally >> without needing any libftdi patches, that'd likely be good. >> It'd get customers at least partial functionality sooner; and >> would constrain the amount of work to be done later. >> >> - Dave >> >>> Users should never be asked to patch a library to enable a configure >>> option, so -- until those changes are in its mainline -- you should >>> repost (with status updates) when this patch no longer applies cleanly. >>> So long as users need to wrangle the libftdi patch, they can manage to >>> apply this one too. So, this is not rejection, but rather a request for >>> temporary deferral. >>> >>> If the libftdi maintainers repeatedly ignore your patch, then we can >>> revisit this topic at that point; however, that seems unlikely to occur. >> >> >
signalyzer-h2.cfg
Description: Binary data
signalyzer-h4.cfg
Description: Binary data
signalyzer-lite.cfg
Description: Binary data
_______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
