Rename hardwaremain() to main()

... and drop the wrapper on ARMv7

Change-Id: If3ffe953cee9e61d4dcbb38f4e5e2ca74b628ccc
Signed-off-by: Stefan Reinauer <reinauer@google.com>
Signed-off-by: Gabe Black <gabeblack@chromium.org>
Reviewed-on: http://review.coreboot.org/3639
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>

8 files changed, 8 insertions, 8 deletions

diff --git a/src/mainboard/amd/dinar/get_bus_conf.c b/src/mainboard/amd/dinar/get_bus_conf.c
index 128a677e7f..a59bc437d3 100644
--- a/src/mainboard/amd/dinar/get_bus_conf.c
+++ b/src/mainboard/amd/dinar/get_bus_conf.c
@@ -83,7 +83,7 @@ void get_bus_conf(void)
 	 * call.  The logically correct place to call AmdInitLate is after PCI scan is done,
 	 * after the decision about S3 resume is made, and before the system tables are
 	 * written into RAM.  The routine that is responsible for writing the tables is
-	 * "write_tables", called near the end of "hardwaremain".  There is no platform
+	 * "write_tables", called near the end of "main".  There is no platform
 	 * specific entry point between the S3 resume decision point and the call to
 	 * "write_tables", and the next platform specific entry points are the calls to
 	 * the ACPI table write functions.  The first of ose would seem to be the right
diff --git a/src/mainboard/amd/inagua/get_bus_conf.c b/src/mainboard/amd/inagua/get_bus_conf.c
index d2c0b817f8..09e3b4ca02 100644
--- a/src/mainboard/amd/inagua/get_bus_conf.c
+++ b/src/mainboard/amd/inagua/get_bus_conf.c
@@ -71,7 +71,7 @@ void get_bus_conf(void)
 	 * call.  The logically correct place to call AmdInitLate is after PCI scan is done,
 	 * after the decision about S3 resume is made, and before the system tables are
 	 * written into RAM.  The routine that is responsible for writing the tables is
-	 * "write_tables", called near the end of "hardwaremain".  There is no platform
+	 * "write_tables", called near the end of "main".  There is no platform
 	 * specific entry point between the S3 resume decision point and the call to
 	 * "write_tables", and the next platform specific entry points are the calls to
 	 * the ACPI table write functions.  The first of ose would seem to be the right
diff --git a/src/mainboard/amd/parmer/get_bus_conf.c b/src/mainboard/amd/parmer/get_bus_conf.c
index 3ae4c18195..d1be8b6268 100644
--- a/src/mainboard/amd/parmer/get_bus_conf.c
+++ b/src/mainboard/amd/parmer/get_bus_conf.c
@@ -69,7 +69,7 @@ void get_bus_conf(void)
 	 * call.  The logically correct place to call AmdInitLate is after PCI scan is done,
 	 * after the decision about S3 resume is made, and before the system tables are
 	 * written into RAM.  The routine that is responsible for writing the tables is
-	 * "write_tables", called near the end of "hardwaremain".  There is no platform
+	 * "write_tables", called near the end of "main".  There is no platform
 	 * specific entry point between the S3 resume decision point and the call to
 	 * "write_tables", and the next platform specific entry points are the calls to
 	 * the ACPI table write functions.  The first of ose would seem to be the right
diff --git a/src/mainboard/amd/persimmon/get_bus_conf.c b/src/mainboard/amd/persimmon/get_bus_conf.c
index 11ec26e16e..8872bb5a1c 100644
--- a/src/mainboard/amd/persimmon/get_bus_conf.c
+++ b/src/mainboard/amd/persimmon/get_bus_conf.c
@@ -74,7 +74,7 @@ void get_bus_conf(void)
  * call.	The logically correct place to call AmdInitLate is after PCI scan is done,
  * after the decision about S3 resume is made, and before the system tables are
  * written into RAM.	The routine that is responsible for writing the tables is
