On Wed, Oct 15, 2014 at 4:35 AM, Joonyoung Shim <jy0922.shim@xxxxxxxxxxx> wrote: > Hi, > > Kevin Hilman <khilman <at> kernel.org> writes: > >> >> Hi Abhilash, >> >> Abhilash Kesavan <a.kesavan <at> samsung.com> writes: >> >> > I had noticed a similar issue where only 6 cores would come up during >> > development on 5420. This was because there was a check in our u-boot >> > secondary boot-up path which would put a core into WFI if a flag was >> > not present and hence fail to boot. I wonder if it is the same >> > situation in your case too. >> > Is the u-boot for odroid-xu3 publically available or can you check if > there is any such code present in your >> secondary bring-up path. >> >> I'm using the hardkernel u-boot[1], branch: odroidxu3-v2012.07. I'm >> currently using the pre-built binaries that are in the >> sd_fuse/hardkernel directory of that branch, but I can rebuild u-boot if >> needed. >> >> I'm not very familiar with u-boot, but if f you have some pointers where >> to start looking in that code, that would be helpful. >> >> Kevin >> >> [1] https://github.com/hardkernel/u-boot.git >> >> > > It seems to need magic code. > > Please refer > https://github.com/abhijeet-dev/linux-samsung/commit/553b7f40465ab4fad6c270f289cd4780942f7fae Thanks, Abhilash had pointed me to the same code, and it works. But... Can someone explain this "magic", ideally in the form of a changelog and patch submitted upstream? Kevin -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
 |