summaryrefslogtreecommitdiff
path: root/util/cbfstool/common.h
diff options
context:
space:
mode:
authorSol Boucher <solb@chromium.org>2015-05-07 02:39:22 -0700
committerStefan Reinauer <stefan.reinauer@coreboot.org>2015-05-13 22:23:37 +0200
commit67d5998d9778ef6f740aac4ed1c93fb311b32ebe (patch)
treed28f767a9f8f4230125a34914b9005bd3601fdea /util/cbfstool/common.h
parent67a0a864be0e8b81f22ebb9d6f090d77d1da2924 (diff)
downloadcoreboot-67d5998d9778ef6f740aac4ed1c93fb311b32ebe.tar.xz
cbfstool: Support top-aligned addresses for new-format images
The cbfstool handling of new-style FMAP-driven "partitioned" images originally disallowed the use of x86-style top-aligned addresses with the add.* and layout actions because it wasn't obvious how they should work, especially since the normal addressing is done relative to each individual region for these types of images. Not surprisingly, however, the x86 portions of the build system make copious use of top-aligned addresses, so this allows their use with new images and specifies their behavior as being relative to the *image* end---not the region end---just as it is for legacy images. Change-Id: Icecc843f4f8b6bb52aa0ea16df771faa278228d2 Signed-off-by: Sol Boucher <solb@chromium.org> Reviewed-on: http://review.coreboot.org/10136 Tested-by: build bot (Jenkins) Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
Diffstat (limited to 'util/cbfstool/common.h')
-rw-r--r--util/cbfstool/common.h2
1 files changed, 2 insertions, 0 deletions
diff --git a/util/cbfstool/common.h b/util/cbfstool/common.h
index 831d3eb088..392ec80bb1 100644
--- a/util/cbfstool/common.h
+++ b/util/cbfstool/common.h
@@ -50,6 +50,8 @@ extern int verbose;
#define MAX(x, y) ((x) > (y) ? (x) : (y))
#define MIN(x, y) ((x) < (y) ? (x) : (y))
+#define IS_TOP_ALIGNED_ADDRESS(x) ((uint32_t)(x) > 0x80000000)
+
#define unused __attribute__((unused))
static inline uint32_t align_up(uint32_t value, uint32_t align)