Searched hist:"4213 fc2913722045eb2c327a64b99e3e3178aa5c" (Results 1 – 4 of 4) sorted by relevance
/openbmc/u-boot/arch/sandbox/include/asm/ |
H A D | io.h | 4213fc2913722045eb2c327a64b99e3e3178aa5c Sun Feb 24 11:33:14 CST 2013 Simon Glass <sjg@chromium.org> sandbox: Add un/map_sysmen() to deal with sandbox's ram_buf
Sandbox doesn't actually provide U-Boot access to the machine's physical memory. Instead it provides a RAM buffer of configurable size, and all memory accesses are within that buffer. Sandbox memory starts at 0 and is CONFIG_DRAM_SIZE bytes in size. Allowing access outside this buffer might produce unpredictable results in the event of an error, and would expose the host machine's memory architecture to the sandbox U-Boot.
Most U-Boot functions assume that they can just access memory at given address. For sandbox this is not true.
Add a map_sysmem() call which converts a U-Boot address to a system address. In most cases this is a NOP, but for sandbox it returns a pointer to that memory inside the RAM buffer.
To get a U-Boot feature to work correctly within sandbox, you should call map_sysmem() to get a pointer to the address, and then use that address for any U-Boot memory accesses.
Signed-off-by: Simon Glass <sjg@chromium.org>
|
/openbmc/u-boot/arch/sandbox/ |
H A D | config.mk | 4213fc2913722045eb2c327a64b99e3e3178aa5c Sun Feb 24 11:33:14 CST 2013 Simon Glass <sjg@chromium.org> sandbox: Add un/map_sysmen() to deal with sandbox's ram_buf
Sandbox doesn't actually provide U-Boot access to the machine's physical memory. Instead it provides a RAM buffer of configurable size, and all memory accesses are within that buffer. Sandbox memory starts at 0 and is CONFIG_DRAM_SIZE bytes in size. Allowing access outside this buffer might produce unpredictable results in the event of an error, and would expose the host machine's memory architecture to the sandbox U-Boot.
Most U-Boot functions assume that they can just access memory at given address. For sandbox this is not true.
Add a map_sysmem() call which converts a U-Boot address to a system address. In most cases this is a NOP, but for sandbox it returns a pointer to that memory inside the RAM buffer.
To get a U-Boot feature to work correctly within sandbox, you should call map_sysmem() to get a pointer to the address, and then use that address for any U-Boot memory accesses.
Signed-off-by: Simon Glass <sjg@chromium.org>
|
/openbmc/u-boot/include/ |
H A D | common.h | 4213fc2913722045eb2c327a64b99e3e3178aa5c Sun Feb 24 11:33:14 CST 2013 Simon Glass <sjg@chromium.org> sandbox: Add un/map_sysmen() to deal with sandbox's ram_buf
Sandbox doesn't actually provide U-Boot access to the machine's physical memory. Instead it provides a RAM buffer of configurable size, and all memory accesses are within that buffer. Sandbox memory starts at 0 and is CONFIG_DRAM_SIZE bytes in size. Allowing access outside this buffer might produce unpredictable results in the event of an error, and would expose the host machine's memory architecture to the sandbox U-Boot.
Most U-Boot functions assume that they can just access memory at given address. For sandbox this is not true.
Add a map_sysmem() call which converts a U-Boot address to a system address. In most cases this is a NOP, but for sandbox it returns a pointer to that memory inside the RAM buffer.
To get a U-Boot feature to work correctly within sandbox, you should call map_sysmem() to get a pointer to the address, and then use that address for any U-Boot memory accesses.
Signed-off-by: Simon Glass <sjg@chromium.org>
|
/openbmc/u-boot/ |
H A D | README | 4213fc2913722045eb2c327a64b99e3e3178aa5c Sun Feb 24 11:33:14 CST 2013 Simon Glass <sjg@chromium.org> sandbox: Add un/map_sysmen() to deal with sandbox's ram_buf
Sandbox doesn't actually provide U-Boot access to the machine's physical memory. Instead it provides a RAM buffer of configurable size, and all memory accesses are within that buffer. Sandbox memory starts at 0 and is CONFIG_DRAM_SIZE bytes in size. Allowing access outside this buffer might produce unpredictable results in the event of an error, and would expose the host machine's memory architecture to the sandbox U-Boot.
Most U-Boot functions assume that they can just access memory at given address. For sandbox this is not true.
Add a map_sysmem() call which converts a U-Boot address to a system address. In most cases this is a NOP, but for sandbox it returns a pointer to that memory inside the RAM buffer.
To get a U-Boot feature to work correctly within sandbox, you should call map_sysmem() to get a pointer to the address, and then use that address for any U-Boot memory accesses.
Signed-off-by: Simon Glass <sjg@chromium.org>
|