Skip to contentSkip to conversation

mach-at91: Support for gsia18s board added

PATCH In review Igor Plyatov 3 participants 9 messages Dec 10, 2010 – Dec 13, 2010

Subsystems (3)
lore
Share & tools
lore
#0 lore raw

PATCH v4 1/1 mach-at91: Support for gsia18s board added

The GS_IA18_S (GMS) is a carrier board from GeoSIG Ltd used with the Stamp9G20 SoM from Taskit company.
It operate as an internet accelerometer.

---
 arch/arm/configs/gsia18s_defconfig        |  147 +++++++
 arch/arm/mach-at91/Kconfig                |    7 +
 arch/arm/mach-at91/Makefile               |    1 +
 arch/arm/mach-at91/board-gsia18s.c        |  587 +++++++++++++++++++++++++++++
 arch/arm/mach-at91/include/mach/gsia18s.h |   33 ++
 5 files changed, 775 insertions(+), 0 deletions(-)
 create mode 100644 arch/arm/configs/gsia18s_defconfig
 create mode 100644 arch/arm/mach-at91/board-gsia18s.c
 create mode 100644 arch/arm/mach-at91/include/mach/gsia18s.h
arch/arm/configs/gsia18s_defconfig new file +147 -0
new file mode 100644
index 0000000..d7cef32
@@ -0,0 +1,147 @@
+CONFIG_EXPERIMENTAL=y
+CONFIG_SYSVIPC=y
+CONFIG_LOG_BUF_SHIFT=14
+CONFIG_BLK_DEV_INITRD=y
+CONFIG_SLAB=y
+CONFIG_MODULES=y
+CONFIG_MODULE_UNLOAD=y
+CONFIG_ARCH_AT91=y
+CONFIG_ARCH_AT91SAM9G20=y
+CONFIG_MACH_GSIA18S=y
+CONFIG_AT91_PROGRAMMABLE_CLOCKS=y
+CONFIG_AT91_SLOW_CLOCK=y
+CONFIG_NO_HZ=y
+CONFIG_HIGH_RES_TIMERS=y
+CONFIG_PREEMPT=y
+CONFIG_AEABI=y
+CONFIG_ZBOOT_ROM_TEXT=0x0
+CONFIG_ZBOOT_ROM_BSS=0x0
+CONFIG_CMDLINE="mem=64M console=ttyS0,115200 initrd=0x21100000,3145728 root=/dev/ram0 rw"
+CONFIG_KEXEC=y
+CONFIG_CPU_IDLE=y
+CONFIG_PM=y
+CONFIG_NET=y
+CONFIG_PACKET=y
+CONFIG_UNIX=y
+CONFIG_INET=y
+CONFIG_NETFILTER=y
+CONFIG_NETFILTER_NETLINK_LOG=m
+CONFIG_NF_CONNTRACK=m
+CONFIG_NF_CT_PROTO_SCTP=m
+CONFIG_NF_CT_PROTO_UDPLITE=m
+CONFIG_NF_CONNTRACK_FTP=m
+CONFIG_NF_CONNTRACK_IRC=m
+CONFIG_NF_CONNTRACK_SIP=m
+CONFIG_NF_CT_NETLINK=m
+CONFIG_NETFILTER_XT_MARK=m
+CONFIG_NETFILTER_XT_CONNMARK=m
+CONFIG_NETFILTER_XT_MATCH_STATE=m
+CONFIG_NF_CONNTRACK_IPV4=m
+CONFIG_IP_NF_IPTABLES=m
+CONFIG_IP_NF_MATCH_ADDRTYPE=m
+CONFIG_IP_NF_MATCH_AH=m
+CONFIG_IP_NF_MATCH_ECN=m
+CONFIG_IP_NF_MATCH_TTL=m
+CONFIG_IP_NF_FILTER=m
+CONFIG_IP_NF_TARGET_REJECT=m
+CONFIG_IP_NF_TARGET_LOG=m
+CONFIG_IP_NF_TARGET_ULOG=m
+CONFIG_NF_NAT=m
+CONFIG_IP_NF_TARGET_MASQUERADE=m
+CONFIG_IP_NF_TARGET_NETMAP=m
+CONFIG_IP_NF_TARGET_REDIRECT=m
+CONFIG_NF_NAT_SNMP_BASIC=m
+CONFIG_IP_NF_MANGLE=m
+CONFIG_IP_NF_TARGET_CLUSTERIP=m
+CONFIG_IP_NF_TARGET_ECN=m
+CONFIG_IP_NF_TARGET_TTL=m
+CONFIG_IP_NF_RAW=m
+CONFIG_IP_NF_ARPTABLES=m
+CONFIG_IP_NF_ARPFILTER=m
+CONFIG_IP_NF_ARP_MANGLE=m
+CONFIG_CFG80211=y
+CONFIG_LIB80211=y
+CONFIG_MAC80211=y
+CONFIG_MAC80211_LEDS=y
+CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
+CONFIG_MTD=y
+CONFIG_MTD_CONCAT=y
+CONFIG_MTD_PARTITIONS=y
+CONFIG_MTD_CMDLINE_PARTS=y
+CONFIG_MTD_CHAR=y
+CONFIG_MTD_BLOCK=y
+CONFIG_MTD_DATAFLASH=y
+CONFIG_MTD_NAND=y
+CONFIG_MTD_NAND_ATMEL=y
+CONFIG_MTD_UBI=y
+CONFIG_BLK_DEV_LOOP=y
+CONFIG_BLK_DEV_RAM=y
+CONFIG_BLK_DEV_RAM_SIZE=8192
+CONFIG_MISC_DEVICES=y
+CONFIG_EEPROM_AT24=y
+CONFIG_BLK_DEV_SD=y
+CONFIG_SCSI_MULTI_LUN=y
+CONFIG_ATA=y
+CONFIG_PATA_AT91=y
+CONFIG_NETDEVICES=y
+CONFIG_NET_ETHERNET=y
+CONFIG_MACB=y
+CONFIG_RTL8187=m
+CONFIG_RT2X00=y
+CONFIG_RT2500USB=y
+CONFIG_RT73USB=y
+CONFIG_RT2800USB=y
+CONFIG_PPP=y
+CONFIG_PPP_ASYNC=y
+CONFIG_PPP_DEFLATE=y
+CONFIG_PPP_BSDCOMP=y
+CONFIG_PPP_MPPE=y
+CONFIG_INPUT_MOUSEDEV_SCREEN_X=320
+CONFIG_INPUT_MOUSEDEV_SCREEN_Y=240
+CONFIG_INPUT_EVDEV=y
+CONFIG_KEYBOARD_GPIO=y
+CONFIG_SERIAL_ATMEL=y
+CONFIG_SERIAL_ATMEL_CONSOLE=y
+CONFIG_I2C=y
+CONFIG_I2C_CHARDEV=y
+CONFIG_I2C_GPIO=y
+CONFIG_SPI=y
+CONFIG_SPI_ATMEL=y
+CONFIG_SPI_SPIDEV=y
+CONFIG_GPIO_SYSFS=y
+CONFIG_GPIO_PCF857X=y
+CONFIG_W1=y
+CONFIG_W1_MASTER_GPIO=y
+CONFIG_W1_SLAVE_DS2431=y
+CONFIG_USB=y
+CONFIG_USB_DEVICEFS=y
+CONFIG_USB_OHCI_HCD=y
+CONFIG_USB_ACM=y
+CONFIG_USB_STORAGE=y
+CONFIG_USB_GADGET=y
+CONFIG_USB_ETH=y
+CONFIG_MMC=y
+CONFIG_MMC_ATMELMCI=y
+CONFIG_NEW_LEDS=y
+CONFIG_LEDS_CLASS=y
+CONFIG_LEDS_GPIO=y
+CONFIG_LEDS_TRIGGER_TIMER=y
+CONFIG_LEDS_TRIGGER_HEARTBEAT=y
+CONFIG_LEDS_TRIGGER_DEFAULT_ON=y
+CONFIG_RTC_CLASS=y
+CONFIG_RTC_DRV_AT91SAM9=y
+CONFIG_EXT2_FS=y
+CONFIG_EXT3_FS=y
+CONFIG_EXT4_FS=y
+CONFIG_VFAT_FS=y
+CONFIG_TMPFS=y
+CONFIG_JFFS2_FS=y
+CONFIG_JFFS2_SUMMARY=y
+CONFIG_UBIFS_FS=y
+CONFIG_NFS_FS=y
+CONFIG_NFS_V3=y
+CONFIG_NLS_CODEPAGE_437=y
+CONFIG_NLS_CODEPAGE_850=y
+CONFIG_NLS_ISO8859_1=y
+CONFIG_NLS_ISO8859_15=y
+CONFIG_NLS_UTF8=y
arch/arm/mach-at91/Kconfig +7 -0
index c015b68..72c5b10 100644
@@ -381,6 +381,13 @@ config MACH_PCONTROL_G20
 	  Select this if you are using taskit's Stamp9G20 CPU module on this
 	  carrier board, beeing the decentralized unit of a building automation
 	  system; featuring nvram, eth-switch, iso-rs485, display, io
+
+config MACH_GSIA18S
+	bool "GS_IA18_S board"
+	help
+	  This enables support for the GS_IA18_S board
+	  produced by GeoSIG Ltd company. This is an internet accelerograph.
+	  <http://www.geosig.com>
 endif
 
 if (ARCH_AT91SAM9260 || ARCH_AT91SAM9G20)
arch/arm/mach-at91/Makefile +1 -0
index d13add7..e8a33c3 100644
@@ -66,6 +66,7 @@ obj-$(CONFIG_MACH_CPU9G20)	+= board-cpu9krea.o
 obj-$(CONFIG_MACH_STAMP9G20)	+= board-stamp9g20.o
 obj-$(CONFIG_MACH_PORTUXG20)	+= board-stamp9g20.o
 obj-$(CONFIG_MACH_PCONTROL_G20)	+= board-pcontrol-g20.o board-stamp9g20.o
+obj-$(CONFIG_MACH_GSIA18S)	+= board-gsia18s.o board-stamp9g20.o
 
 # AT91SAM9260/AT91SAM9G20 board-specific support
 obj-$(CONFIG_MACH_SNAPPER_9260)	+= board-snapper9260.o
arch/arm/mach-at91/board-gsia18s.c new file +587 -0

587 lines not on this page · raw message