- * "write_tables", called near the end of "hardwaremain".	There is no platform
+ * "write_tables", called near the end of "main".	There is no platform
  * specific entry point between the S3 resume decision point and the call to
  * "write_tables", and the next platform specific entry points are the calls to
  * the ACPI table write functions.	The first of ose would seem to be the right
diff --git a/src/mainboard/amd/south_station/get_bus_conf.c b/src/mainboard/amd/south_station/get_bus_conf.c
index cbe19d83b6..165c683d86 100644
--- a/src/mainboard/amd/south_station/get_bus_conf.c
+++ b/src/mainboard/amd/south_station/get_bus_conf.c
@@ -71,7 +71,7 @@ void get_bus_conf(void)
  * call.  The logically correct place to call AmdInitLate is after PCI scan is done,
  * after the decision about S3 resume is made, and before the system tables are
  * written into RAM.  The routine that is responsible for writing the tables is
- * "write_tables", called near the end of "hardwaremain".  There is no platform
+ * "write_tables", called near the end of "main".  There is no platform
  * specific entry point between the S3 resume decision point and the call to
  * "write_tables", and the next platform specific entry points are the calls to
  * the ACPI table write functions.  The first of ose would seem to be the right
diff --git a/src/mainboard/amd/thatcher/get_bus_conf.c b/src/mainboard/amd/thatcher/get_bus_conf.c
index 3ae4c18195..d1be8b6268 100644
--- a/src/mainboard/amd/thatcher/get_bus_conf.c
+++ b/src/mainboard/amd/thatcher/get_bus_conf.c
@@ -69,7 +69,7 @@ void get_bus_conf(void)
 	 * call.  The logically correct place to call AmdInitLate is after PCI scan is done,
 	 * after the decision about S3 resume is made, and before the system tables are
 	 * written into RAM.  The routine that is responsible for writing the tables is
-	 * "write_tables", called near the end of "hardwaremain".  There is no platform
+	 * "write_tables", called near the end of "main".  There is no platform
 	 * specific entry point between the S3 resume decision point and the call to
 	 * "write_tables", and the next platform specific entry points are the calls to
 	 * the ACPI table write functions.  The first of ose would seem to be the right
diff --git a/src/mainboard/amd/torpedo/get_bus_conf.c b/src/mainboard/amd/torpedo/get_bus_conf.c
index e2bd54edf2..4444937d57 100644
--- a/src/mainboard/amd/torpedo/get_bus_conf.c
+++ b/src/mainboard/amd/torpedo/get_bus_conf.c
@@ -76,7 +76,7 @@ void get_bus_conf(void)
  * call.  The logically correct place to call AmdInitLate is after PCI scan is done,
  * after the decision about S3 resume is made, and before the system tables are
  * written into RAM.  The routine that is responsible for writing the tables is
- * "write_tables", called near the end of "hardwaremain".  There is no platform
+ * "write_tables", called near the end of "main".  There is no platform
  * specific entry point between the S3 resume decision point and the call to
  * "write_tables", and the next platform specific entry points are the calls to
  * the ACPI table write functions.  The first of ose would seem to be the right
diff --git a/src/mainboard/amd/union_station/get_bus_conf.c b/src/mainboard/amd/union_station/get_bus_conf.c
index cbe19d83b6..165c683d86 100644
--- a/src/mainboard/amd/union_station/get_bus_conf.c
+++ b/src/mainboard/amd/union_station/get_bus_conf.c
@@ -71,7 +71,7 @@ void get_bus_conf(void)
  * call.  The logically correct place to call AmdInitLate is after PCI scan is done,
  * after the decision about S3 resume is made, and before the system tables are
  * written into RAM.  The routine that is responsible for writing the tables is
- * "write_tables", called near the end of "hardwaremain".  There is no platform
+ * "write_tables", called near the end of "main".  There is no platform
  * specific entry point between the S3 resume decision point and the call to
  * "write_tables", and the next platform specific entry points are the calls to
  * the ACPI table write functions.  The first of ose would seem to be the right