Quote:
|
I'm going to reproduce your steps. You seem to have used the rex board instead of wario, which I'm currently using. Perhaps that might explain something?
|
This is why I chose this config (this is in kernel extraction directory)
Code:
[root@drama gplrelease]# grep -Ri lab126 arch/arm/configs/
arch/arm/configs/imx_rex_defconfig:CONFIG_LOCALVERSION="-lab126"
arch/arm/configs/imx_rex_defconfig:CONFIG_LAB126=y
arch/arm/configs/imx_rex_defconfig:CONFIG_CPU_FREQ_OVERRIDE_LAB126=y
arch/arm/configs/imx_rex_android_defconfig:CONFIG_LOCALVERSION="-lab126"
arch/arm/configs/imx_rex_android_defconfig:CONFIG_LAB126=y
[root@drama gplrelease]#
Probably it is good idea to do the same with u-boot that comes with kindle source package. Haven't tried this one though.
Code:
[root@drama uboot]# grep -Ri lab126 configs/
configs/mx6sll_rex_defconfig:CONFIG_SYS_EXTRA_OPTIONS="IMX_CONFIG=board/lab126/mx6sll_rex/imximage.cfg,ANDROID_SUPPORT,CMD_COREMARK"
[root@drama uboot]#
Quote:
As for U-Boot being a dead end, why have you come to that conclusion? In your example, didn't U-Boot boot at all? As far as I know, if there is a problem in the file you supplied with -bios, then the boot sequence should have stopped, instead of continuing. It doesn't really "skip" U-Boot just like that.
Have you tried compiling mainline U-Boot (instead of Lab126 U-Boot) to see whether it boots under your setup of (host, QEMU version, cross-compiler toolchain)? Under my setup, the only i.MX board that boots in U-Boot is the imx25-pdk, and that happened with both mainline and Lab126 U-Boot.
|
Everything I tried with u-boot didn't ... you know boot. Except the binaries provided by the StackExchange thread. So I figured I am done compiling it. I think DTB file should suffice for helping the kernel find all devices which actually might be a problem, because QEMU probably can't emulate them all.
So I am kissing u-boot goodbye and trying to attach the rootfs.img if you don't beat me to it.
Quote:
|
Edit 2: If we bring up the Kindle OS without relying on U-Boot, then it would be good, but I feel that the presence of U-Boot is very important, because of the implementation of idme variables, which is necessary to boot without modifying the userland to skip the missing variables, and to provide a more complete emulation package overall.
|
I had no idea about this idme thing ... looked it up and it makes sense what are you saying.