arch/arm/mach-at91/include/mach/gsia18s.h new file +33 -0
new file mode 100644
index 0000000..307c194
@@ -0,0 +1,33 @@
+/* Buttons */
+#define GPIO_TRIG_NET_IN		AT91_PIN_PB21
+#define GPIO_CARD_UNMOUNT_0		AT91_PIN_PB13
+#define GPIO_CARD_UNMOUNT_1		AT91_PIN_PB12
+#define GPIO_KEY_POWER			AT91_PIN_PA25
+
+/* PCF8574 0x20 GPIO - U1 on the GS_IA18-CB_V3 board */
+#define GS_IA18_S_PCF_GPIO_BASE0	NR_BUILTIN_GPIO
+#define PCF_GPIO_HDC_POWER		(GS_IA18_S_PCF_GPIO_BASE0 + 0)
+#define PCF_GPIO_WIFI_SETUP		(GS_IA18_S_PCF_GPIO_BASE0 + 1)
+#define PCF_GPIO_WIFI_ENABLE		(GS_IA18_S_PCF_GPIO_BASE0 + 2)
+#define PCF_GPIO_WIFI_RESET		(GS_IA18_S_PCF_GPIO_BASE0 + 3)
+#define PCF_GPIO_ETH_DETECT		4 /* this is a GPI */
+#define PCF_GPIO_GPS_SETUP		(GS_IA18_S_PCF_GPIO_BASE0 + 5)
+#define PCF_GPIO_GPS_STANDBY		(GS_IA18_S_PCF_GPIO_BASE0 + 6)
+#define PCF_GPIO_GPS_POWER		(GS_IA18_S_PCF_GPIO_BASE0 + 7)
+
+/* PCF8574 0x22 GPIO - U1 on the GS_2G_OPT1-A_V0 board (Alarm) */
+#define GS_IA18_S_PCF_GPIO_BASE1	(GS_IA18_S_PCF_GPIO_BASE0 + 8)
+#define PCF_GPIO_ALARM1			(GS_IA18_S_PCF_GPIO_BASE1 + 0)
+#define PCF_GPIO_ALARM2			(GS_IA18_S_PCF_GPIO_BASE1 + 1)
+#define PCF_GPIO_ALARM3			(GS_IA18_S_PCF_GPIO_BASE1 + 2)
+#define PCF_GPIO_ALARM4			(GS_IA18_S_PCF_GPIO_BASE1 + 3)
+/* bits 4, 5, 6 not used */
+#define PCF_GPIO_ALARM_V_RELAY_ON	(GS_IA18_S_PCF_GPIO_BASE1 + 7)
+
+/* PCF8574 0x24 GPIO U1 on the GS_2G-OPT23-A_V0 board (Modem) */
+#define GS_IA18_S_PCF_GPIO_BASE2	(GS_IA18_S_PCF_GPIO_BASE1 + 8)
+#define PCF_GPIO_MODEM_POWER		(GS_IA18_S_PCF_GPIO_BASE2 + 0)
+#define PCF_GPIO_MODEM_RESET		(GS_IA18_S_PCF_GPIO_BASE2 + 3)
+/* bits 1, 2, 4, 5 not used */
+#define PCF_GPIO_TRX_RESET		(GS_IA18_S_PCF_GPIO_BASE2 + 6)
+/* bit 7 not used */
Signature · 1 line
1.7.0.4
#1 lore raw
Quoted 7 lines · Igor Plyatov

