Just so I'm clear. You are asking about the switch to 3.0 as the default ? If so, that was only done in master for the upcoming 1.2 release and not on the edison branch, so you wouldn't pick it up by pulling.
Thanks! I did a git checkout -b master origin/master and will try again.
Thanks Bruce for pointing me in the right direction. I just wanted to follow up.
I switched to master branch and did a clean build for Beagleboard. I can confirm that it worked. I blew my SD Card away and put freshly built yocto images of MLO, u-boot.bin& uImage and my Beagleboard xM boots fine (one last question after this output below):
OMAP3630/3730-GP ES1.0, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz OMAP3 Beagle board + LPDDR/NAND I2C: ready DRAM: 512 MiB NAND: 256 MiB MMC: OMAP SD/MMC: 0 In: serial Out: serial Err: serial Beagle xM Rev A No EEPROM on expansion board Die ID #335000001bf00000015739ea07035019 Hit any key to stop autoboot: 0 SD/MMC found on device 0 reading uEnv.txt
** Unable to read "uEnv.txt" from mmc 0:1 ** reading uImage
3106612 bytes read Booting from mmc ... ## Booting kernel from Legacy Image at 82000000 ... Image Name: Linux-3.0.12-yocto-standard+ Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 3106548 Bytes = 3 MiB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
Yocto (Built by Poky 6.0) 1.1+snapshot-20120111 beagleboard ttyO2
beagleboard login: root root@beagleboard:~# ls root@beagleboard:~# uptime 19:06:08 up 0 min, load average: 1.08, 0.30, 0.10 root@beagleboard:~# uname -a Linux beagleboard 3.0.12-yocto-standard+ #1 PREEMPT Wed Jan 11 13:53:06 EST 2012 armv7l GNU/Linux root@beagleboard:~#
Excellent!
... so now I'm back to trying to get poky to use my local linux-yocto-3.0 git repo.
One more question. When I setup linux-yocto_3.0.bbappend in poky-extras/meta-kernel-dev/recipies-kernel/linux, do I use "yocto/standard/beagleboard" for KMACHINE?
If you still want the default (which you likely do here), you can leave KMACHINE untouched in your bbappend and the inherited value from the core layers will take care of everything. Get that working on your local clone, and then try tweaking things :)
