Re: [Openocd-development] RFC Release Cycle

So when I send a pull request to you from my repository, would you rebase or merge? We now have a nice linear history, which gives me a warm fuzzy feeling for a simple project like OpenOCD What would a typical pull request look like? Subject: Pull request - my master branch has some fixes

Re: [Openocd-development] OpenOCD 0.5.0-rc1 release

On Wed, Jun 29, 2011 at 7:43 AM, simon qian wrote: > Is it possible to update Versaloon driver in 0.5.0 release? > Mail me if there is any problem with the driver patch. I don't have a problem with applying this patch as it only affects the versaloon interface driver... -- Øyvind Harboe - Can

Re: [Openocd-development] OpenOCD 0.5.0-rc1 release

Is it possible to update Versaloon driver in 0.5.0 release? Mail me if there is any problem with the driver patch. 2011/6/29 Øyvind Harboe > On Wed, Jun 29, 2011 at 2:30 AM, Jean-Christophe PLAGNIOL-VILLARD > wrote: > > On 20:20 Tue 28 Jun , Øyvind Harboe wrote: > >> Where is the plan? > >

Re: [Openocd-development] OpenOCD 0.5.0-rc1 release

On Wed, Jun 29, 2011 at 2:30 AM, Jean-Christophe PLAGNIOL-VILLARD wrote: > On 20:20 Tue 28 Jun     , Øyvind Harboe wrote: >> Where is the plan? > I'll write the patch when we have finish the discussion about the workflow > now we just close the merge window k. While we're working out the new work

Re: [Openocd-development] RFC Release Cycle

>> I'd have some reservations about only one person having write >> access, but not particularly the way of working. Call me old fashioned. > Does not mean you do not have the write access does just mean you dont use it > As example if the release manager is in vacantion or too much busy you use it

Re: [Openocd-development] compiler warnings with dsp5680xx.c

Thanks for the fast response! Better, but one more: libtool: compile: nios2-linux-gnu-gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I/home/oyvind/workspace/zy1000/build/../openocd/src/target -I../.. -I/home/oyvind/workspace/zy1000/build/../openocd/src -I../../src -DPKGDATADIR=\"/opt/zy1000/share/openocd

Re: [Openocd-development] compiler warnings with dsp5680xx.c

ok, now i've tested everything and it works ok. as i said on the other mail, i modified the read functions and got rid of the casting warnings. the first patch has the changes to get rid of the warnings, and the second patch re-enables the target. thanks On Tue, Jun 28, 2011 at 8:22 PM, Rodrigo

Re: [Openocd-development] compiler warnings with dsp5680xx.c

i've been doing some testing and i realized i missed several important things. please ignore the previous patch. i am preparing a correct one. thanks. On Tue, Jun 28, 2011 at 4:51 PM, Rodrigo Rosa wrote: > hi > > i modified the read functions and got rid of the casting warnings. > been trying th

Re: [Openocd-development] OpenOCD 0.5.0-rc1 release

On 20:20 Tue 28 Jun , Øyvind Harboe wrote: > Where is the plan? I'll write the patch when we have finish the discussion about the workflow now we just close the merge window > > Could you create a mirror at the openocd git mirror? > > We've done that so far and it makes it easier to find stuf

Re: [Openocd-development] RFC Release Cycle

On 19:56 Tue 28 Jun , Øyvind Harboe wrote: > On Tue, Jun 28, 2011 at 7:30 PM, Jean-Christophe PLAGNIOL-VILLARD > wrote: > > On 19:39 Tue 28 Jun     , Øyvind Harboe wrote: > >> > but now all the maintainer will have their own fork/repository > >> > as done in the kernel > >> > >> Right. And you

Re: [Openocd-development] compiler warnings with dsp5680xx.c

hi i modified the read functions and got rid of the casting warnings. been trying the changes, and everything seems to work ok. the first patch has the changes to get rid of the warnings, and the second patch re-enables the target. salú! On Tue, Jun 28, 2011 at 9:31 AM, Øyvind Harboe wrote: >

Re: [Openocd-development] USB Blaster support broken

On Tue, Jun 28, 2011 at 9:19 AM, Domien Nowicki wrote: > ** > 1. The USB Blaster clone does not use the original FT245 chip, and so it > tries to emulate its behavior. > As it turns out, the API call FT_GetLatencyTimer is not properly emulated > by the clone, and this makes OpenOCD abort. In real

Re: [Openocd-development] OpenOCD 0.5.0-rc1 release

The jimtcl should also be included in the first release. I should be updating in the next day or so. Cheers Spen ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development

Re: [Openocd-development] RFC Release Cycle

