Re: [Openocd-development] Event gdb-attach is called two times in a row on GDB attach
> [...] it is a very good idea to always use as recent versions as possible. If nothing else, than because there is a chance that someone would be interested in helping you in the community. -- Øyvind Harboe US toll free 1-866-980-3434 / International +47 51 63 25 00 http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Event gdb-attach is called two times in a row on GDB attach
Drasko DRASKOVIC wrote: > > git rebase really makes working on top of the master branch > > simple in most cases, .. > 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... You did not describe what requirements you are able to specify for deployment of the code that you create, so it is impossible to give concrete advice about how you would use git to best reach your goal, but rest assured that git can allow you to do it with very little effort, and indeed, it is a very good idea to always use as recent versions as possible. //Peter ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Event gdb-attach is called two times in a row on GDB attach
On Tue, Oct 26, 2010 at 11:02 AM, Øyvind Harboe https://lists.berlios.de/mailman/listinfo/openocd-development>> wrote: >/ On Tue, Oct 26, 2010 at 10:55 AM, Drasko DRASKOVIC />/ https://lists.berlios.de/mailman/listinfo/openocd-development>> wrote: />>/ On Tue, Oct 26, 2010 at 10:44 AM, Øyvind Harboe https://lists.berlios.de/mailman/listinfo/openocd-development>> wrote: />>>/ On Tue, Oct 26, 2010 at 10:34 AM, Drasko DRASKOVIC />>>/ https://lists.berlios.de/mailman/listinfo/openocd-development>> wrote: // On Mon, Oct 25, 2010 at 8:47 PM, Øyvind Harboe 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
Re: [Openocd-development] Event gdb-attach is called two times in a row on GDB attach
On Tue, Oct 26, 2010 at 11:02 AM, Øyvind Harboe wrote: > On Tue, Oct 26, 2010 at 10:55 AM, Drasko DRASKOVIC > wrote: >> On Tue, Oct 26, 2010 at 10:44 AM, Øyvind Harboe >> wrote: >>> On Tue, Oct 26, 2010 at 10:34 AM, Drasko DRASKOVIC >>> wrote: On Mon, Oct 25, 2010 at 8:47 PM, Øyvind Harboe 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. > 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... BR, Drasko ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Event gdb-attach is called two times in a row on GDB attach
On Tue, Oct 26, 2010 at 10:55 AM, Drasko DRASKOVIC wrote: > On Tue, Oct 26, 2010 at 10:44 AM, Øyvind Harboe > wrote: >> On Tue, Oct 26, 2010 at 10:34 AM, Drasko DRASKOVIC >> wrote: >>> On Mon, Oct 25, 2010 at 8:47 PM, Øyvind Harboe >>> 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. 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. -- Øyvind Harboe US toll free 1-866-980-3434 / International +47 51 63 25 00 http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Event gdb-attach is called two times in a row on GDB attach
On Tue, Oct 26, 2010 at 10:44 AM, Øyvind Harboe wrote: > On Tue, Oct 26, 2010 at 10:34 AM, Drasko DRASKOVIC > wrote: >> On Mon, Oct 25, 2010 at 8:47 PM, Øyvind Harboe >> 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. > > If you are working on changes that you are have no intention of rebasing to > master or contributing to the community, then of course you're pretty > much on your own... I guess that this is the case ;). I found a workaround hacking through target.c (target_register_event_callback registers one callback too many) and commenting out target_handle_event(target, event); call in target_call_event_callbacks() function (I have no idea what this is doing, but it is not doing it well). Now everything seems to be working. BR, Drasko ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Event gdb-attach is called two times in a row on GDB attach
On Tue, Oct 26, 2010 at 10:34 AM, Drasko DRASKOVIC wrote: > On Mon, Oct 25, 2010 at 8:47 PM, Øyvind Harboe > 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. If you are working on changes that you are have no intention of rebasing to master or contributing to the community, then of course you're pretty much on your own... -- Øyvind Harboe US toll free 1-866-980-3434 / International +47 51 63 25 00 http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Event gdb-attach is called two times in a row on GDB attach
On Mon, Oct 25, 2010 at 8:47 PM, Øyvind Harboe 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. ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Event gdb-attach is called two times in a row on GDB attach
> I am using openocd-0.4.0. Try the HEAD of the master branch. -- Øyvind Harboe US toll free 1-866-980-3434 / International +47 51 63 25 00 http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
