Re: [Openocd-development] Creative summary of options for OpenOCDdistros

> -Original Message- > From: openocd-development-boun...@lists.berlios.de [mailto:openocd- > development-boun...@lists.berlios.de] On Behalf Of Freddie Chopin > Sent: woensdag 24 juni 2009 18:28 > To: openocd-development > Subject: [Openocd-development] Creative summary of options for > Op

[Openocd-development] Breakpoints do not work for LM3S6918 /

I also am posting to the SparkFun's list for openOCD http://forum.sparkfun.com/viewtopic.php?t=16068 Best regards, Joe ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-developme

Re: [Openocd-development] Creative summary of options for OpenOCD distros

Ronald Vanschoren pisze: > At least the translation layer should be GPL'd and the binary > part should be publicly available. Just like in linux - the "interface" between OpenOCD and library can clearly be open-source. Zach Welch pisze: > Someone should present a complete design document. ;) Fo

Re: [Openocd-development] Creative summary of options for OpenOCD distros

Ronald Vanschoren pisze: > Bit confused here, what do you mean with "BOTH libraries" When you enable RLink (for example) which uses libusb, the libusb0.dll library HAS TO be present on the system, even if you don't plan to use RLink - that is because the libraries now are loaded unconditionally

[Openocd-development] Carte blanche for MIPS support commits anyone?

Just so you guys know. As the recruiter I'm currently on the lookout for someone I can give carte blanche to on MIPS changes. The carte blanche is the final step before being a regular OpenOCD maintainer w/commit access. -- Øyvind Harboe Embedded software and hardware consulting services http://

Re: [Openocd-development] The OpenOCD Foundation

> Without biasing the community further than this, what would you expect > from such an entity? As a user? Developer? Contributor? Vendor? Founder? I'd like to see an ability to collect money to pay a developer to do more tedious legwork of making more complete and well tested target support or o

Re: [Openocd-development] Advanced Reset Process

On Thu, Jun 25, 2009 at 12:06 AM, David Brownell wrote: > On Wednesday 24 June 2009, Duane Ellis wrote: >> > So maybe you can answer this ... What does the "arp_" prefix in >> > various commands represent? >> > >> > "Address Resolution Protocol" was my first reaction ... but >> > that doesn't seem

Re: [Openocd-development] [patch] Unbreak build for Mac OS X

Oleksandr Tymoshenko wrote: > Attached patch unbreaks build on MacOS X (I guess > on *BSD too): > > - stdlib.h should be included instead of malloc.h for > better portability > - Eliminate "r could be used uninitialized" gcc warning > COMMITED - Thanks. -Duane.

[Openocd-development] [patch] Unbreak build for Mac OS X

Attached patch unbreaks build on MacOS X (I guess on *BSD too): - stdlib.h should be included instead of malloc.h for better portability - Eliminate "r could be used uninitialized" gcc warning -- gonzo Index: src/helper/membuf.c

[Openocd-development] [patch] MIPS/EJTAG watchpoints support

Attached patch adds simple watchpoint support for MIPS32/EJTAG (no value comparation yet). -- gonzo Index: src/target/mips_ejtag.h === --- src/target/mips_ejtag.h (revision 2400) +++ src/target/mips_ejtag.h (working copy) @@ -96,6 +

Re: [Openocd-development] License

Zach Welch a écrit : > Personally, I want to be done with talking about these matters and start > to move on to fix the problems for the community. Sound good? > > Cheers, > > Zach > > Agreed! -- Tired of Microsoft's rebootive multitasking? then it's time to upgrade to Linux. http://home.comc

Re: [Openocd-development] Creative summary of options for OpenOCD distros

On Thu, 2009-06-25 at 00:12 +0200, Ronald Vanschoren wrote: > > This is _very_ apt observation, and one I almost forgot myself. > > > Thanks ;-) > > As (I think) you say here, the Linux kernel module scenario does not > > affect the legality of a loadable module in the same user-space process >

Re: [Openocd-development] The OpenOCD Foundation

+++ Zach Welch [2009-06-24 14:00 -0700]: > On Wed, 2009-06-24 at 09:30 -0700, Zach Welch wrote: > """ > I hereby commit myself to donating all profits recovered in the pursuit > of OpenOCD GPL violations on my behalf to a non-profit. I would prefer > that the community create The OpenOCD Foundatio

Re: [Openocd-development] Creative summary of options for OpenOCD distros

Thanks for pointing out the system32 thing. I forgot about that. I'm an embedded developer, I don't do things like DLL's ;-) Bit confused here, what do you mean with "BOTH libraries" Original Message  Subject: [Openocd-development] Creative summary of options for OpenOCD dis

Re: [Openocd-development] Creative summary of options for OpenOCD distros

Ronald Vanschoren pisze: > Link-kit is definitely better then build-kit, but what are we doing > here? Dynamic linking is also a "link-kit". In my interpretation of GPL, > there is nothing illegal to distributing an OpenOCD binary that _CAN_ > link to FTD2XX but doesn't require it. We (OpenOCD comm

Re: [Openocd-development] Creative summary of options for OpenOCD distros

> This is _very_ apt observation, and one I almost forgot myself. > Thanks ;-) > As (I think) you say here, the Linux kernel module scenario does not > affect the legality of a loadable module in the same user-space process > as OpenOCD. The module still violates the GPL when distributed, sinc

[Openocd-development] Advanced Reset Process

On Wednesday 24 June 2009, Duane Ellis wrote: > > So maybe you can answer this ... What does the "arp_" prefix in > > various commands represent? > > > > "Address Resolution Protocol" was my first reaction ... but > > that doesn't seem relevant to JTAG.  ;) > > That name "arp_" was coined by my se

Re: [Openocd-development] Creative summary of options for OpenOCD distros

Freddie Chopin pisze: > Actually I think that OpenOCD should switch to dynamic library loading, > because the need to have all possible usb libraries when you use Wiggler > and OpenOCD version compiles with support for all possible dongles is > not very convenient. ... OpenOCD version compile_D

Re: [Openocd-development] Creative summary of options for OpenOCD distros

Michael Schwingen pisze: > However, as soon as a combination of OpenOCD + non-GPL plugin module is > distributed as a single package/installer, you might again be in trouble > with the GPL. IANAL, but anyone willing to distribute an installer > package *should* be sure, and that means a proposed so

Re: [Openocd-development] Creative summary of options for OpenOCD distros

Freddie Chopin wrote: > I'm not the first one to suggest such idea (modularity, drivers, ...) on > this list. > Right. And modules in the same address space are tricky license-wise. > >> The drivers would have to run in a separate process space, which means >> > > You are going to check

Re: [Openocd-development] openocd, ftd2xx

Zach Welch wrote: > Hi all, > > Here is the full list of GPL-compliant solutions for libftd2xx GPL > compliance, after further review, consideration, and enumeration: > > 1) Documentation: build it yourself! > 2) Build-Kit: automate the build on users' machines > 3) XXX: to be revealed, if legal >

Re: [Openocd-development] Creative summary of options for OpenOCD distros

Freddie Chopin wrote: > Michael Schwingen pisze: > >> by linking OpenOCD with FTD2XX, you create a >> derived work which can not be distributed under GPL because the library >> is not GPL. >> > > You wouldn't link OpenOCD to anything at all. User would decide what > file he/she would like

Re: [Openocd-development] first ftd2xx fix: documentation!

Main problem with build environment for Windows is that MinGW itself is just a compiler, and MSYS is just a shell. You need like a dozen of different addons for MSYS, and you need to compile them and install them. It's not common knowledge for Windows user what is the system directory on linux.

Re: [Openocd-development] License

David Brownell wrote: > On Wednesday 24 June 2009, Dominic wrote: > >> Being the one who followed the project from >> its very beginning I believe I do know some things that others may have >> missed >> or never heard about. >> > > So maybe you can answer this ... What does the "arp

Re: [Openocd-development] Creative summary of options for OpenOCD distros

Michael Schwingen pisze: > by linking OpenOCD with FTD2XX, you create a > derived work which can not be distributed under GPL because the library > is not GPL. You wouldn't link OpenOCD to anything at all. User would decide what file he/she would like to use, and that file has to provide full ABI

Re: [Openocd-development] Creative summary of options for OpenOCD distros

On Wed, 2009-06-24 at 21:36 +0200, Ronald Vanschoren wrote: > > Note: Linux kernel modules need to be GPL, too - the only way to have > > non-GPL drivers in Linux is to have userspace drivers, which are quite > > limited in capabilities. > > > > This is not correct. GPL v2 talks about "deriv

Re: [Openocd-development] Creative summary of options for OpenOCD distros

Michael Schwingen pisze: > Freddie Chopin wrote: >> 2. Modular OpenOCD which would allow binary "drivers" to be used (just >> as the drivers are used in Linux kernel) > What kind of module interface do you envision that would avoid the > problems which we currently have with the FTD2XX library?

Re: [Openocd-development] proposed FASTDATA bulk write optimizationfor mips_m4k file transfers

The FASTDATA register is part of the EJTAG specification at least back to 3.10 (search for MD00047-2B-EJTAG-SPC-03.10.pdf to see the FASTDATA register). This patch optimizes any calls to target->type->bulk_write_memory() and I have only found the call in target.c. I don't know if flash programming

Re: [Openocd-development] proposed FASTDATA bulk write optimizationfor mips_m4k file transfers

> I'm itching to apply any patches on MIPS4K, but I can't > really dive into MIPS support and provide useful feedback > > Part of my job description in OpenOCD is to be a recruiter > and we're desperately short on active MIPS target experts. > > So if anyone out there have opinions about M

Re: [Openocd-development] [Openocd-svn] r2381 - trunk/src/helper

> > Spencer Oliver wrote: > > strok_r is not available on win32 - strok is said to be > reentrant on win32. > > Not near a dev pc at the moment so i thought i would point > it out - i > > can make the change later if you do not have time. > > > > Hmm... Perhaps we should add "strtok_r()"

Re: [Openocd-development] Creative summary of options for OpenOCD distros

Ronald Vanschoren wrote: >> Note: Linux kernel modules need to be GPL, too - the only way to have >> non-GPL drivers in Linux is to have userspace drivers, which are quite >> limited in capabilities. >> >> > > This is not correct. GPL v2 talks about "derived work". It's well > accepted (b

Re: [Openocd-development] openocd, ftd2xx

Zach Welch wrote: > On Wed, 2009-06-24 at 20:14 +0100, Ian Guffick wrote: >> >>> Here is the full list of GPL-compliant solutions for libftd2xx GPL >>> compliance, after further review, consideration, and enumeration: >>> >>> 1) Documentation: build it yourself! >>> 2) Build-Kit: automate the bui

[Openocd-development] first ftd2xx fix: documentation!

Hello, It remains somewhat unclear to me exactly how badly distributors need to see a solution today, when users (who are all developers, right?) should be able to compile the code themselves and use the FTD2XX driver. If Windows is the blocker, the first question that should be answered is: ho

[Openocd-development] The OpenOCD Foundation

On Wed, 2009-06-24 at 09:30 -0700, Zach Welch wrote: [snip] > To reiterate, I am now no longer willing to accept offers to do the work > that I actually need to survive, to demonstrate that my motives here > have no profit in them anymore. All previous offers for me to do paid > work are now off

Re: [Openocd-development] License

Dominic, Since this followed your very constructive and friendly reply to my summary of the options and willingness to swear off profits, I have tried to interpret your response herein in the best possible light. Likewise, I hope you will grant me the same consideration, just in case it is needed.

[Openocd-development] Question about the driver install structure for libftdi

Hello List, from Freddie I know that a "mix mode" installer is working. Here libftdi is used for the JTAG part of the FT2232 chip, and the FTD2XX driver is used for the COM port of the chip. Now I can confirm that the COM port of the Turtelizer is working. The installation is a little strange,

Re: [Openocd-development] proposed FASTDATA bulk write optimizationfor mips_m4k file transfers

>I'm itching to apply any patches on MIPS4K, but I can't really >dive into MIPS support and provide useful feedback > >Part of my job description in OpenOCD is to be a recruiter >and we're desperately short on active MIPS target >experts. If the PIC32 catches on you should see more MIPS expert

Re: [Openocd-development] License

On Wed, Jun 24, 2009 at 10:30 PM, David Brownell wrote: > On Wednesday 24 June 2009, Dominic wrote: >>       Being the one who followed the project from >> its very beginning I believe I do know some things that others may have >> missed >> or never heard about. > > So maybe you can answer this ..

Re: [Openocd-development] License

On Wednesday 24 June 2009, Dominic wrote: > Being the one who followed the project from > its very beginning I believe I do know some things that others may have > missed > or never heard about. So maybe you can answer this ... What does the "arp_" prefix in various commands represent? "

Re: [Openocd-development] OpenOCD, the GPL, and FTD2XX

Interesting that you should bring up eCos. Look at what happened there. *LOTS* of closed source packages to eCos exists I'd hate to have closed source targets + interface drivers in OpenOCD and if you use the eCos license you'll get that for sure. I know there are hardware vendors who's achin

Re: [Openocd-development] Creative summary of options for OpenOCD distros

> Note: Linux kernel modules need to be GPL, too - the only way to have > non-GPL drivers in Linux is to have userspace drivers, which are quite > limited in capabilities. > This is not correct. GPL v2 talks about "derived work". It's well accepted (by Linus himself and most of the community

Re: [Openocd-development] OpenOCD, the GPL, and FTD2XX

On Jun 24, 2009, at 18:13, Freddie Chopin wrote: > David Brownell pisze: >> [so called "full explanation"] > You are wrong, because I just still don't get it how a > GPL-with-exception can exist. For an example of a GPL+exception license, see the eCos license at

Re: [Openocd-development] openocd, ftd2xx

On Wed, 2009-06-24 at 11:26 -0700, Zach Welch wrote: > > We can raise money to pay for the signing costs; presumably, they don't > need to be signed during development testing. > My IT guys said that in Vista unsigned drivers can be loaded if you enable a boot time option and it only lasts fo

Re: [Openocd-development] openocd, ftd2xx

On Wed, 2009-06-24 at 20:14 +0100, Ian Guffick wrote: > > > Here is the full list of GPL-compliant solutions for libftd2xx GPL > > compliance, after further review, consideration, and enumeration: > > > > 1) Documentation: build it yourself! > > 2) Build-Kit: automate the build on users' machines

Re: [Openocd-development] openocd, ftd2xx

> Here is the full list of GPL-compliant solutions for libftd2xx GPL > compliance, after further review, consideration, and enumeration: > > 1) Documentation: build it yourself! > 2) Build-Kit: automate the build on users' machines > 3) XXX: to be revealed, if legal > 4) libftdi-ftd2xx: ABI comp

Re: [Openocd-development] openocd, ftd2xx

On Wed, 2009-06-24 at 19:20 +0200, Dominic wrote: > Hello Zach, > > > > thank you for this posting. I was just formulating a reply to some of > your last emails, but it's probably better if what I had to say > remains in the privacy of my harddrive. Since you have said that, I am intensely curi

Re: [Openocd-development] proposed FASTDATA bulk write optimization for mips_m4k file transfers

I'm itching to apply any patches on MIPS4K, but I can't really dive into MIPS support and provide useful feedback Part of my job description in OpenOCD is to be a recruiter and we're desperately short on active MIPS target experts. So if anyone out there have opinions about MIPS target code,

[Openocd-development] proposed FASTDATA bulk write optimization for mips_m4k file transfers

Attached is a proposed bulk write optimization for mips_m4k file transfers. The motivation was to speed-up image loading on the mips_m4k target to reach similar transfer times as the xscale target. Files modified: M2399 src/target/mips32.h M2399 src/target/mips_ejtag.c

Re: [Openocd-development] Creative summary of options for OpenOCD distros

Freddie Chopin wrote: > 2. Modular OpenOCD which would allow binary "drivers" to be used (just > as the drivers are used in Linux kernel) > > PRO - possibility to use closed-source drivers (same as above), no need > for running additional software other than OpenOCD, no speed penalty of > the me

Re: [Openocd-development] License

On Wednesday 24 June 2009 19:04:37 Zach Welch wrote: > Are you any of those things, today? Is he contributing, today? > > > Please respect MR. Dominic Rath. He is the CREATOR of OpenOCD 2004 (with > > 1-2 years or more of intensive coding) > > I do want to be clear that I do value and respect his

Re: [Openocd-development] FT2232 & Windows - summary of options

+++ Freddie Chopin [2009-06-24 16:56 +0200]: > David Brownell pisze: > > Under the GPL. From the very first public release, that has been > > part of it. You download it, and the GPL is there. That brings > > along with it certain rules. > > GPL. GPL. GPL... How about Users, Users, Users? Again

Re: [Openocd-development] openocd, ftd2xx

Hello Zach, thank you for this posting. I was just formulating a reply to some of your last emails, but it's probably better if what I had to say remains in the privacy of my harddrive. On Wednesday 24 June 2009 18:30:09 Zach Welch wrote: > Hi all, > > Here is the full list of GPL-compliant sol

Re: [Openocd-development] License

On Wed, 2009-06-24 at 14:27 +0200, Laurent Gauch wrote: > > > > On Wed, 2009-06-24 at 12:20 +0200, Dominic Rath wrote: > > >/ This goes inentionally to you alone, feel free to bring it up on the > > >list if you want... > > />/ > > />/ > You have made me start to wonder if it would be possible to

Re: [Openocd-development] Summer coding project proposal

On Wed, 2009-06-24 at 17:53 +0100, John Devereux wrote: > Zach Welch writes: > > > On Wed, 2009-06-24 at 11:18 +0200, Magnus Lundin wrote: > >> Simple project for a CS student. > >> > >> A wrapper with a libftdi interface calling libftd2xx, as a project using > >> a LGPL license > >> > >> So

Re: [Openocd-development] [patch] openocd.texi - fixes from sam3 update

Committed. Thanks! -- Øyvind Harboe Embedded software and hardware consulting services http://consulting.zylin.com ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development

Re: [Openocd-development] Summer coding project proposal

Zach Welch writes: > On Wed, 2009-06-24 at 11:18 +0200, Magnus Lundin wrote: >> Simple project for a CS student. >> >> A wrapper with a libftdi interface calling libftd2xx, as a project using >> a LGPL license >> >> So any user can take their binary copy of OpenOCD linked against libftdi >>

[Openocd-development] openocd, ftd2xx

Hi all, Here is the full list of GPL-compliant solutions for libftd2xx GPL compliance, after further review, consideration, and enumeration: 1) Documentation: build it yourself! 2) Build-Kit: automate the build on users' machines 3) XXX: to be revealed, if legal 4) libftdi-ftd2xx: ABI compatible

[Openocd-development] Creative summary of options for OpenOCD distros

OK - be creative. End the flames, throw some ideas. Here goes another summary of REALISTIC and ACCEPTABLE options, if ftd2xx.dll will still be "censored" in the distributions. 1. Any kind of network protocol that would talk to "driver". PRO - Possibilities to use JTAGs over internet to debug re

Re: [Openocd-development] Summer coding project proposal

On Wed, 2009-06-24 at 08:34 -0700, Zach Welch wrote: > On Wed, 2009-06-24 at 16:00 +0200, Michael Bruck wrote: > > On Wed, Jun 24, 2009 at 13:29, Zach Welch wrote: > > > On Wed, 2009-06-24 at 12:23 +0200, Michael Bruck wrote: > > >> On Wed, Jun 24, 2009 at 11:42, Zach Welch wrote: > [snip] > > >> T

Re: [Openocd-development] Can we get back to forward progress?

On Wednesday 24 June 2009, Thomas A. Moulton wrote: > ps. let's let the old threads die Good suggestions, all. ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development

Re: [Openocd-development] FT2232 & Windows - summary of options

David Brownell pisze: > "Users" that have only invective to "contribute" aren't > helping the community. You have clearly mistaken me for someone else, so I'll just end this particular thread. 4\/3!! ___ Openocd-development mailing list Openocd-develop

Re: [Openocd-development] OpenOCD, the GPL, and FTD2XX

On Wednesday 24 June 2009, Freddie Chopin wrote: >  > See ... how your first "no explanation" whine was in fact >  > fully addressed at the very beginning of the flamewar you >  > have been feeding. > > Let's not forget who ignited that whole "war". You. Erm, not at all. *YOU* have been the prim

Re: [Openocd-development] OpenOCD license

> Having said this I don't understand how you (or anyone sensible) could support > violating licenses. Do you have the habit of breaking laws for the sake of it? Please show me the exact lines in GPL v2 that _clearly_ say linking FTD2xx with OpenOCD is a violation of the license. If one binar

Re: [Openocd-development] FT2232 & Windows - summary of options

On Wednesday 24 June 2009, Freddie Chopin wrote: > > Notice the complete disregard of technical arguments here. > > > > That's a good sign that the person making the argument has no real > > contribution to make, beyond invective. > > That's probably because I'm a USER, not a contributor. Quite s

Re: [Openocd-development] Summer coding project proposal

On Wed, 2009-06-24 at 16:00 +0200, Michael Bruck wrote: > On Wed, Jun 24, 2009 at 13:29, Zach Welch wrote: > > On Wed, 2009-06-24 at 12:23 +0200, Michael Bruck wrote: > >> On Wed, Jun 24, 2009 at 11:42, Zach Welch wrote: [snip] > >> There is no infringement here, so there is nothing to debate. The

Re: [Openocd-development] FT2232 & Windows - summary of options

On Wed, 2009-06-24 at 16:56 +0200, Freddie Chopin wrote: > GPL. GPL. GPL... How about Users, Users, Users? Again - The Most > Important Qestion - Is OpenOCD meant for users to use, or just to be > "100%-GPL-at-any-cost"? > > > You're the ONLY one advocating a "we-don't-care-for-X" mindset. > >

Re: [Openocd-development] OpenOCD, the GPL, and FTD2XX

David Brownell pisze: > [so called "full explanation"] You are wrong, because I just still don't get it how a GPL-with-exception can exist. If the GPL-chain has to end on the system libs, what is the purpose of having GPL-with-exception? Such code clearly cannot be used in ANY GPL project, beca

Re: [Openocd-development] FT2232 & Windows - summary of options

David Brownell pisze: > Notice the complete disregard of technical arguments here. > > That's a good sign that the person making the argument has no real > contribution to make, beyond invective. That's probably because I'm a USER, not a contributor. Quite simple. > Under the GPL. From the very

Re: [Openocd-development] OpenOCD license

Hello: I'll just participate in this horrible flame once. On Wednesday 24 June 2009 14:02:26 Ronald Vanschoren wrote: > >it sucks to have to be the one to push for license > >compliance like this > > Then don't! I'm just a user of OpenOCD so you have all right to ignore what > I'm saying as

[Openocd-development] [patch] openocd.texi - fixes from sam3 update

Fix formatting bug in at91sam7 doc added with the at91sam3 support; and some formatting issues with sam7 and stm32 keyword params. Tweak at91sam3 docs. Remove ninth nibble from flash bank addresses, clarify "at91sam3 show" variants and that the flash bank layout is not needed as a parameter (unli

Re: [Openocd-development] New Flash Target: Atmel AT91SAM3 - Cortex M3

On Wed, 2009-06-24 at 07:28 -0700, Zach Welch wrote: > On Wed, 2009-06-24 at 09:56 -0400, Duane Ellis wrote: > > David Brownell wrote: > > >> I get all kinds of build errors on Ubuntu 9.04/x86_32 where the > > >> [snip] > > >> .bank[0] = { ... }, > > > > duane> i thought the bank[0] = { ..

Re: [Openocd-development] New Flash Target: Atmel AT91SAM3 - Cortex M3

On Wed, 2009-06-24 at 09:56 -0400, Duane Ellis wrote: > David Brownell wrote: > >> I get all kinds of build errors on Ubuntu 9.04/x86_32 where the > >> [snip] > >> .bank[0] = { ... }, > > duane> i thought the bank[0] = { } was valid C99 initialization. > > zach> I just realized tha

Re: [Openocd-development] New Flash Target: Atmel AT91SAM3 - Cortex M3

On Wednesday 24 June 2009, Duane Ellis wrote: > > I get all kinds of build errors on Ubuntu 9.04/x86_32 where the > > chip details banks get initialized.  The errors made no sense to > > me, and they went away when I changed the > > > >   .bank[0] = { ... }, > >   .bank[1] = { ... }, > > >

Re: [Openocd-development] Summer coding project proposal

> Given that you are in the USA you could probably patent it as a > business method and prevent anyone from using it or collecting money > for it. This should have read: "... or you could collect money for it." ___ Openocd-development mailing list Openoc

Re: [Openocd-development] Summer coding project proposal

On Wed, Jun 24, 2009 at 13:29, Zach Welch wrote: > On Wed, 2009-06-24 at 12:23 +0200, Michael Bruck wrote: >> On Wed, Jun 24, 2009 at 11:42, Zach Welch wrote: >> > On Wed, 2009-06-24 at 11:18 +0200, Magnus Lundin wrote: >> >> Simple project for a CS student. >> >> >> >> A wrapper with a libftdi int

Re: [Openocd-development] New Flash Target: Atmel AT91SAM3 - Cortex M3

David Brownell wrote: >> I get all kinds of build errors on Ubuntu 9.04/x86_32 where the >> [snip] >> .bank[0] = { ... }, duane> i thought the bank[0] = { } was valid C99 initialization. zach> I just realized that I left out the '.bank = ' bits. zach> Sorry for that minor mess, bu

Re: [Openocd-development] New Flash Target: Atmel AT91SAM3 - Cortex M3

On Wed, 2009-06-24 at 09:13 -0400, Duane Ellis wrote: > David Brownell wrote: > > I get all kinds of build errors on Ubuntu 9.04/x86_32 where the > > chip details banks get initialized. The errors made no sense to > > me, and they went away when I changed the > > > > .bank[0] = { ... }, > >

Re: [Openocd-development] New Flash Target: Atmel AT91SAM3 - Cortex M3

On Wed, 2009-06-24 at 09:09 -0400, Duane Ellis wrote: > Zach Welch wrote: > > Fixed. There were a few "could be used uninitialized" warnings too. > > These seem like they should have been covered by --enable-werror. > > > > Duane, are you building with that option before committing changes? > >

Re: [Openocd-development] [Openocd-svn] r2381 - trunk/src/helper

Spencer Oliver wrote: > strok_r is not available on win32 - strok is said to be reentrant on win32. > Not near a dev pc at the moment so i thought i would point it out - i can > make the change later if you do not have time. > Hmm... Perhaps we should add "strtok_r()" to the replacments.c file

Re: [Openocd-development] New Flash Target: Atmel AT91SAM3 - Cortex M3

David Brownell wrote: > I get all kinds of build errors on Ubuntu 9.04/x86_32 where the > chip details banks get initialized. The errors made no sense to > me, and they went away when I changed the > > .bank[0] = { ... }, > .bank[1] = { ... }, > > to be > > .bank = {{ ... }, { ..

Re: [Openocd-development] New Flash Target: Atmel AT91SAM3 - Cortex M3

Zach Welch wrote: > Fixed. There were a few "could be used uninitialized" warnings too. > These seem like they should have been covered by --enable-werror. > > Duane, are you building with that option before committing changes? > I normally build with optimization disabled so that I can *debug

Re: [Openocd-development] License

On Wed, 2009-06-24 at 14:08 +0200, Øyvind Harboe wrote: > Hi Dominic, > > first of all: there is every evidence that the technical problems > that USB are encountering these days will be resolved *LONG* > before any change in license could be effecuated. > > I even believe that USB problems will

[Openocd-development] License

> > On Wed, 2009-06-24 at 12:20 +0200, Dominic Rath wrote: > >/ This goes inentionally to you alone, feel free to bring it up on the list > >if you want... > />/ > />/ > You have made me start to wonder if it would be possible to bring some > />/ > sort of claim of "misrepresentation" against the

Re: [Openocd-development] License

Hi Dominic, first of all: there is every evidence that the technical problems that USB are encountering these days will be resolved *LONG* before any change in license could be effecuated. I even believe that USB problems will be fixed before the community will have finished debating the ramifica

Re: [Openocd-development] OpenOCD license

>it sucks to have to be the one to push for license >compliance like this Then don't! I'm just a user of OpenOCD so you have all right to ignore what I'm saying as you'll find that I'm less important, but it's about time people here start to realize the real "clients" are users and not developer

Re: [Openocd-development] License

On Wed, 2009-06-24 at 12:20 +0200, Dominic Rath wrote: > This goes inentionally to you alone, feel free to bring it up on the list if > you want... > > > You have made me start to wonder if it would be possible to bring some > > sort of claim of "misrepresentation" against the project authors, we

[Openocd-development] Can we get back to forward progress?

As far as I can see there are two solutions being worked on: USB (winusb, libusb) and libftdi and tcpip/Sockets/pipes/ipc Can the person who is heading up each task start a NEW thread and identify who else is working with you and the state of the work. I for one will be willing to test anythi

Re: [Openocd-development] Summer coding project proposal

On Wed, 2009-06-24 at 12:23 +0200, Michael Bruck wrote: > On Wed, Jun 24, 2009 at 11:42, Zach Welch wrote: > > On Wed, 2009-06-24 at 11:18 +0200, Magnus Lundin wrote: > >> Simple project for a CS student. > >> > >> A wrapper with a libftdi interface calling libftd2xx, as a project using > >> a LGPL

[Openocd-development] OpenOCD license

Hi all, In the face of Rick's abrupt departure, I feel that I need to provide more status and summary of the licensing situation. Each copyright holder has the right to "dictate" whether or not they will allow license terms to be changed in their derived works. That is immutable, and I do not fe

Re: [Openocd-development] Summer coding project proposal

Michael Bruck wrote: > If a third party develops a libftdi.dll replacement then there is no > reason a user can not use that replacement. The GPL license that > applies to the user does not restrict at all what he does with the > code or binary as long as he does not distribute binaries of it. > >

Re: [Openocd-development] Summer coding project proposal

On Wed, Jun 24, 2009 at 12:23, Michael Bruck wrote: > On Wed, Jun 24, 2009 at 11:42, Zach Welch wrote: >> On Wed, 2009-06-24 at 11:18 +0200, Magnus Lundin wrote: >>> Simple project for a CS student. >>> >>> A wrapper with a libftdi interface calling libftd2xx, as a project using >>> a LGPL  license

Re: [Openocd-development] Summer coding project proposal

On Wed, Jun 24, 2009 at 11:42, Zach Welch wrote: > On Wed, 2009-06-24 at 11:18 +0200, Magnus Lundin wrote: >> Simple project for a CS student. >> >> A wrapper with a libftdi interface calling libftd2xx, as a project using >> a LGPL  license >> >> So any user can take their binary copy of OpenOCD li

Re: [Openocd-development] Summer coding project proposal

On Wed, Jun 24, 2009 at 11:48, Øyvind Harboe wrote: > On Wed, Jun 24, 2009 at 11:46 AM, Michael Bruck wrote: >> On Wed, Jun 24, 2009 at 11:30, Øyvind Harboe wrote: >>> But why should we go for such an inferior and specif solution when a more >>> general one is proposed and worked on? >> >> What are

Re: [Openocd-development] Summer coding project proposal

On Wed, 2009-06-24 at 11:46 +0200, Michael Bruck wrote: > On Wed, Jun 24, 2009 at 11:30, Øyvind Harboe wrote: > > But why should we go for such an inferior and specif solution when a more > > general one is proposed and worked on? > > What are the speed/roundtrip time implications of passing all d

Re: [Openocd-development] New Flash Target: Atmel AT91SAM3 - Cortex M3

On Wed, 2009-06-24 at 00:21 -0700, David Brownell wrote: > On Tuesday 23 June 2009, Duane Ellis wrote: > > >> Author: duane > > >> Date: 2009-06-24 04:01:14 +0200 (Wed, 24 Jun 2009) > > >> New Revision: 2383 > > I get all kinds of build errors on Ubuntu 9.04/x86_32 where the > chip details banks g

Re: [Openocd-development] Summer coding project proposal

On Wed, Jun 24, 2009 at 11:46 AM, Michael Bruck wrote: > On Wed, Jun 24, 2009 at 11:30, Øyvind Harboe wrote: >> But why should we go for such an inferior and specif solution when a more >> general one is proposed and worked on? > > What are the speed/roundtrip time implications of passing all data

Re: [Openocd-development] Summer coding project proposal

On Wed, Jun 24, 2009 at 11:30, Øyvind Harboe wrote: > But why should we go for such an inferior and specif solution when a more > general one is proposed and worked on? What are the speed/roundtrip time implications of passing all data through the Windows socket interfaces for the TCP/IP solution?

Re: [Openocd-development] Summer coding project proposal

On Wed, 2009-06-24 at 11:18 +0200, Magnus Lundin wrote: > Simple project for a CS student. > > A wrapper with a libftdi interface calling libftd2xx, as a project using > a LGPL license > > So any user can take their binary copy of OpenOCD linked against libftdi > and simply replace the libftd

Re: [Openocd-development] [Openocd-svn] r2381 - trunk/src/helper

> > Added: > >trunk/src/helper/membuf.c > >trunk/src/helper/membuf.h > > Modified: > >trunk/src/helper/Makefile.am > > Log: > > Add a growable sprintf memory buffer library > > > > Modified: trunk/src/helper/Makefile.am > > strok_r is not available on win32 - strok is said to be >

Re: [Openocd-development] Summer coding project proposal

But why should we go for such an inferior and specif solution when a more general one is proposed and worked on? -- Øyvind Harboe Embedded software and hardware consulting services http://consulting.zylin.com ___ Openocd-development mailing list Openo

  1   2   >