Skip to content
Snippets Groups Projects
Commit d060c49a authored by Rasmus Villemoes's avatar Rasmus Villemoes Committed by Tom Rini
Browse files

README: drop mention of MEM_SUPPORT_64BIT_DATA


The first sentence is half-way true; the macro is always defined, but
has the value 0 or 1.

The second is outright false. A lot of code guarded by
MEM_SUPPORT_64BIT_DATA uses a "ulong" to store values, so if
sizeof(long) is not 8, that code would probably compile, but not work
at all as expected.

It would probably be possible to make all such code explicitly use u64
and thus make it work on 32 bit targets, but until that is done, do
not pretend that it's ok to override the automatic value of
MEM_SUPPORT_64BIT_DATA.

Signed-off-by: default avatarRasmus Villemoes <rasmus.villemoes@prevas.dk>
parent 4762c515
No related branches found
No related tags found
No related merge requests found
...@@ -1240,9 +1240,6 @@ typically in board_init_f() and board_init_r(). ...@@ -1240,9 +1240,6 @@ typically in board_init_f() and board_init_r().
Configuration Settings: Configuration Settings:
----------------------- -----------------------
- MEM_SUPPORT_64BIT_DATA: Defined automatically if compiled as 64-bit.
Optionally it can be defined to support 64-bit memory commands.
- CONFIG_SYS_LONGHELP: Defined when you want long help messages included; - CONFIG_SYS_LONGHELP: Defined when you want long help messages included;
undefine this when you're short of memory. undefine this when you're short of memory.
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment