On Tue, Oct 26, 2010 at 11:02 AM, Øyvind Harboe <oyvind.harboe at zylin.com
<https://lists.berlios.de/mailman/listinfo/openocd-development>> wrote:
>/ On Tue, Oct 26, 2010 at 10:55 AM, Drasko DRASKOVIC
/>/ <drasko.draskovic at gmail.com
<https://lists.berlios.de/mailman/listinfo/openocd-development>> wrote:
/>>/ On Tue, Oct 26, 2010 at 10:44 AM, Øyvind Harboe <oyvind.harboe at zylin.com
<https://lists.berlios.de/mailman/listinfo/openocd-development>> wrote:
/>>>/ On Tue, Oct 26, 2010 at 10:34 AM, Drasko DRASKOVIC
/>>>/ <drasko.draskovic at gmail.com
<https://lists.berlios.de/mailman/listinfo/openocd-development>> wrote:
/>>>>/ On Mon, Oct 25, 2010 at 8:47 PM, Øyvind Harboe <oyvind.harboe at zylin.com
<https://lists.berlios.de/mailman/listinfo/openocd-development>> wrote:
/>>>>>>/ I am using openocd-0.4.0.
/>>>>>/
/>>>>>/ Try the HEAD of the master branch.
/>>>>/
/>>>>/ I can not, as I am creating patch for local use based on stable release.
/>>>/
/>>>/ Rebase your changes to git master. Read up on the git documentation
/>>>/ on how to do this. This is an area where git shines! If you don't know how
/>>>/ to do this, then you should make the investment in learning this if you
/>>>/ want the help from the community.
/>>/ Although I love git very much, I do not want to do this. I am working
/>>/ on a patch that I can share with some people locally, and I can not
/>>/ make a patch on a master branch that constantly changes.
/>/
/>/ In such cases, I think you'll be hard pressed to find help in the open
/>/ source community. If you show no intention of contributing back
/>/ to the community, that's a huge disincentive for the community
/>/ to work with you.
/I disagree on this, having a lot of experience in OS. Every bug
pointed, discussed and "workarounded" or solved, and any information
that can put some light on the problem are very helpful for all those
who come up with the same problem. Working for the community is not
only contribution of raw code, but more the right info that can be
shared. Here I pointed the problem and gave some solutions. It's a
mini-patch, if you like it - can be helpful for someone.
I have intention to share all innovative and useful stuff, as I always
did, but at this particular case it is something very specific (custom
FPGA design of JTAG interface on custom SoC) and will be totally
uninteresting for OpenOCD community as no person would use it.
I am really not sure it will be uninteresting. This will maybe not be
used directly if your Soc is ultra-specific, but it could give
opportunity to other developer to do the same (based on your example)
for an other Soc :-) !
Everything has something interesting !
Regards,
Laurent
http://www.amontec.com
Amontec JTAGkey-2 hi-speed USB JTAG Dongle
- 30Mhz JTAG TCK Frequency,
- RTCK support,
- 1.2V to 5.5V auto-sense,
- 32ma output drivers
- 2 connectivity LEDs (2x green)
- 2 activity LEDS (1x red 1x amber)
>/ It sounds like you don't have experience with git rebasing, because
/>/ git rebase really makes working on top of the master branch
/>/ simple in most cases, besides it is simply not true that
/>/ OpenOCD master branch "constantly changes" these days in the
/>/ sense that it would be hard or cumbersome to develop and rebase
/>/ most feature branches on top of it.
/OK, I'll see about this. But I am convinced that it will be more
easier for the most of the people to apply patch 6 months from now on
a stable release, than to clone dev branches, rebase, integrate the
changes etc...
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
