Index: openocd.texi
===================================================================
--- openocd.texi	(revision 1399)
+++ openocd.texi	(working copy)
@@ -3825,8 +3825,43 @@
 at91sam9260.cfg  nslu2.cfg     sam7x256.cfg    wi-9c.cfg
 @end example
 
+@section Config (*.cfg) file naming convention
 
+Here are the basic rules to give consistency to the file names and to organise 
+config files. 
 
+Rule 1: File names may not contain spaces. Use underscores ('_') instead to
+separate words. This avoids having to work out if quotes and what type of quote 
+must be used to specify a file.
+@example
+/target/Atmel_AT91SAM9260.cfg not /target/Atmel AT91SAM9260.cfg
+@end example
+
+Rule 2: The manufacturer name must be prefixed to group files.
+@example
+/board/Atmel_AT91SAM7S-EK.cfg not /board/AT91SAM7S-EK.cfg
+@end example
+
+Rule 3: The name used must be as close as possible to the original name given by 
+the manufacturer, including capitalization.
+@example
+/target/Atmel_AT91SAM7S256.cfg not sam7s256.cfg or at91sam7s256.cfg
+@end example
+
+Rule 4: If a config file covers a range of targets, then the biggest common 
+denominator must be used.
+@example
+/target/Atmel_AT91SAM7S.cfg covers all AT91SAM7Sxxx targets
+@end example
+
+Rule 5: If a config file is for a specific target, not covered by a generic 
+config file, then the full name must be used.
+used.
+@example
+/target/Atmel_AT91SAM7S16.cfg is not covered by /target/Atmel_AT91SAM7S.cfg
+@end example
+
+
 @include fdl.texi
 
 @node OpenOCD Index