On Tue, Jun 28, 2011 at 1:56 PM, Øyvind Harboe wrote: > On Tue, Jun 28, 2011 at 7:30 PM, Jean-Christophe PLAGNIOL-VILLARD > wrote: >> On 19:39 Tue 28 Jun     , Øyvind Harboe wrote: >>> > but now all the maintainer will have their own fork/repository >>> > as done in the kernel >>> >>> Right. And

Re: [Openocd-development] RFC Release Cycle

On 19:15 Tue 28 Jun , Øyvind Harboe wrote: > On Tue, Jun 28, 2011 at 6:58 PM, Jean-Christophe PLAGNIOL-VILLARD > wrote: > > On 19:04 Tue 28 Jun     , Øyvind Harboe wrote: > >> > The best way to do is to choose one git tree as the master git > >> > then each maintainer will have their one git t

Re: [Openocd-development] OpenOCD 0.5.0-rc1 release

On Tue, Jun 28, 2011 at 12:26 PM, Jean-Christophe PLAGNIOL-VILLARD wrote: > Changelog > What is this change against? Some commit on master? Regards, Jie ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/m

Re: [Openocd-development] OpenOCD 0.5.0-rc1 release

Where is the plan? Could you create a mirror at the openocd git mirror? We've done that so far and it makes it easier to find stuff... -- Øyvind Harboe - Can Zylin Consulting help on your project? US toll free 1-866-980-3434 / International +47 51 87 40 27 http://www.zylin.com/

Re: [Openocd-development] RFC Release Cycle

On Tue, Jun 28, 2011 at 7:30 PM, Jean-Christophe PLAGNIOL-VILLARD wrote: > On 19:39 Tue 28 Jun     , Øyvind Harboe wrote: >> > but now all the maintainer will have their own fork/repository >> > as done in the kernel >> >> Right. And you will pull & merge from us and push the result to the >> mast

Re: [Openocd-development] RFC Release Cycle

On 19:39 Tue 28 Jun , Øyvind Harboe wrote: > > but now all the maintainer will have their own fork/repository > > as done in the kernel > > Right. And you will pull & merge from us and push the result to the > master branch? exactly Best Regards, J. ___

Re: [Openocd-development] Jlink support: multiple devices

On 12:02 Tue 28 Jun , Paul Claessen wrote: > Greetings ... > > Question for the J-link developer (Jean-Christophe?), or anyone who > knows the answer: > > Is there a way to hookup and use multiple Segger J-Links devices > with OpenOCD? Yes you can I use it everyday and I implement it in openO

Re: [Openocd-development] RFC Release Cycle

> but now all the maintainer will have their own fork/repository > as done in the kernel Right. And you will pull & merge from us and push the result to the master branch? -- Øyvind Harboe - Can Zylin Consulting help on your project? US toll free 1-866-980-3434 / International +47 51 87 40 27

Re: [Openocd-development] RFC Release Cycle

On 19:04 Tue 28 Jun , Øyvind Harboe wrote: > > The best way to do is to choose one git tree as the master git > > then each maintainer will have their one git tree too > > where they manage it how they want. > > All the maintainers have their own repositories and forks at the git > mirror, but

Re: [Openocd-development] RFC Release Cycle

On Tue, Jun 28, 2011 at 6:58 PM, Jean-Christophe PLAGNIOL-VILLARD wrote: > On 19:04 Tue 28 Jun     , Øyvind Harboe wrote: >> > The best way to do is to choose one git tree as the master git >> > then each maintainer will have their one git tree too >> > where they manage it how they want. >> >> Al

Re: [Openocd-development] RFC Release Cycle

> The best way to do is to choose one git tree as the master git > then each maintainer will have their one git tree too > where they manage it how they want. All the maintainers have their own repositories and forks at the git mirror, but we also have write access to the master repository. -- Ø

Re: [Openocd-development] RFC Release Cycle

On 07:30 Tue 21 Jun , Øyvind Harboe wrote: > 2011/6/21 Jon Povey : > > Øyvind Harboe wrote: > >> I am struggling a bit following the above, but I think we agree: > >> > >> - development goes on in master like it always has done > >> - you create a fork at the openocd mirror and create a > >> re

[Openocd-development] compiler warnings with dsp5680xx.c

dsp5680xx.c generates warnings. Could someone submit a patch to fix this? I'll disable this source file meanwhile. openocd/src/target/dsp5680xx.c: In function 'eonce_rx_upper_data': openocd/src/target/dsp5680xx.c:252: warning: cast increases required alignment of target type openocd/src/target/ds

[Openocd-development] Jlink support: multiple devices

Greetings ... Question for the J-link developer (Jean-Christophe?), or anyone who knows the answer: Is there a way to hookup and use multiple Segger J-Links devices with OpenOCD? With FT2232 devices, for instance, you can specify a serial number to select a certain device, but for J-Link,

