标题 | 阅读 | 评论 | 转发 | 发布日期 | |
---|---|---|---|---|---|
Unix系列shell程序编写从入门到精通 | 914 | 0 | 0 | 2008-04-29 | |
linux内核启动分析 | 1901 | 0 | 0 | 2008-04-08 | |
crc 校验错误分析 | 7080 | 1 | 0 | 2008-04-07 | |
do_boot启动linux的改动 | 2090 | 0 | 0 | 2008-04-07 | |
u-boot分析(二) | 1280 | 0 | 0 | 2008-04-06 | |
Uboot-1.1.2 for PXA270源码分析-初始化部分代码(board.c)(转) | 1817 | 0 | 0 | 2008-04-06 | |
u-boot 启动内核分析(转) | 1712 | 0 | 0 | 2008-04-06 | |
了解UBOOT添加命令的执行流程 | 1247 | 0 | 0 | 2008-04-02 |
redglass2008-09-10 13:12
我做2440系统的移植的时候发现这样的问题 在一开始进行到setup_processor这个函数的时候(arch/arm/kernel/setup.c)跟踪看了一下list = lookup_processor_type();得到的指针是null,跟踪进去看汇编,就是head.s中的那个__lookup_processor_type函数,代码如下,其中把各个寄存器的值都打出来了,看了都没什么问题,在1:后答应看到的r3,r4,r9都能和arch/arm/mm/proc-arm920.s对应上(后面有代码),应该能正常的到2:,但是怎么在c里面的那个语句获得不到该得到的值呢?请知道的话帮我解释一下吧。谢谢了 __lookup_processor_type: adr r3, 3f ldmda r3, {r5, r6, r9} sub r3, r3, r9 @ get offset between virt&phys add r5, r5, r3 @ convert virt addresses to add r6, r6, r3 @ physical address space mrc p15, 0, r9, c0, c0 @ get processor id 1: ldmia r5, {r3, r4} @ value, mask and r4, r4, r9 @ mask wanted bits teq r3, r4 beq 2f add r5, r5, #PROC_INFO_SZ @ sizeof(proc_info_list) cmp r5, r6 blo 1b mov r5, #0 @ unknown processor 2: mov pc, lr __arm920_proc_info: .long 0x41009200 .long 0xff00fff0 .long PMD_TYPE_SECT | \ PMD_SECT_BUFFERABLE | \ PMD_SECT_CACHEABLE | \ PMD_BIT4 | \ PMD_SECT_AP_WRITE | \ PMD_SECT_AP_READ b __arm920_setup .long cpu_arch_name .long cpu_elf_name .long HWCAP_SWP | HWCAP_HALF | HWCAP_THUMB .long cpu_arm920_name .long arm920_processor_functions .long v4wbi_tlb_fns .long v4wb_user_fns #ifndef CONFIG_CPU_DCACHE_WRITETHROUGH .long arm920_cache_fns #else .long v4wt_cache_fns #endif .size __arm920_proc_info, . - __arm920_proc_info