diff options
| author | Hung-Te Lin <hungte@chromium.org> | 2014-05-16 10:14:05 +0800 |
|---|---|---|
| committer | Marc Jones <marc.jones@se-eng.com> | 2015-01-03 17:33:13 +0100 |
| commit | 0780d67ffe8ef754ace0912114e2b1e772554990 (patch) | |
| tree | dd2b1adf8828b1d1855c8d7cff12be2b34a00d1a /src/include/device/i915_reg.h | |
| parent | 3ae558f5a1f00aba39621c5d0f042436c5f71789 (diff) | |
util/cbfstool: Fix byte-ordering for payload type field.
In https://chromium-review.googlesource.com/181272 the payload->type has been
changed to big-endian (network ordering) but the cbfs_image is still parsing
type as host ordering, which caused printing cbfs image verbosely
(cbfstool imge print -v) to fail to find entry field and print numerous
garbage output.
Payload fields should be always parsed in big-endian (network ordering).
BUG=none
TEST=make; cbfstool image.bin print -v -v -v # see payloads correctly
Original-Change-Id: If1ac355b8847fb54988069f694bd2f317ce49a1a
Original-Signed-off-by: Hung-Te Lin <hungte@chromium.org>
Original-Reviewed-on: https://chromium-review.googlesource.com/200158
Original-Reviewed-by: Ronald Minnich <rminnich@chromium.org>
(cherry picked from commit 423f7dd28f8b071692d57401e144232d5ee2e479)
Signed-off-by: Marc Jones <marc.jones@se-eng.com>
Change-Id: I5a4694e887c7ff48d8d0713bb5808c29256141a9
Reviewed-on: http://review.coreboot.org/8005
Reviewed-by: Ronald G. Minnich <rminnich@gmail.com>
Tested-by: build bot (Jenkins)
Diffstat (limited to 'src/include/device/i915_reg.h')
0 files changed, 0 insertions, 0 deletions