summaryrefslogtreecommitdiff
path: root/board/bf533-ezkit/bf533-ezkit.c
diff options
context:
space:
mode:
authorHaavard Skinnemoen <haavard.skinnemoen@atmel.com>2008-05-02 15:32:57 +0200
committerHaavard Skinnemoen <haavard.skinnemoen@atmel.com>2008-05-27 15:27:30 +0200
commitcaf83ea888a0220f41747d0b7748fa43b4a4bd49 (patch)
tree3ac20bbef11f75760e772c74b07ef99f8a466908 /board/bf533-ezkit/bf533-ezkit.c
parent0c16eed2189a190bd5655b33c029f809a9b31128 (diff)
downloadu-boot-imx-caf83ea888a0220f41747d0b7748fa43b4a4bd49.zip
u-boot-imx-caf83ea888a0220f41747d0b7748fa43b4a4bd49.tar.gz
u-boot-imx-caf83ea888a0220f41747d0b7748fa43b4a4bd49.tar.bz2
avr32: Use the same entry point for reset and exception handling
Since the reset vector is always aligned to a very large boundary, we can save a couple of KB worth of alignment padding by placing the exception vectors at the same address. Deciding which one it is is easy: If we're handling an exception, the CPU is in Exception mode. If we're starting up after reset, the CPU is in Supervisor mode. So this adds a very minimal overhead to the reset path (only executed once) and the exception handling path (normally never executed at all.) Signed-off-by: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
Diffstat (limited to 'board/bf533-ezkit/bf533-ezkit.c')
0 files changed, 0 insertions, 0 deletions