as
the yellow one with IAR 5.2. (I don't use windows at home)
Michel Catudal
White Pigeon Michigan
--
Tired of Microsoft's rebootive multitasking?
then it's time to upgrade to Linux.
http://home.comcast.net/~mcatudal
diff -rNu openocd-svn-122208/src/target/interface/olimex-jtag-tiny.cfg
openocd-svn
working just as good on windows as
the yellow one with IAR 5.2. (I don't use windows at home)
Michel Catudal
White Pigeon Michigan
--
Tired of Microsoft's rebootive multitasking?
then it's time to upgrade to Linux.
http://home.comcast.net/~mcatudal
diff -rNu openocd-svn-122208/src/target
Dirk Behme a écrit :
Now that I'm able to easily build with libftdi and libftd2xx, I tried
libftd2xx (libftd2xx0.4.16.tar.gz), too.
While libftdi works fine, with libftd2xx I get:
-- cut --
...
Debug: 58 3 ft2232.c:1412 ft2232_init_ftd2xx(): 'ft2232' interface
using FTD2XX with
Dirk Behme a écrit :
Running it as root does the trick. chmod a+s didn't help.
I wonder why open source libftdi is able to do the job, but libftd2xx
needs to do some root stuff.
Anyway, thanks
Dirk
If you want to do chmod a+s openocd you have to do it from root
sudo chmod
I have a few issues with debugging a STM32-SK board (using eclipse with
the latest Zylin plugin)
I have modified the IAR application so it would work with my arm-elf-gcc
compiler. I use the latest SVN code and have no issue yet with
it. My gcc is version 4.4.0 and gdb 6.8. Eclipse is the
If I enter this sequence the interrupts don't work until I cycle the power.
target extended-remote localhost:
mon halt
load
thbreak main
c
If I enter this sequence they do work
target extended-remote localhost:
mon halt
load
mon cortex_m3 maskisr off
thbreak main
c
That is with the
Spencer Oliver a écrit :
If I enter this sequence the interrupts don't work until I
cycle the power.
target extended-remote localhost:
mon halt
load
thbreak main
c
If I enter this sequence they do work
target extended-remote localhost:
mon halt
load
mon cortex_m3 maskisr
Peter LaDow a écrit :
This may not directly be an OpenOCD issue, but I am trying to debug my
design. Since this list is well populated with ARM users, perhaps
somebody has some insight.
I've received the parts and assembled my first LPC2148 based design.
I've also purchased the Olimex
{idProduct}==bcd9, SYSFS{idVendor}==0403, MODE=666,
GROUP=uucp, RUN=/etc/udev/setmode
SYSFS{idProduct}==0401, SYSFS{idVendor}==093c, MODE=666,
GROUP=uucp, RUN=/etc/udev/setmode
SYSFS{idProduct}==9000, SYSFS{idVendor}==138e, MODE=666,
GROUP=uucp, RUN=/etc/udev/setmode
Michel Catudal
--
Tired
Rick Altherr a écrit :
Does anyone
ever get an IAR jlink to work with openocd? If so, please post the
configuration files.
I got it to work but only with the latest yellow ones from IAR. It
doesn't work at all with the slightly older ones that are black.
It has serious issues though, very
Daniel Franzini a écrit :
Hi all
I'm able to build and link openocd with the jlink patch enabled. But
it does not work. I also loaded libusb correctly and openocd indeed
finds out and comunicates with jlink. But it returns a lot of errors
messages about wrong commands and wrong values
James a écrit :
On Wed, 2009-03-04 at 09:41 +0100, Mag. Dr. Nikolaus Klepp wrote:
take this one: http://developers.stf12.net/eclipse-demo
Thanks.
I've never looked at an Eclipse before, probably because people told me
it would be bad for my eyes. They were right.
I'll stick to
After months of hard work I am forced to abandon all work on the OpenOCD
support for the Micronas ARM7TDMI devices.
I had stopped it at one time but later restarted. Micronas was not very
helpfull but they have some nice devices.
They announced last week that following the layoffs and decision of
Rob Brown a écrit :
OK, finally got the Luminary Micro LM3S811 evaluation board going...
wrote 10128 byte from file /home/rfbrown/projects/Luminary/qs_ek-lm3s811.hex
in
9.243969s (1.069954 kb/s)
That's pretty awful! I'm sure it used to be better? Anyway, it's a non-STM32
Cortex part as
Øyvind Harboe a écrit :
Ugh. Can we fix this once and for all? Win32 adds the A, Linux and OS X do
not. Perhaps we should just introduce a global variable in the TCL that
defines the platform type. Similar to __LINUX__, __WIN32__, __DARWIN__ that
gcc emits. Then the problematic devices
Øyvind Harboe a écrit :
I think this change should be committed if it helps some and
hurts noone...
I tried it and found huge improvements. There is still a problem not
related to that one, it always fails to program the first time.
This can't be an STM32 problem since I have never
Jeff Williams a écrit :
If MC1322x standard then good luck getting it to work. Trust me, this
is not a trivial matter. It took me almost a month to figure it out,
and this is after smart, seasoned people had already broken their
picks on it.
But there's no point in debating - the
Gene Smith a écrit :
Spencer Oliver wrote:
This is a bit off topic for this list but thought I would ask
since quite a bit of discussion on programming STM32 is here.
This is in regard to in-application programming (IAP) mentioned in
PM0042 Programming manual. Does this mean that your
Øyvind Harboe a écrit :
resetting first
the jtag, and this rsets my target also, and then a little later
resetting the Cortex core giving two rests in quick succeion. It works
but I dont like it. For my old LM2S811 reset does not work well, but I
have not had time to really dig in to this,
Michael Schwingen a écrit :
Zach Welch wrote:
Sheesh. One religious war per week isn't enough? ;) We made it past
the C vs C++ language war only to be caught up in whitespace wars? :)
Just my thought. We have had this discussions - what, half a year ago?
I do not understand
Michael Bruck a écrit :
On Sun, May 3, 2009 at 10:38 PM, Rick Altherr kc8...@kc8apf.net wrote:
In the next few weeks I would like to prepare a roadmap document for where
I think a project like this one should go. I will make that available to
this group. That will basically be done to
Oleksandr Tymoshenko a écrit :
Hi
I'm trying to use openocd for debugging MIPS target but it seems
that EJTAG support still lacks some features and has some bugs.
I fixed several but it's still work in progress. Attached is the first
(and very small) patch that fixes restoring CPU context
Xiaofan Chen a écrit :
2009/5/5 Michel Catudal michelcatu...@gmail.com:
A project I am working on is to make a programmer for the PIC32 on SuSE
Linux. I am looking into implementing the use of the Programming
Excecutive in OpenOCD.
I have read the documentation from Microchip and it seems
Xiaofan Chen a écrit :
As far as I know, the chip erase is not implemented/working
for flashing the PIC32 according to the mailing list archive. So
it might be barely working. I do not know the status of debugging.
The mips debugger should work with it but you need some way to flash the
David Brownell a écrit :
On Wednesday 20 May 2009, Tiago Maluta wrote:
I'd like to know if OpenOCD support AVR32 (AP7000) processors?
Not yet. I'd partition that work in two parts:
- Nexus [3] framework, which could support more than
just the AVR32 chips.
- AVR32-specific
Xiaofan Chen a écrit :
On Mon, May 25, 2009 at 11:28 AM, Xiaofan Chen xiaof...@gmail.com wrote:
There are many 16/32bit MCUs which will benefit from OpenOCD if
they are supported. Most popular non-ARM ones I can think of are Renesas
M16C/32C, H8/H8S/H8SX, Infineon XC166/XE166, TI MSP430.
Duane Ellis a écrit :
I doubt the V850 would ever be supported by openocd. Reason: Support
for it in GCC is long dead (dormant?), along with support for it in
GDB, those two things have to come first.
-Duane.
The V850E is the latest and the latest GCC is working relatively well
from my
Nicolas Pitre a écrit :
As far as my opinion matters, I don't think that uint32_t is that much
clearer than u32. It is widely assumed that u32 refers to an integer
and not a float, hence having the information carried everywhere is up
only for additional typing and screen realestate.
Rick Altherr a écrit :
Perhaps I'm jaded from writing code for OS X where function names are
intended to be descriptive and thus end up long. Most editors include
autocompletion which makes the difference minimal in practice. Even
when I'm writing code in vi, I prefer the longer type names
Xiaofan Chen a écrit :
2009/5/25 Michel Catudal michelcatu...@gmail.com:
Within theses chips and ColdFire, Infineon XE166 does not seem to have gcc
support.
Incorrect, I have one, do you need it? I could provide some binaries on
my web site if I have space left.
It is about two
Duane Ellis a écrit :
According to an Engineer I talked to, the V850 core is a M4K core
which is the same as the PIC32.
No, it has a different binary instruction set.
Sure has lots of the same types of instructions, however the
instruction set books i have show different opcodes, and
Thomas A. Moulton a écrit :
On Tue, 2009-06-23 at 22:02 +, Photo Leecher wrote:
The exception could be allowed now and then removed later once the
supposed new solutions are done and working.
A Real exception once added can not be removed.
tom
Agreed!
Also, I think that
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.
Thomas A. Moulton a écrit :
On Thu, 2009-06-25 at 17:05 -0300, Alain Mouette wrote:
Building OpenOCD is far more complex then it should be :(
I also had a few problems building on Ubuntu 8.04. I made a detailed
report on the problems, so that they could be improved. Unfortunately I
got
Dominic a écrit :
o the WinUSB backend brings a WHQL signed driver, which is good,
because it
runs on all windows versions that required signed drivers (Vista 64-bit,
Windows 7)
Out of curiosity, do you mean to say that the driver will not load at
all if not signed under vista 64 and Win
Xiaofan Chen a écrit :
2009/6/27 Michel Catudal michelcatu...@gmail.com:
Out of curiosity, do you mean to say that the driver will not load at
all if not signed under vista 64 and Win 7?
This would be a serious reason for me not to let IS change my system
from XP.
I have several very
David Brownell a écrit :
On Friday 26 June 2009, Xiaofan Chen wrote:
On the other hand, it may be easier to create a WinUSB backend for
OpenOCD which covers the needs for OpenOCD (or libftdi) and
OpenOCD (or libftdi) only. You may not need to be a Windows driver
developer to do this.
Dominic a écrit :
load_image /home/vmaster/test.img 0x2000 bin
1048576 byte written at address 0x2000
downloaded 1048576 byte in 4.363197s (204.322 KB/s)
That was the problem I had, I will give another try. With results like
this I would say that I have no more objection.
Flashing
Xiaofan Chen a crit:
On Thu, Jul 23, 2009 at 5:18 AM, Leon
Woestenbergleon.woestenb...@gmail.com wrote:
I received a STM32-comStick today (STM32F107) but the accompanying
documentation (on CD) did not mention a JTAG port.
It has a micro-USB port (not mini, and comes without
Qiang Wang a écrit :
Hello, Oyvind Harboe
Yes, Eclipse is.
But Zylin plug-ins needs more jobs to do.
My work is about the hardware and software, too.
I try to use Zylin to debug my code, with openocd too.
It is good but not enough for job, we have to purchase special ARM Debug ICE.
Best
Øyvind Harboe a écrit :
I adapted the zylin plugin to Linux and it works fine. As is it had serious
issues.
Could you explain what issues you found?
The binaries published years ago don't work unless you use some old 3.2
Eclipse and there are no new binaries published.
The source
Qiang Wang a écrit :
Could you explain what issues you found?
I use the zylin in windows to debug some ARM assembly code and c code.
I use the register table,too. But I found that the register table can
only show 64-bit register value but not 32-bit.
If you have the experience of
Øyvind Harboe a écrit :
We use the Zylin Embedded CDT on linux daily inhouse and I've received
lots of feedback indicating that there are Linux users out there.
It does work on Cygwin too.
On cdt-contrib.sourceforge.net you need to check out embeddedcdt4. The
older embeddedcdt versions are
Øyvind Harboe a écrit :
I'll answer a few more questions here, but really these belong
in the zylin-discuss mailing list.
[stuff deleted w.r.t. warnings, I'll have a peek at the current warnings
at some point]
Not a problem
This one is better than the 4.5 version even though it still
Michael Schwingen a écrit :
Michel Catudal wrote:
ECDT_Debugger_Name = gdb
This is a silly default, but there isn't really a good default here.
I chose arm-elf-gdb.
It is easy to change, I was just mentionning that it looks bad because
Alain Mouette a écrit :
Michel Catudal escreveu:
Freddie Chopin a écrit :
Alain Mouette pisze:
I just have to discover if dgb+OpenOCD works fine, but I was not able to
make it work with CM3 en Eclipse either (it worked fine in ARM 7/9).
Probably I just have to try
I have a small problem with Olimex Jtag Tiny but only with a newer STM32
processor
Here is three situations, the first if the evaluation board with Olimex
Tiny, the second is my keypad with J-Link and the third one
is my keypad with Olimex Tiny. The configuration file is identical for
all
Le 05/10/2009 17:19, Øyvind Harboe a écrit :
So the only thing we need to agree on *now* is to
move git to sourceforge.
I am supportive of the move to sourceforge.
No dissent heard so far on that one.
I also believe there is a consensus that Berlios does
not have the qualities we're
Le 07/10/2009 03:13, Nico Coesel a écrit :
This part of the terms made my alarm bells to turn on:
* No proprietary dependencies: your project
* must work on a completely free operating system. Find free
replacements for your non-free dependencies. Develop and test your Java
Le 08/10/2009 18:13, David Brownell a écrit :
On Thursday 08 October 2009, Jon Smirl wrote:
Can someone help me out and point me to a working cross toolchain for
arm7tdmi with uclibc or equivalent on Linux? I've got a working glib
setup but it keeps linking in 900KB of run-time code.
Le 08/10/2009 19:02, David Brownell a écrit :
On Thursday 08 October 2009, Michel Catudal wrote:
An arm-linux-gcc is only for Linux based system, not bare metal stuff.
Depends what you mean by bare metal.
I use arm-none-linux-gnueabi-gcc all the time to compile
Linux kernels
Le 08/10/2009 19:13, Duane Ellis a écrit :
Take a look at
http://lostarm.sf.net
That is very old stuff
It is easier to download mine or create your own with my source files. I
use the latest 4.4.1 code.
It builds a *COMPLETE* gnu gcc tool chain for ARM7TDMI - bare metal, it
Le 20/10/2009 02:59, Øyvind Harboe a écrit :
On Tue, Oct 20, 2009 at 5:11 AM, Zach Welchz...@superlucidity.net wrote:
On Mon, 2009-10-19 at 19:24 +0200, Øyvind Harboe wrote:
I'd like to see openocd forbidding build == src dir:
Not a good idea.
Why?
Because
David Brownell a crit:
On Friday 13 November 2009, Martn Sebastin Baudino wrote:
But now I'm been asked to look at the code and see if it is possible to
actually embed it on an STR7 board, which we use to automatically test other
boards. Our goal would be (for now) to just flash
Freddie Chopin a écrit :
Why everyone sees only the bad sides of C++ and completely forgets the
good ones? Templates? Stronger compilation-time-error-checks? Easier
error handling? Easier abstraction? Easier polymorphism? Easier - well -
everything?
I will never use C++ in my embedded
Carsten Breuer a écrit :
Hi Guys,
is there any other GDB then insight or the EclipsePlugin under windows?
Best Regards,
Carsten
command line gdb
Insight and Eclipse are just applications using gdb.
You could write your own if you dislike those.
Aside from that there are
Carsten Breuer a écrit :
Debugging was once cool with real emulators, with jtag, bdm or whatever,
it always sucks a bit.
Best Regards,
Carsten
I dislike the emulators. At work I have some projects with a Fujitsu
processor and when I debug I need the $15k emulator
to connect to the
Freddie Chopin a écrit :
On 2009-12-24 23:07, David Brownell wrote:
Curious. Cygwin and Linux builds don't have that particular
issue; I wonder why not?
This may be because official MinGW uses gcc 3.4.5 and that's rather
old... Yesterday I was trying to build a crosscompiler on
David Brownell a écrit :
I'm sure there are a few issues other folk have been carrying
around. Please share!
- Dave
I spent a few hours today checking to see if I could see any issues with
the new code.
I still have a problem with STM32 where the first load doesn't work.
There is also
David Brownell a crit:
On Sunday 10 January 2010, Michel Catudal wrote:
I still have a problem with STM32 where the first load doesn't work.
I don't remember seeing a description of such an issue ... can
you post one, or an URL to a description in the mailing list
David Brownell a crit:
On Monday 11 January 2010, Michel Catudal wrote:
That is correct. As for the watchdog, once you enable it you can no
longer debug as it keep reseting.
Isn't there an STM32-specific register to prevent the watchdog
from counting while the core
Le 02/02/2010 05:35, Igor Skochinsky a écrit :
Hi Spencer,
On Tue, Feb 2, 2010 at 11:18, Spencer Olivers...@spen-soft.co.uk wrote:
I have been given all the info for the ST-LINK from ST.
http://www.st.com/stonline/products/literature/um/15285.pdf
It is accessed using vendor specific
Le 02/02/2010 20:43, Igor Skochinsky a écrit :
So you mean the JTAG connector is for reprogramming the STM32, and not
for connecting other boards? That does make it somewhat less
attractive...
I've looked at the schematics more closely, and it seems the pins we'd
need to connected are
Le 07/02/2010 12:22, Øyvind Harboe a écrit :
I'll be present at IS2T's booth (see below) at Embedded World 2010,
if anyone wants to talk about OpenOCD, or Zylin products/services
for that matter.
Email/phone me if you want to set up a meeting.
I'll write a small report to the mailing list
For those interested I have some RPM for the OpenOCD RC2 on my web site.
I have Mandriva 2010.0 and Fedora 12 RPM files, both source and binaries.
If you want to test openocd with setedit I also have new binaries for
setedit. I haven't updated sourceforge with those yet.
The setedit and turbo
Le 17/02/2010 15:59, CeDeROM a écrit :
Partially - the Primer1 use RLink in JTAG mode, Primer2 use RLink in
SWD mode. I am planning to work on SWD support soon (probably
start/mid march) - I have even downloaded some documentation few days
ago :-)
I have a question on RLink. I have a
Le 17/02/2010 22:18, Xiaofan Chen a écrit :
On Tue, Feb 16, 2010 at 8:10 AM, David Brownelldavi...@pacbell.net wrote:
Then the other stuff will be more focussed specifically on SWD low
level stuff. I figure that'll be the easiest place for other folk
to help out with code ... new
Le 19/02/2010 16:55, CeDeROM a écrit :
Ive just found an interesting STM8Discovery DevelKit with STM8S105C6T6
microcontroller (8-bit, 32 KB Flash, 2 KB RAM, 1 KB EEPROM) onboard
for extremely low price (~$10) with supplied JTAG programmer (Embedded
ST-LINK). Anyone knows/use this St-Link
Le 19/02/2010 18:45, Xiaofan Chen a écrit :
http://www.kamami.pl/index.php?ukey=productproductID=45417
Original Sam-ICE is Atmel OEM version of Segger J-Link. If you
use IAR EWARM, it is locked to Atmel's MCU only. I have no
idea whether this is an official one or a clone.
It
Le 20/02/2010 00:05, simon qian a écrit :
Hi,
I have implemented SWIM interface in Versaloon.
So I know SWIM is NOT SWD, SWIM is more complex.
By modifying the software at the TM8Discovery Devel Kit I meant reflash
the whole thing. The JTAG interface is present on the STM32 board so you
can
simon qian a écrit :
Hi,
As I know, ST-Link supports JTAG for STM32 and SWIM for STM8, but it
doesn't support SWD.
If you want to reflash STM32 of ST-Link to be supported by OpenOCD,
you can try Versaloon driver, but you will lost ST-Link's functionality.
The version on the STM8Discovery
Le 21/04/2010 00:55, Xiaofan Chen a écrit :
On Wed, Apr 21, 2010 at 11:28 AM, Jon Povey jon.po...@racelogic.co.uk wrote:
Note: I am running OpenOCD on Linux inside VirtualBox hosted on Windows,
using VirtualBox's USB capture features.
If this is of interest to anyone please let me know
Le 21/04/2010 21:07, Xiaofan Chen a écrit :
2010/4/22 Michel Catudal michelcatu...@gmail.com:
Too many unknowns. OpenOCD can work under Windows. And I am
sure VirtualBox's USB implementation is not the best (the same
for VMware, all of the USB implementation seems to be
problematic
On 16/08/2010 12:44, David Brownell wrote:
I have no license to use JTAGICE mkII protocol.
Irrelevant. AVR32 uses the Nexus protocols,
layered on top of JTAG. Those are public and
need no licensing.
For devices where you need most of the pins Nexus can't be used. Nexus
has
On 16/08/2010 21:54, David Brownell wrote:
--- On Mon, 8/16/10, Michel Catudalmichelcatu...@gmail.com wrote:
Irrelevant. AVR32 uses the Nexus protocols,
layered on top of JTAG. Those are public and
need no licensing.
For devices where you need most of the pins Nexus can't be
On 31/08/2010 11:18, simon qian wrote:
My AVR32 debugger/programmer will be released next week.
I'll get some sample(UC3B0256) from Atmel this week.
I think I can do the test after next week.
Are you planning to support the UC3C series as well?
They are +5V devices and not +3.3V devices
Le 2010-10-19 03:24, Peter Stuge a écrit :
Yes, moving that to a PC makes for cheaper solutions, but performance
and all sorts of hell will follow. And really, how much cheaper than
a $6 USB Cortex-M3 microcontroller running at 72MHz does JTAG need?
A $3.76 48 pins AVR32.
--
Tired of
Le 2010-10-29 19:15, Andreas Fritiofson a écrit :
On Fri, Oct 29, 2010 at 8:58 PM, Chris Jonesch...@martin-jones.com wrote:
Am I stuck? Or is there a way of finding out how the Cortex-M3 debug unit is
wedged, if that's the case, and tickling it back to life?
Would it reset
wiped out, code common
between the ADC DMA and RAM area used by the IAR reflashing program.
After I enabled the reset core everything worked fine. I use the
bootloader to reflash code in the field connecting on the OBD or other
diagnostic port.
I use J-Link.
Michel Catudal
--
Tired
Le 2010-11-04 17:10, Andreas Fritiofson a écrit :
2010/10/31 Michel Catudalmichelcatu...@gmail.com:
Le 2010-10-29 19:15, Andreas Fritiofson a écrit :
One can also ponder why you need debug access to something molded in
plastic... Wouldn't it be better to debug your application on a
Le 2011-03-29 19:06, Xiaofan Chen a écrit :
On Tue, Mar 29, 2011 at 9:46 PM, Drasko DRASKOVIC
drasko.drasko...@gmail.com wrote:
Ah... sorry, I did not take care - it is v.1.0 you are talking about.
I constantly thought about 0.18, thinking that it was the last
version.
Indeed, when I looked
Le 2011-04-10 09:26, Damjan Marion a écrit :
It is Mac OS X. It is linked against:
libusb @1.0.8_0 (active)
libusb-compat @0.1.3_0 (active)
BTW Seems that my j-link died right now. It doesn't power up and I can see
USB stall in dmesg.
Wonder if there is a way to reflash it.
Le 2011-07-11 02:28, Jean-Christophe PLAGNIOL-VILLARD a écrit :
On 19:43 Sun 10 Jul , li...@neuronenwerk.de wrote:
On Sun, 10 14:38 , Jean-Christophe PLAGNIOL-VILLARD wrote:
On 09:30 Sun 10 Jul , Xiaofan Chen wrote:
I try to get in Contact with them already hope they will reply soon
Le 23/08/2011 03:47, Evan Hunter a écrit :
The way it has been designed means that no memory locations are touched until
symbol locations are provided by GDB. The symbols names which are available
tell the system which RTOS is in use.
On most platforms OpenOCD would have initialised the
Le 25/08/2011 15:18, Jie Zhang a écrit :
Hi,
There are a lot of coding style mismatch in the current OpenOCD code.
I'd like suggest setting a rule that asks fixing all coding style
issues before a patch is merged.
And there are still something missing on
Le 29/08/2011 12:28, Eric Wetzel a écrit :
For the record, here are the relevant standards:
GNU: http://www.gnu.org/prep/standards/standards.html#Writing-C
Kernighan Ritchie:
http://en.wikipedia.org/wiki/Indent_style#K.26R_style (sorry, didn't
try very hard on this one)
Linux:
Le 29/08/2011 20:03, mike a écrit :
I strongly disagree on using anything that resembles KR.
Where I work you could get reprimanded and maybe even fired if you did
use it.
So are you saying that
if (x == y) {
x++;
} else {
x--;
}
is a serious offence where you work? If it is,
Le 01/10/2011 10:34, Peter Stuge a écrit :
I am personally very strongly against depending on companies based in
the US for open source project infrastructure. I find there are quite
significant drawbacks, due to stupid US law and/or due to the service
being provided by a business with a clear
88 matches
Mail list logo
