summaryrefslogtreecommitdiff
path: root/include/chromeos
diff options
context:
space:
mode:
authorGabe Black <gabeblack@chromium.org>2011-08-11 04:37:06 -0700
committerSimon Glass <sjg@chromium.org>2011-08-29 10:59:36 -0700
commit87d29940c710751191b82c18a49a79b490c03749 (patch)
tree0c92a818f19b2930b92d21fd7e50c0fb82ab93f0 /include/chromeos
parentf461780a13efe560edf8a16c8df1e7e9b92d7035 (diff)
Revert "Make the FMAP configuration decoding function board specific."
This reverts commit 23cefdce356de66442d858abf12c72afc8d33cac. Since we changed our minds about loading FMAP information from CBFS, we can go back to using the same mechanism on ARM and x86. BUG=chrome-os-partner:5432 TEST=Built and booted on x86-alex and verified that the FMAP information showed up in debugging output from vboot_twostop. Change-Id: Id41c82ca24dbfa301559e24104b5e226ec9b7e03 Signed-off-by: Gabe Black <gabeblack@google.com> Reviewed-on: http://gerrit.chromium.org/gerrit/5864 Reviewed-by: Stefan Reinauer <reinauer@google.com> Reviewed-by: Vadim Bendebury <vbendeb@chromium.org> Reviewed-by: Simon Glass <sjg@chromium.org> Tested-by: Gabe Black <gabeblack@chromium.org>
Diffstat (limited to 'include/chromeos')
-rw-r--r--include/chromeos/fmap.h4
1 files changed, 0 insertions, 4 deletions
diff --git a/include/chromeos/fmap.h b/include/chromeos/fmap.h
index a2a88a16b50..37efc4b1284 100644
--- a/include/chromeos/fmap.h
+++ b/include/chromeos/fmap.h
@@ -11,8 +11,6 @@
#ifndef CHROMEOS_FMAP_H_
#define CHROMEOS_FMAP_H_
-#include <compiler.h>
-
/* Structures to hold Chrome OS specific configuration from the FMAP. */
struct fmap_entry {
@@ -44,6 +42,4 @@ struct twostop_fmap {
void dump_fmap(struct twostop_fmap *config);
-int decode_twostop_fmap(struct twostop_fmap *fmap);
-
#endif /* CHROMEOS_FMAP_H_ */