The GS_IA18_S (GMS) is a carrier board from GeoSIG Ltd used with the Stamp9G20 SoM from Taskit company.
It operate as an internet accelerometer.

---
 arch/arm/configs/gsia18s_defconfig        |  147 +++++++

please no new defconfig
start to merge them

your patch contain a lots of whitespace please fix it

arch/arm/mach-at91/board-gsia18s.c line 581

Quoted 6 lines
arch/arm/mach-at91/board-gsia18s.c new file +6 -0
+
+/*
+ * Up to date linux/arch/arm/tools/mach-types database required to support this.
+MACHINE_START(GSIA18S, "GS_IA18_S")
+*/
+MACHINE_START(STAMP9G20, "GS_IA18_S")

if you do this you must use system_rev to identify the board

arch/arm/mach-at91/board-gsia18s.c line 587

Quoted 6 lines
arch/arm/mach-at91/board-gsia18s.c new file +6 -0
+	.boot_params	= AT91_SDRAM_BASE + 0x100,
+	.timer		= &at91sam926x_timer,
+	.map_io		= gsia18s_map_io,
+	.init_irq	= init_irq,
+	.init_machine	= gsia18s_board_init,
+MACHINE_END

Best Regards,
J.

#2 lore raw

Dear Jean-Christophe,

Quoted 10 lines · Igor Plyatov
Quoted 7 lines

The GS_IA18_S (GMS) is a carrier board from GeoSIG Ltd used with the Stamp9G20 SoM from Taskit company.
It operate as an internet accelerometer.

---
 arch/arm/configs/gsia18s_defconfig        |  147 +++++++

please no new defconfig
start to merge them

I already write that it is not possible to use same defconfig for our board and Stamp9G20, because 69 different CONFIG_xxx options required for our machine (compared with Portux G20 and Stamp9G20) and our options very excessive for other devices based on the Stamp9G20. This device for the embedded, where space constraints exists for memory and it is required to save resources as more as possible.

Quoted 1 line

your patch contain a lots of whitespace please fix it

There is no problems with whitespace. This patch checked by scripts/checkpatch.pl twice. It seems your mailer corrupt this patch.

Quoted 7 lines

arch/arm/mach-at91/board-gsia18s.c line 581

Quoted 6 lines
arch/arm/mach-at91/board-gsia18s.c new file +6 -0
+
+/*
+ * Up to date linux/arch/arm/tools/mach-types database required to support this.
+MACHINE_START(GSIA18S, "GS_IA18_S")
+*/
+MACHINE_START(STAMP9G20, "GS_IA18_S")

if you do this you must use system_rev to identify the board

I can cite Christian Glindkamp:
"And for different carrier boards, system_rev does not make sense at all."

Please, use more testimony why it is required to use system_rev here. Yours position does not clear for me.
You can point me to the right documentation or discussion about this requirements in the mail archives...

Quoted 8 lines

arch/arm/mach-at91/board-gsia18s.c line 587

Quoted 6 lines
arch/arm/mach-at91/board-gsia18s.c new file +6 -0
+	.boot_params	= AT91_SDRAM_BASE + 0x100,
+	.timer		= &at91sam926x_timer,
+	.map_io		= gsia18s_map_io,
+	.init_irq	= init_irq,
+	.init_machine	= gsia18s_board_init,
+MACHINE_END

Best Regards,
J.

Best regards!
--
Igor Plyatov

#3 lore raw
Quoted 13 lines · Igor Plyatov

