Re: [U-Boot] armv8: cache_v8: mmu setup have the wrong pte attribute
hi Who's the maintainer of arch/arm/cpu/armv8? Please take a look at this issue, thanks a lot. Thanks, Jay -Original Message- From: U-Boot [mailto:u-boot-boun...@lists.denx.de] On Behalf Of Cao Jie Sent: Friday, June 23, 2017 4:36 PM To: u-boot@lists.denx.de Subject: [U-Boot] armv8: cache_v8: mmu setup have the wrong pte attribute Hi all I do some test on my board which have two armv8 CA53 core, and I found some region (1MB size) don't be correctly mapped by MMU. Through ds5 I can't find this region were mapped. I did some deep debug and found add_map function in cache_v8.c files maybe have some wrong operation for Some region which size equal to 1MB. For 1MB size region need three level translation and the descriptor of level 3 is different with level 1 and level 2. Look like current add_map function can't handle this case. Did someone hit this bug? By the way I use the 2017.05 version. Any feedback would be appreciate. Thanks, Jay ___ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot ___ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
[U-Boot] armv8: cache_v8: mmu setup have the wrong pte attribute
Hi all I do some test on my board which have two armv8 CA53 core, and I found some region (1MB size) don't be correctly mapped by MMU. Through ds5 I can't find this region were mapped. I did some deep debug and found add_map function in cache_v8.c files maybe have some wrong operation for Some region which size equal to 1MB. For 1MB size region need three level translation and the descriptor of level 3 is different with level 1 and level 2. Look like current add_map function can't handle this case. Did someone hit this bug? By the way I use the 2017.05 version. Any feedback would be appreciate. Thanks, Jay ___ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
[U-Boot] [ U-Boot ] armv8/start.S : what's the difference between CONFIG_ARMV8_SPIN_TABLE and CONFIG_ARMV8_MULTIENTRY
Hi all I am new to armv8's uboot and when I research codes about armv8/start.S I'm confused by two option: CONFIG_ARMV8_SPIN_TABLE and CONFIG_ARMV8_MULTIENTRY Both option have the same function which cause slave CPUS to enter standby mode, so why we have the two option for this case? What's the difference between them? Any feedback would be appreciate. Thanks, Jay ___ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot