Pieter Conradie wrote:
> Hi all,
>
> I have updated the config file naming convention according to all the
> suggestions. Is this better?
>
Yes, thank you for your work.
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https
Pieter Conradie wrote:
> Hi all,
>
> I have updated the config file naming convention according to all the
> suggestions. Is this better?
>
Looks good to me.
cu
Michael
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https:
Hi all,
I have updated the config file naming convention according to all the
suggestions. Is this better?
Regards,
Pieter
Index: openocd.texi
===
--- openocd.texi(revision 1399)
+++ openocd.texi(working copy)
@@ -3
On Mar 5, 2009, at 8:03 PM, Duane Ellis wrote:
Pieter Conradie wrote> [many rules for config names]
+Rule 1: [no spaces, use underlines]
Agreed. I would add *all* non-ascii problematic chars become
underline
too, or are removed.
ie: What about a name like: "O'Conner Chips Are Us"
Techn
Pieter Conradie wrote> [many rules for config names]
> +Rule 1: [no spaces, use underlines]
Agreed. I would add *all* non-ascii problematic chars become underline
too, or are removed.
ie: What about a name like: "O'Conner Chips Are Us"
> +Rule 2: [mfg prefix]
Agreed.
> +Rule 3: The name used mu
On Thu, Mar 5, 2009 at 8:49 PM, Dean Glazeski wrote:
> I agree. Keep the configuration files in all lowercase. It leads to much
> less confusion and less of a likelihood of problems in Linux land due to
> case problems.
Another approach would be if all target config files had a displayname.
T
I agree. Keep the configuration files in all lowercase. It leads to much
less confusion and less of a likelihood of problems in Linux land due to
case problems.
I'm also wondering if the manufacturer of a target controller or board is
necessary at the beginning of the configuration file. After
Laurent Gauch wrote:
> For me it will be better to remove uppercase for any files.
>
Me too!
> /target/atmel_at91sam7s.cfg not /target/Atmel_AT91SAM7S.cfg
> /board/atmel_at91sam7s-ek.cfg not /board/Atmel_AT91SAM7S-EK.cfg
>
> I would like that ALL openocd source files use 'abcdef' but not 'Abc
On Mar 5, 2009, at 6:33 AM, Laurent Gauch wrote:
Hi Øyvind and list members,
I have taken artistic liberty to create the first draft of the
Config file (*.cfg) naming convention. I guess that it is now open
to debate. Over to you...
Best regards,
Pieter
Index: openocd.texi
>
> Hi Øyvind and list members,
>
> I have taken artistic liberty to create the first draft of the Config file
> (*.cfg) naming convention. I guess that it is now open to debate. Over to
> you...
>
> Best regards,
> Pieter
>
> Index: openocd.texi
>
What's a manufacturer? That's not obvious when PCB & CPU differs.
--
Øyvind Harboe
PayBack incident management system
Reduce costs and increase quality, free Starter Edition
http://www.payback.no/index_en.html
___
Openocd-development mailing list
Openo
al Message-
From: oyvindhar...@gmail.com [mailto:oyvindhar...@gmail.com] On Behalf Of
Øyvind Harboe
Sent: 04 March 2009 10:37 AM
To: Pieter Conradie
Cc: openocd-development@lists.berlios.de
Subject: Re: [Openocd-development] Naming convention of *.cfg files
On Wed, Mar 4, 2009 at 9:01 AM, Piete
On Wed, Mar 4, 2009 at 9:01 AM, Pieter Conradie
wrote:
> Hi everyone,
>
>
>
> I have noticed discrepancies in the names of the CFG files, which could
> confuse users of OpenOCD. Example: at91sam9260.cfg vs. sam7x256.cfg
>
>
>
> Maybe we need a naming convention.
Sounds good to me. If you are will
Hi everyone,
I have noticed discrepancies in the names of the CFG files, which could confuse
users of OpenOCD. Example: at91sam9260.cfg vs. sam7x256.cfg
Maybe we need a naming convention. There are a few things that could be
addressed:
1. Capitalization: Should we start to use capitalization t
14 matches
Mail list logo