Dear Jean-Christophe,

Quoted 10 lines · Igor Plyatov
Quoted 7 lines

The GS_IA18_S (GMS) is a carrier board from GeoSIG Ltd used with the Stamp9G20 SoM from Taskit company.
It operate as an internet accelerometer.

---
 arch/arm/configs/gsia18s_defconfig        |  147 +++++++

please no new defconfig
start to merge them

Quoted 6 lines

I already write that it is not possible to use same defconfig for our board and Stamp9G20, because 69 different CONFIG_xxx options required for our machine (compared with Portux G20 and Stamp9G20) and our options very excessive for other devices based on the Stamp9G20. This device for the embedded, where space constraints exists for memory and it is required to save resources as more as possible.

sorry as I explain before if you have exclusive option you need to create kconfig options which are board specific to manage them
we work to reduce the number of defconfig in the mainline
and it's not PortuxG20 and Stamp9g20 specific but to have only one defconfig for all 9g20 at a first step and late for all sam9

Quoted 5 lines
Quoted 2 lines

your patch contain a lots of whitespace please fix it

There is no problems with whitespace. This patch checked by scripts/checkpatch.pl twice. It seems your mailer corrupt this patch.

my mailer no way mutt does not do it
and when I edit with vim I saw the whitespace too
please check again

Quoted 9 lines
Quoted 8 lines

arch/arm/mach-at91/board-gsia18s.c line 581

Quoted 7 lines
arch/arm/mach-at91/board-gsia18s.c new file +6 -0
+
+/*
+ * Up to date linux/arch/arm/tools/mach-types database required to support this.
+MACHINE_START(GSIA18S, "GS_IA18_S")
+*/
+MACHINE_START(STAMP9G20, "GS_IA18_S")

if you do this you must use system_rev to identify the board

Quoted 8 lines

I can cite Christian Glindkamp:
"And for different carrier boards, system_rev does not make sense at all."

Please, use more testimony why it is required to use system_rev here. Yours position does not clear for me.
You can point me to the right documentation or discussion about this requirements in the mail archives...

two bards with the same machine id NACK as we can not compile them in the same kernel and this a target we all work on to allow
if you want to tuse the same machine id as I did for other boards you must use system_rev or any detection to identify tehm

Best Regards,
J.

#4 lore raw
Quoted 6 lines · Jean-Christophe PLAGNIOL-VILLARD
Quoted 5 lines · Igor Plyatov

Dear Jean-Christophe,

Quoted 3 lines · Igor Plyatov
Quoted 2 lines

+/*
+ * Up to date linux/arch/arm/tools/mach-types database required to support this.

Please wrap comments.

Quoted 14 lines
Quoted 5 lines
Quoted 4 lines

arch/arm/mach-at91/board-gsia18s.c line 581

Quoted 3 lines
arch/arm/mach-at91/board-gsia18s.c new file +3 -0
+MACHINE_START(GSIA18S, "GS_IA18_S")
+*/
+MACHINE_START(STAMP9G20, "GS_IA18_S")

if you do this you must use system_rev to identify the board

Quoted 8 lines

I can cite Christian Glindkamp:
"And for different carrier boards, system_rev does not make sense at all."

Please, use more testimony why it is required to use system_rev here. Yours position does not clear for me.
You can point me to the right documentation or discussion about this requirements in the mail archives...

Quoted 4 lines

two bards with the same machine id NACK as we can not compile them in the same kernel and this a target we all work on to allow
if you want to tuse the same machine id as I did for other boards you must use system_rev or any detection to identify tehm

Well, the platform was registered into the machine database on 10th December, so it's missed my recent update to the file queued for the next -rc.

I also notice that the name has been changed - machine_is_gsia18s() vs MACH_TYPE_GS_IA18_S / CONFIG_MACH_GS_IA18_S. This means I'll simply delete it from any future updates until someone talks to me about fixing the entry, exactly as I'm doing with a bunch of others who also haven't contacted me.

All it takes is an email and the entry gets quickly fixed...

#5 lore raw

Dear Russell,

Quoted 9 lines · Jean-Christophe PLAGNIOL-VILLARD
Quoted 6 lines · Igor Plyatov
Quoted 5 lines

Dear Jean-Christophe,

Quoted 3 lines · Igor Plyatov
Quoted 2 lines

