On Wed, Mar 4, 2009 at 9:01 AM, Pieter Conradie <pieter.conra...@psitek.com> 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 willing to step up to the plate and submit a patch to the openocd documentation which defines the naming convention that could be a good start? > 1. Capitalization: Should we start to use capitalization to reflect the > actual name that manufacturers use? Example: AT91SAM9260.cfg vs. > at91sam9260.cfg makes sense to me. Proper capitalisation/naming can make this look prettier. I'm also in favour of using spaces in the names if hat helps it make more human readable. > 2. Manufacturer name prefixed to files to group them, e.g. > /target/Atmel_AT91SAM9260.cfg or /target/Atmel/AT91SAM9260.cfg. See > samsung_s3c2410.cfg. The same should apply to the board directory, e.g. > /board/Atmel_AT91SAM9260-EK.cfg or /board/Atmel/AT91SAM9260-EK.cfg I'm not sure how well this will work or how obvious it will be. What about a PCB with an FPGA from A and a MCU from B produced by C? - Ø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 Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
