aboutsummaryrefslogtreecommitdiff
path: root/uncrustify.cfg
diff options
context:
space:
mode:
authorDrasko DRASKOVIC <drasko.draskovic@gmail.com>2011-06-22 12:45:21 +0200
committerØyvind Harboe <oyvind.harboe@zylin.com>2011-06-24 11:00:35 +0200
commit37aaa28292baee3592492933beb49d5e8884aa14 (patch)
tree95f1937d275c1ae0dc46dde1d2f7b666c80d6746 /uncrustify.cfg
parente7c611deeac63e585eb61d6c4cdb54d078c2c579 (diff)
Fix load_image for ELF with all p_paddr set to zero
So far image_load command tries to load ELF binaries to address discovered by reading p_paddr member of a Program header of an ELF segment. However, ELF specifications says for p_paddr : ...Because System V ignores physical addressing for application programs, this member has unspecified contents for executable files and shared objects. ARM ELF specifiaction goes even further, demanding that this member be set to zero, using the p_vaddr as a segment load address. To avoid the cases to wrong addr where p_paddr is zero, we are now using p_vaddr to as a load destination in case that *all* p_paddr == 0. Basically, this patch re-implements the approach present in BDF's elf.c, which is used by GDB also (so that we can be consistent).
Diffstat (limited to 'uncrustify.cfg')
0 files changed, 0 insertions, 0 deletions