Hi, * Adam Ford <aford173@xxxxxxxxx> [220302 14:37]: > I apologize for digging up an old thread, but I finally managed to get > my hands on an OMAP3503. It seems like older kernels do not boot at > all or hang somewhere in the boot process. I am still seeing a > difference in behavior between OMAP3503 and OMAP3530, where 3505 > throws a bunch of splat and a kernel panic, while the 3530 appears to > boot happily. > > Using the latest 5.17-rc6, I had to remove some IVA and SGX references > from omap_l3_smx.h to get the 3503 to stop crashing on boot. OK interesting, I did not know those registers are not accessible on 3503. > Do you have any ideas how we can make the omap3_l3_app_bases and > omap3_l3_debug_bases more cleanly remove the IVA and SGX references > if/when OMAP3503 is detected? I assume the same algorithm would have > to detect a AM3703 as well. I'm trying to get my hands on an AM3703 > to see if there is similar behavior as what I'm seeing on the > OMAP3503. As there are possibly multiple omap3 variants used on the same boards, we need to rely on the runtime detection of the SoC. So yeah soc_device_attribute is the way to go here. I don't recall any similar issues booting 3703 but it's been a while so worth testing for sure. Regards, Tony
