Introduce the notion of a 'sample comment'.
- presence of the sample's reported.by file is now mandatory.
- when saving a sample, reporter name & URL are queried, to avoid operator forget about creating the reported.by file.
- when saving a sample, one can store a few-liner comment.
- when recalling a sample, the reporter name, URL and comment (if present) are printed.
- update the powerpc-e500v2-linux-gnuspe sample to include Nate's comment (from his original mail).
- update all samples that were missing the reported.by file.
/trunk/scripts/saveSample.sh | 46 35 11 0 ++++++++++++++++++------
/trunk/scripts/showSamples.sh | 12 6 6 0 +++---
/trunk/samples/powerpc-e500v2-linux-gnuspe/reported.by | 15 15 0 0 ++++++++
/trunk/samples/samples.mk | 22 17 5 0 +++++++++--
4 files changed, 73 insertions(+), 22 deletions(-)
1 # powerpc specific configuration file
4 select ARCH_SUPPORT_ABI
5 select ARCH_SUPPORT_CPU
6 select ARCH_SUPPORT_TUNE
8 The PowerPC architecture, as defined by:
9 http://www.ibm.com/developerworks/eserver/articles/archguide.html
11 config ARCH_POWERPC_SPE
13 prompt "Enable SPE support"
16 Add support for the Signal Processing Engine. This will set up
17 the toolchain so that it supports the SPE ABI extensions. This
18 mainly targets Freescale e500 processors.
20 Setting this option will append "spe" to the end of your target
21 tuple name (e.g., powerpc-e500v2-linux-gnuspe) so that the gcc
22 configure/build system will know to include SPE ABI support.
23 It will also automatically add "-mabi=spe -mspe" to your
24 TARGET_CFLAGS, and "--enable-e500_double" to your CC_EXTRA_CONFIG,
25 so you do not need to explicitly add them.