On Wed, Feb 20, 2013 at 6:12 PM, Satya Swaroop Damarla <swaroop.dama...@gmail.com> wrote: > Hey hans, this is what he meant, > > In the machine config file add the following > > PREFERRED_VERSION_u-boot ?= "v2013.01%" or PREFERRED_VERSION_u-boot ?= > "v2013.01.01%" > > By the way did you already complete the first part... There is also other > file called "u-boot-fw-utils_2012.04.01.bb" ... I think we should do the > same... > > Hans bytheway, are you also working on the same board or diffferent board > with same problem? >
Different board, same core, similar problem ;) Now I get it. Thanks. But still question remains how in earth I managed to build the kernel if not also having copied/renamed the mkimage .bb? Is the PREFERRED_VERSION_u-boot used to determine what mkimage and fw utils it picks up? Then it might be that since I/we build u-boot as a separate package, but kernel lifts in the mkimage stuff, it works but the wrong package was used. In my case obviously compatible, but not recommended I guess. Also, I agree that the fw utils should probably be in sync similar to mkimage. Hans > > > > > > On Wed, Feb 20, 2013 at 6:01 PM, Hans Beckérus <hans.becke...@gmail.com> > wrote: >> >> On Wed, Feb 20, 2013 at 5:16 PM, Rudolf Streif >> <rstr...@linuxfoundation.org> wrote: >> > Satya, >> > >> > Simply look at the u-boot recipes in meta/recipes-bsp/u-boot such as >> > u-boot_2012.04.01.bb. You can simply copy it and name it >> > u-boot_2013.01.bb >> > and then modify SRCREV to the revision that corresponds to the tag >> > 2013.01 >> > or 2013.01.01 in git.denx.de: >> > >> > for 2013.01: 3a9d879f6f64585b819af728b53be0a05037fe0d >> > for 2013.01.01: e8ae0fa5edd152b2b29c470b88429be4cdcd2c46 >> > >> > Do the same for u-boot-mkimage and include the u-boot version with your >> > bsp. >> > >> > Rudi >> > >> > >> Hi Rudi, sorry to chime in , but I have a similar problem but do not >> really get the last thing you said. >> What do you mean by including the u-boot version in the bsp? Also is >> it a must to also copy the mkimage .bb or will the system find a >> suitable one automatically? >> The thing is that I only copied/edited the u-boot .bb but never the >> mkimage. Still my kernel successfully builds the kernel uImage!? >> Some magic that I have missed :) >> >> Hans >> >> >> > On Wed, Feb 20, 2013 at 5:17 AM, Satya Swaroop Damarla >> > <swaroop.dama...@gmail.com> wrote: >> >> >> >> Hi Guys, >> >> >> >> I need support for uboot on Tamonten board but the version on it is >> >> v2012.04 but I came to know that v2012.10 or v2013.01 supports the >> >> Tamontenboard through some guys here.. >> >> >> >> It would be great if you can tell me how can I accomplish v2013.01 or >> >> v2012.10 into the build system and make it available so that I can >> >> compile >> >> the and get uImage >> >> >> >> (Tamonten board is a derivative of harmony board with some changes and >> >> has >> >> arm cortexa9 processor without neon extentions ) >> >> >> >> I am kind of new to add new .bb files and help is really appreciated as >> >> I >> >> am not able to figure out how to add >> >> >> >> Greetings & Regards, >> >> Swaroop >> >> >> >> _______________________________________________ >> >> yocto mailing list >> >> yocto@yoctoproject.org >> >> https://lists.yoctoproject.org/listinfo/yocto >> >> >> > >> > >> > >> > -- >> > -- >> > Rudolf J. Streif >> > Director of Embedded Solutions >> > The Linux Foundation >> > >> > rudolf.str...@linux.com >> > Phone: +1.619.631.5383 >> > Skype: rudolfstreif >> > PGP: RSA 2048/2048 D6E7D28B >> > >> > Linux Foundation Events Schedule: events.linuxfoundation.org >> > Linux Foundation Training Schedule: training.linuxfoundation.org >> > >> > >> > _______________________________________________ >> > yocto mailing list >> > yocto@yoctoproject.org >> > https://lists.yoctoproject.org/listinfo/yocto >> > > > _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
