-development] Moving to git
From: Øyvind Harboe
To: Ronald Vanschoren
Cc: openocd-development@lists.berlios.de
Date: Tue Oct 06 2009 08:24:34 GMT+0200 (Romance Standard Time)
On Tue, Oct 6, 2009 at 8:23 AM, Ronald Vanschoren wrote:
!!! And if anyone objects to GI
>!!! And if anyone objects to GIT, please speak up ASAP !!!
Why are we moving to GIT anyway? What was wrong with SVN?
gr.
Ronald
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd
> Nobody has yet posted a license to this list that would make it
> possible to consider a scenario where it OpenOCD would only
> allow honorable linking with closed source that could not be
> exploited in some insidious way by a commercially orientated
> villain
Lots of people have, even you, it'
Original Message
Subject: [Openocd-development] Dynamic library loading
From: Øyvind Harboe
To: Ronald Vanschoren
Cc: openocd-development
Date: Sun Jun 28 2009 20:39:05 GMT+0200 (Romance Standard Time)
> (Lots of stuff deleted from your mail. Nothing is intended
> b
Original Message
Subject: [Openocd-development] Dynamic library loading
From: Øyvind Harboe
To: Harald Kipp
Cc: openocd-development
Date: Sun Jun 28 2009 19:59:55 GMT+0200 (Romance Standard Time)
On Fri, Jun 26, 2009 at 6:49 PM, Harald Kipp wrote:
Freddie Chop
09 20:16:41 GMT+0200 (Romance Standard Time)
Ronald Vanschoren pisze:
Did you actually try it? There is no redefinition normally (depends on
how the .h file of ftd2xx is made) and I think I used this approach
before (although slightly different). Guess it's a 2 minute check for
yo
1) Why do you initialize the FT_Close_ptr and FT_Purge_ptr in a
different place then all the others? Isn't it cleaner to keep all the
initializations together?
As a trV embedded engineer I've saved some memory [; Keeping all
together would be clearer, but I decided to min
Freddie,
Thanks for this patch, I like the idea :-)
I don't have any experience in OpenOCD development but I did have a
look at the patch and have two questions/remarks:
1) Why do you initialize the FT_Close_ptr and FT_Purge_ptr in a
different place then all the others? Isn't it cleaner to k
I know this wasn't addressed to me, but the advice I gave (about binary
Linux Kernel Modules) was cross-checked with the legal department of
that company, the legal department of the client AND with FSF, so don't
think you alone are right because you hired a lawyer.
Any lawyer will say "stay aw
Original Message
Subject: [Openocd-development] ftd2xx -> libftdi
From: Xiaofan Chen
To: Ronald Vanschoren
Cc: openocd-development
Date: Fri Jun 26 2009 18:30:22 GMT+0200 (Romance Standard Time)
On Sat, Jun 27, 2009 at 12:19 AM, Ronald
Vanschoren wrote:
I
Original Message
Subject: [Openocd-development] ftd2xx -> libftdi
From: Xiaofan Chen
To: Freddie Chopin
Cc: openocd-development
Date: Fri Jun 26 2009 17:54:25 GMT+0200 (Romance Standard Time)
> On Fri, Jun 26, 2009 at 11:49 PM, Freddie Chopin wrote:
>
>> Ro
Original Message
Subject: [Openocd-development] ftd2xx -> libftdi
From: Xiaofan Chen
To: open...@duaneellis.com
Cc: openocd-development
Date: Fri Jun 26 2009 17:27:36 GMT+0200 (Romance Standard Time)
On Fri, Jun 26, 2009 at 11:15 PM, Duane Ellis wrote:
Zach Wel
ry of options for OpenOCD
distros
From: Freddie Chopin
To: openocd-development
Date: Thu Jun 25 2009 00:20:53 GMT+0200 (Romance Standard Time)
Ronald Vanschoren pisze:
Link-kit is definitely better then build-kit, but what are we doing
here? Dynamic linking is also a "link-kit
> 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
> 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
get lost over the years
because nobody actively maintains/tests it as it's not an official
feature.
gr.
Ronald
Original Message
Subject: [Openocd-development] OpenOCD license
From: Raúl Sánchez Siles
To: openocd-development@lists.berlios.de
Date: Wed Jun 24 2009 16:55:32 GMT+0200
>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
I haven't read all 700 emails related to this issue, but can someone please
explain to me why this statement holds?
> - Binaries linking to FTD2XX may NOT be distributed.
Where can I find the FTD2XX license?
Thanks,
Ronald
Original Message
Subject: [Openocd-development] Op
Dear,
I've purchased a Primer2 device (http://www.stm32circle.com/) but not
before finding out that it only supports Serial Wire Debug (SWD) and not
"normal" JTAG.
After some browsing around, it seems OpenOCD doesn't support SWD (yet).
I did find the following quote:
>SWD is definitely a post-1.0
hread support to a gdb stub?
I've looked into the gdbserver code that gives quite a few good
pointers, but any help is welcome.
Thanks,
Ronald Vanschoren
www.lieron.be
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
http
20 matches
Mail list logo