Re: [Openocd-development] USB Blaster support broken

On 06/28/2011 09:34 AM, Laurent Gauch wrote: Greetings all, In the past few days I have been trying to get my USB Blaster clone (called "USB Blaster mini") to work with OpenOCD from the latest git tree (762ca59dd5cbe70026234d549bb5f5ac1a05d5b4

Re: [Openocd-development] USB Blaster support broken

On 06/28/2011 09:19 AM, Domien Nowicki wrote: Greetings all, In the past few days I have been trying to get my USB Blaster clone (called "USB Blaster mini") to work with OpenOCD from the latest git tree (762ca59dd5cbe70026234d549bb5f5ac1a05d5b4

Re: [Openocd-development] USB Blaster support broken

Please see if you can get someone to review the changes and when it is ready, resubmit the patch as a git patch. http://repo.or.cz/w/openocd.git/blob/HEAD:/HACKING Thanks! -- Øyvind Harboe - Can Zylin Consulting help on your project? US toll free 1-866-980-3434 / International +47 51 87 40 27

Re: [Openocd-development] Cortex M3: Patch for automatic handling of interrupt mask during stepping

On 24 June 2011 21:27, Peter Horn wrote: > > Am 24.06.2011 21:52, schrieb Spencer Oliver: > >> On Jun 24, 2011 10:32 AM, "Øyvind Harboe" > > wrote: >> > >> > Anyone have any objections against this patch? >> > >> > Did anyone else but Andreas Fritiofson revi

Re: [Openocd-development] Openocd release known issues

On 28/06/2011, at 6:32 PM, Spencer Oliver wrote: > On 27 June 2011 22:33, Steve Bennett wrote: > On 27/06/2011, at 10:07 PM, Spencer Oliver wrote: > >> On 27 June 2011 11:05, Spencer Oliver wrote: >> Thanks that solves all the problems i see with make distcheck. >> At some point i may look into

Re: [Openocd-development] Openocd release known issues

On 28/06/2011, at 6:24 PM, Spencer Oliver wrote: > On 27 June 2011 22:33, Steve Bennett wrote: > On 27/06/2011, at 10:07 PM, Spencer Oliver wrote: > >> On 27 June 2011 11:05, Spencer Oliver wrote: >> Thanks that solves all the problems i see with make distcheck. >> At some point i may look into

Re: [Openocd-development] Status of building using Mingw64?

On 28/06/2011, at 5:14 PM, Xiaofan Chen wrote: > On Tue, Jun 28, 2011 at 2:25 PM, Steve Bennett wrote: >> If you like, you can try the following two patches. >> To do this, you will need to first update jimtcl to the master branch. >> >> I have compile tested this, but I don't have anything to r

Re: [Openocd-development] Openocd release known issues

On 27 June 2011 22:33, Steve Bennett wrote: > On 27/06/2011, at 10:07 PM, Spencer Oliver wrote: > > On 27 June 2011 11:05, Spencer Oliver wrote: > >> Thanks that solves all the problems i see with make distcheck. >> At some point i may look into a method of tweaking so we do not install >> unnec

Re: [Openocd-development] Openocd release known issues

On 27 June 2011 22:33, Steve Bennett wrote: > On 27/06/2011, at 10:07 PM, Spencer Oliver wrote: > > On 27 June 2011 11:05, Spencer Oliver wrote: > >> Thanks that solves all the problems i see with make distcheck. >> At some point i may look into a method of tweaking so we do not install >> unnec

Re: [Openocd-development] Openocd release known issues

> Try latest git. You will need to remove the old autosetup/jimsh0.exe It's a good idea to run 'git clean -f -d -x' prior to running autotools and friends. This will erase all files and directories that aren't under revision control. Regards, Dimitar ___

Re: [Openocd-development] USB Blaster support broken

Greetings all, In the past few days I have been trying to get my USB Blaster clone (called "USB Blaster mini") to work with OpenOCD from the latest git tree (762ca59dd5cbe70026234d549bb5f5ac1a05d5b4

[Openocd-development] USB Blaster support broken

Greetings all, In the past few days I have been trying to get my USB Blaster clone (called "USB Blaster mini") to work with OpenOCD from the latest git tree (762ca59dd5cbe70026234d549bb5f5ac1a05d5b4

Re: [Openocd-development] Status of building using Mingw64?

On Tue, Jun 28, 2011 at 2:25 PM, Steve Bennett wrote: > If you like, you can try the following two patches. > To do this, you will need to first update jimtcl to the master branch. > > I have compile tested this, but I don't have anything to run it on. Just a minor thing. -#ifdef __MINGW32__ -#d