Searched hist:"7 a6a7d10e6b96ab4a5c0d8852802ec52be2b582e" (Results 1 – 2 of 2) sorted by relevance
| /rk3399_rockchip-uboot/arch/nios2/include/asm/ |
| H A D | system.h | 7a6a7d10e6b96ab4a5c0d8852802ec52be2b582e Mon Aug 16 02:49:44 UTC 2010 Thomas Chou <thomas@wytron.com.tw> nios2: fix out of reach case for do_reset
There is a limitation (or bug?) of nios2 toolchain. The nios2 gcc
didn't generate correct code when the reset vector is passed as a
constant. It just generated a direct "call", which was wrong when
the reset vector was not located in the same 256MB span as u-boot.
The "Nios II Processor Reference Handbook" said,
"call can transfer execution anywhere within the 256 MByte range
determined by PC31..28. The Nios II GNU linker does not automatically
handle cases in which the address is out of this range."
So we have to use registered "callr" instruction to do the job.
Signed-off-by: Thomas Chou <thomas@wytron.com.tw>
Signed-off-by: Scott McNutt <smcnutt@psyent.com>
|
| /rk3399_rockchip-uboot/arch/nios2/cpu/ |
| H A D | cpu.c | 7a6a7d10e6b96ab4a5c0d8852802ec52be2b582e Mon Aug 16 02:49:44 UTC 2010 Thomas Chou <thomas@wytron.com.tw> nios2: fix out of reach case for do_reset
There is a limitation (or bug?) of nios2 toolchain. The nios2 gcc
didn't generate correct code when the reset vector is passed as a
constant. It just generated a direct "call", which was wrong when
the reset vector was not located in the same 256MB span as u-boot.
The "Nios II Processor Reference Handbook" said,
"call can transfer execution anywhere within the 256 MByte range
determined by PC31..28. The Nios II GNU linker does not automatically
handle cases in which the address is out of this range."
So we have to use registered "callr" instruction to do the job.
Signed-off-by: Thomas Chou <thomas@wytron.com.tw>
Signed-off-by: Scott McNutt <smcnutt@psyent.com>
|