Index: openocd.texi
===================================================================
--- openocd.texi	(revision 1399)
+++ openocd.texi	(working copy)
@@ -3825,8 +3825,51 @@
 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 group 
+config files. 
 
+Rule 1: The file name must be in lower case (no capitalisation).
+@example
+/target/samsung_s3c2410.cfg not Samsung_S3C2410.cfg
+@end example
+
+Rule 2: The file name may not contain spaces. Use underscores ('_') instead to
+separate words. *All* non-ascii problematic chars must be replaced by 
+underscores ('_') or removed. 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 3: The file name used must be as close as possible to the original name 
+given by the manufacturer.
+@example
+/target/atmel_at91sam7s256.cfg not /target/atmel_sam7s256.cfg
+/board/atmel_at91sam7s-ek.cfg not /board/atmel_sam7s_ek.cfg
+@end example
+
+Rule 4: For target files the CPU manufacturer name must be prefixed. For boards,
+the board manufacturer name must be used.
+@example
+/target/nxp_lpc2129.cfg not /target/lpc219.cfg
+/board/olimex_sam9_l9260.cfg not /target/sam9_l9260.cfg
+@end example
+
+Rule 5: If a config file covers a range of targets, then the biggest common 
+denominator name must be used.
+@example
+/target/atmel_at91sam7s.cfg covers all AT91SAM7Sxxx targets
+@end example
+
+Rule 6: If a config file is for a specific target, not covered by a generic 
+config file, then the full name must be used.
+@example
+/target/atmel_at91sam7s16.cfg is not covered by /target/atmel_at91sam7s.cfg
+@end example
+
+
 @include fdl.texi
 
 @node OpenOCD Index