+/*
+ * Up to date linux/arch/arm/tools/mach-types database required to support this.

Please wrap comments.

This comment exactly 80 characters long, but anyway I will split it into two strings in next version of this patch.

Quoted 14 lines
Quoted 14 lines
Quoted 13 lines
Quoted 4 lines

arch/arm/mach-at91/board-gsia18s.c line 581

Quoted 3 lines
arch/arm/mach-at91/board-gsia18s.c new file +3 -0
+MACHINE_START(GSIA18S, "GS_IA18_S")
+*/
+MACHINE_START(STAMP9G20, "GS_IA18_S")

if you do this you must use system_rev to identify the board

I can cite Christian Glindkamp:
"And for different carrier boards, system_rev does not make sense at all."

Please, use more testimony why it is required to use system_rev here. Yours position does not clear for me.
You can point me to the right documentation or discussion about this requirements in the mail archives...

Quoted 8 lines
Quoted 4 lines

two bards with the same machine id NACK as we can not compile them in the same kernel and this a target we all work on to allow
if you want to tuse the same machine id as I did for other boards you must use system_rev or any detection to identify tehm

Well, the platform was registered into the machine database on 10th December, so it's missed my recent update to the file queued for the next -rc.

Just to clarify: my gsia18s machine number will be added into linux-2.6.37-rc6?

Does this mean that I must wait for rc6 and then send my patch with new machine name or I can send it now?

Quoted 7 lines

I also notice that the name has been changed - machine_is_gsia18s() vs MACH_TYPE_GS_IA18_S / CONFIG_MACH_GS_IA18_S. This means I'll simply delete it from any future updates until someone talks to me about fixing the entry, exactly as I'm doing with a bunch of others who also haven't contacted me.

All it takes is an email and the entry gets quickly fixed...

Russel, please fix it to more readable "gsia18s" and "*_GSIA18S" for my 3234 machine.
Old names with two underscores ("gs_ia18_s" and "*_GS_IA18_S") was very hard to read in the source code.

Best regards!
--
Igor Plyatov

#6 lore raw
Quoted 2 lines · Igor Plyatov

Just to clarify: my gsia18s machine number will be added into linux-2.6.37-rc6?

That depends on the timing of my next pull request. I don't have that much queued for the -rc at present, so I may skip sending stuff for rc6. It will be in before the next merge window now though, and idIt'll be queued in linux-next nevertheless.

Quoted 4 lines

Russel, please fix it to more readable "gsia18s" and "*_GSIA18S" for my 3234 machine.
Old names with two underscores ("gs_ia18_s" and "*_GS_IA18_S") was very hard to read in the source code.

Fixed, inspite of the spelling error above. Grr.

#7 lore raw

Dear Russell,

Quoted 1 line

Fixed, inspite of the spelling error above. Grr.

Thank you!

I'm sorry for typo.

Best regards!
--
Igor Plyatov

#8 lore raw
In reply to Jean-Christophe PLAGNIOL-VILLARD

Dear Jean-Christophe,

Quoted 5 lines

sorry as I explain before if you have exclusive option you need to create kconfig options which are board specific to manage them
we work to reduce the number of defconfig in the mainline
and it's not PortuxG20 and Stamp9g20 specific but to have only one defconfig for all 9g20 at a first step and late for all sam9

Thank you for time spent on my patches and e-mails!
I was think to do it this way, but unsure that this is a right way. Now, with yours help, I know what to do.

Quoted 7 lines
Quoted 4 lines
Quoted 1 line

your patch contain a lots of whitespace please fix it

There is no problems with whitespace. This patch checked by scripts/checkpatch.pl twice. It seems your mailer corrupt this patch.

my mailer no way mutt does not do it
and when I edit with vim I saw the whitespace too
please check again

I found this whitespaces. There is something strange inside of gedit, because I does not have practice to use spaces for formatting. It seems, time to learn vi, come :-)

Quoted 8 lines
Quoted 4 lines

Please, use more testimony why it is required to use system_rev here. Yours position does not clear for me.
You can point me to the right documentation or discussion about this requirements in the mail archives...

two bards with the same machine id NACK as we can not compile them in the same kernel and this a target we all work on to allow
if you want to tuse the same machine id as I did for other boards you must use system_rev or any detection to identify tehm

OK. I will use the GSIA18S machine instead of the STAMP9G20. The GSIA18S already registerd in the ARM machines database.

Best regards!
--
Igor Plyatov