Minor fixes to Developer Manual pages.
- Fix cosmetic bug on main page
- Add missing JTAG list item.
---
main.txt |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
Minor fixes to Developer Manual pages.
- Fix cosmetic bug on main page
- Add missing JTAG list item.
---
main.txt |3 ++-
Add missing copyright header to target_type.h.
---
target_type.h | 25 +
1 file changed, 25 insertions(+)
Add missing copyright header to target_type.h.
---
target_type.h | 25 +
1 file changed, 25 insertions(+)
==
only in patch2:
unchanged:
Add missing copyright header and fix @page direction in membuf.h.
---
membuf.h | 24 +---
1 file changed, 21 insertions(+), 3 deletions(-)
Add missing copyright header and fix @page direction in membuf.h.
---
membuf.h | 24 +---
1 file changed, 21 inser
Update TODO list to relect 0.2.0 release.
---
TODO | 71 ---
1 file changed, 34 insertions(+), 37 deletions(-)
Update TODO list to relect 0.2.0 release.
---
TODO | 71 --
Add comments to README about compiler and library dependencies.
---
README | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
Add comments to README about compiler and library dependencies.
---
README | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
==
on
This series contains a few minor improvements for the 0.2.0 release.
1/5 Add comments to README about compiler and library dependencies.
2/5 Update TODO list to relect 0.2.0 release.
3/5 Add missing copyright header and fix @page direction in membuf.h.
4/5 Add missing copyright hea
On Tue, 2009-06-30 at 21:50 -0400, Duane Ellis wrote:
> Zach> However, I would rather see you move some of the things in the C file
> Zach> into the H file (all of the #defines and struct declarations, to
> start).
> Zach> Basically, use it as the driver's private header file.
>
> duane> None of
Zach> However, I would rather see you move some of the things in the C file
Zach> into the H file (all of the #defines and struct declarations, to
start).
Zach> Basically, use it as the driver's private header file.
duane> None of those defines are *PUBLIC*.
duane> None of those structures are *P
On Tue, 2009-06-30 at 21:20 -0400, Duane Ellis wrote:
> > However, I would rather see you move some of the things in the C file
> > into the H file (all of the #defines and struct declarations, to start).
> > Basically, use it as the driver's private header file.
> >
>
> None of those defines a
> However, I would rather see you move some of the things in the C file
> into the H file (all of the #defines and struct declarations, to start).
> Basically, use it as the driver's private header file.
>
None of those defines are *PUBLIC*.
None of those structures are *PUBLIC*.
The public i
On Tue, 2009-06-30 at 20:42 -0400, Duane Ellis wrote:
> zwe...@mail.berlios.de wrote:
> > Author: zwelch
> > Date: 2009-07-01 00:25:09 +0200 (Wed, 01 Jul 2009)
> > New Revision: 2438
> >
> > Modified:
> >trunk/src/flash/flash.c
> > Log:
> > Remove at91sam3.h from flash.c; use extern like other
zwe...@mail.berlios.de wrote:
> Author: zwelch
> Date: 2009-07-01 00:25:09 +0200 (Wed, 01 Jul 2009)
> New Revision: 2438
>
> Modified:
>trunk/src/flash/flash.c
> Log:
> Remove at91sam3.h from flash.c; use extern like other drivers.
>
>
If you are doing this then you should remove the file "
>
> Having looked at the same code to fix (what I presume are)
> the same "may be used uninitialized" warnings, I am curious
> how you managed to trigger these warnings? I have to wonder
> if you're using an older version of gcc or a different set of
> optimizations.
>
> --Z
>
You are cor
Having looked at the same code to fix (what I presume are) the same "may
be used uninitialized" warnings, I am curious how you managed to trigger
these warnings? I have to wonder if you're using an older version of
gcc or a different set of optimizations.
--Z
On Tue, 2009-06-30 at 23:13 +0200, n
On Tue, 2009-06-30 at 09:54 -0700, David Brownell wrote:
> > does the community know of any reason to hold this countdown?
>
> Oh, and I'd still like to see the at91sam3 config files
> become non-executable. :)
Thanks for noticing this. I believe that all of the files under tcl/
should now have
On Tue, 2009-06-30 at 13:08 -0700, Joseph Kuss wrote:
> Zach,
>
> I am starting to build openOCD revision 2431 on my windows vista
> laptop.
> I am following the instructions at:
>
> http://forum.sparkfun.com/viewtopic.php?t=11221
>
>
> I got the latest "free as in beer" version of the FTDI
On Tue, 2009-06-30 at 20:09 +0300, Yusuf Caglar AKYUZ wrote:
> David Brownell wrote:
> >> does the community know of any reason to hold this countdown?
> >
> > Oh, and I'd still like to see the at91sam3 config files
> > become non-executable. :)
> >
>
> You make me think that next release will
Try deleting c:\cygwin and reinstalling Cygwin.
You should budget (time) to wipe the entire cygwin directory
every so often. It helped me with a build problem today
My laptop at home just segfaults willy nilly when using Cygwin
(even after wiping c:\cygwin), so my experience is that stars mus
On Tue, Jun 30, 2009 at 6:54 PM, David Brownell wrote:
>> does the community know of any reason to hold this countdown?
>
> Oh, and I'd still like to see the at91sam3 config files
> become non-executable. :)
What was this again?
--
Øyvind Harboe
Embedded software and hardware consulting service
David Brownell wrote:
>> does the community know of any reason to hold this countdown?
>
> Oh, and I'd still like to see the at91sam3 config files
> become non-executable. :)
>
You make me think that next release will be in very far future :)
I guess I have skipped the mentioning of this but c
> does the community know of any reason to hold this countdown?
Oh, and I'd still like to see the at91sam3 config files
become non-executable. :)
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman
Kevin Bortis pisze:
> Could you please explain me how you calculated the work-area-size
> value of 20k for the stm32? I have searched in the docu and on the
> internet, but the only thing I got about the work-area-size was, that
> the flash code for the stm32 uses about 48byte. What is the rest use
On Tuesday 30 June 2009, Zach Welch wrote:
> does the community know of any reason to hold this countdown?
No, but I'd like to send in one patch updating target/davinci.cfg
PLL handling. I noticed one minor buglet affecting current code
and have some new bits (all Tcl code) I'd like to get in now
Thank you for correcting me.
Could you please explain me how you calculated the work-area-size
value of 20k for the stm32? I have searched in the docu and on the
internet, but the only thing I got about the work-area-size was, that
the flash code for the stm32 uses about 48byte. What is the rest u
Committed.
Thanks!
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
"Řyvind Harboe" napisał(a):
> Can you do one better and submit a correct patch?
The mechanism itself is fine, so I just fixed the descriptions and numbers. And
some other minor things by the way.
4\/3!!
work-area-fix.patch
Description: Binary data
Do you have a link to the definitive version? (I didn't follow
this discussion)
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://l
> -Original Message-
> From: openocd-development-boun...@lists.berlios.de [mailto:openocd-
> development-boun...@lists.berlios.de] On Behalf Of Zach Welch
> Sent: dinsdag 30 juni 2009 12:13
> To: openocd-development
> Subject: [Openocd-development] Final Fixes for 0.2.0?
>
> Hi all,
>
> W
On Tue, Jun 30, 2009 at 1:03 PM, wrote:
> Revert patch for r2419, as it is wrong. Work-area is the size of used RAM,
> not flash.
Can you do one better and submit a correct patch?
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
Revert patch for r2419, as it is wrong. Work-area is the size of used RAM, not
flash.
4\/3!!
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
2009/6/30 Raúl Sánchez Siles :
> On Tuesday 30 June 2009 03:51:43 Zach Welch wrote:
>> On Mon, 2009-06-29 at 18:32 -0700, David Brownell wrote:
>> > On Monday 29 June 2009, Zach Welch wrote:
>
>> Attached is a new patch that can be substituted for the original #6 in
>> the series.
>>
>> Cheers,
>>
On Tuesday 30 June 2009 03:51:43 Zach Welch wrote:
> On Mon, 2009-06-29 at 18:32 -0700, David Brownell wrote:
> > On Monday 29 June 2009, Zach Welch wrote:
> Attached is a new patch that can be substituted for the original #6 in
> the series.
>
> Cheers,
>
> Zach
Don't you think asking for trun
Hi all,
We have reached the scheduled release window. Are we ready to jump
through it, or do obstacles remain in our path? I would like to release
the 0.2.0 archives on the project files section of the berliOS site, so
packagers may begin to integrate these into their distributions.
As of this
On Tue, 2009-06-30 at 10:56 +0200, Marcel Jost wrote:
> Hi
>
> This is a patch to add Luminary Micro LM3S9B90 and LM3S9B92 Evaluation
> Kit support. These kits include a new ft2232 adapter, the Luminary
> In-Circuit Debug Interface (ICDI) Board. So i added this as a new ft2232
> layout, called
Hi
This is a patch to add Luminary Micro LM3S9B90 and LM3S9B92 Evaluation
Kit support. These kits include a new ft2232 adapter, the Luminary
In-Circuit Debug Interface (ICDI) Board. So i added this as a new ft2232
layout, called "luminary_icdi".
The topic is discussed here:
https://lists.be
Switch automake handling to use --gnu mode, not --foreign.
Remove INSTALL file; automake generates a copy of the latest version.
---
Makefile.am |5 +++--
bootstrap |2 +-
2 files changed, 4 insertions(+), 3 deletions(-)
Switch automake handling to use --gnu mode, not --foreign.
Remove I
Provide some useful information in README file, rather than punting.
Add some text to introduce the project to new users.
Move packaging, configuration, and compilation of OpenOCD out of
the User's Guide and into README, where it can be used by users
before configuring and compiling the documentat
The first patch in this series puts content into the README files,
removing the "Building OpenOCD" chapter from the Users's Guide. I went
ahead and "improved" the content in the process, so please be sure to
review for consistency, clarity, or the lack thereof.
The second patch allows automake to
38 matches
Mail list logo
