summaryrefslogtreecommitdiff
path: root/arch/nios2/include/asm/bitops
diff options
context:
space:
mode:
authorThomas Chou <thomas@wytron.com.tw>2010-08-16 10:49:44 +0800
committerScott McNutt <smcnutt@psyent.com>2010-08-19 22:15:49 -0400
commit7a6a7d10e6b96ab4a5c0d8852802ec52be2b582e (patch)
treef8aad9ce824371f69022db5aedacd0f11477345d /arch/nios2/include/asm/bitops
parent62a05573822fc253a1ad5037482511347d6abaa5 (diff)
downloadu-boot-imx-7a6a7d10e6b96ab4a5c0d8852802ec52be2b582e.zip
u-boot-imx-7a6a7d10e6b96ab4a5c0d8852802ec52be2b582e.tar.gz
u-boot-imx-7a6a7d10e6b96ab4a5c0d8852802ec52be2b582e.tar.bz2
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>
Diffstat (limited to 'arch/nios2/include/asm/bitops')
0 files changed, 0 insertions, 0 deletions