diff options
| author | Rasmus Villemoes | 2024-01-03 11:47:09 +0100 |
|---|---|---|
| committer | Tom Rini | 2024-01-17 08:00:07 -0500 |
| commit | d060c49afe21578460b55173597885c16754fdae (patch) | |
| tree | 1065c913567acfa4c8010c5017b6fd4542468065 /README | |
| parent | 4762c51562fb7ff42d502b3ee88d0c9da6aade49 (diff) | |
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: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
Diffstat (limited to 'README')
| -rw-r--r-- | README | 3 |
1 files changed, 0 insertions, 3 deletions
@@ -1240,9 +1240,6 @@ typically in board_init_f() and board_init_r(). 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; undefine this when you're short of memory. |