So far I've tried the following: 1) The current default in meta-raspberrypi - bootfiles at 56cd7ffb3f7244017c8eb3b492ea37592c678506 and kernel 0ec4154d64ebba48ca2446cde60a90546311defc 2) The above

That would be a good idea in my opinion too as i tried to make doc last week and i ended up dropping this task as i didn't have the time to search for those xml deps. @g

Hello Chris, Thanks for your detailed explanation. IMHO, this information should be added in the main documentation. It would be definitely helpful for others too. Regards -- Joshua Immanuel HiPro

You are not missing a thing, because I don't think you are the target user for the Build Appliance. :-) What I did find is that there are a number of *very* smart people who were failing at doing a

Yep, the later kernels just give the four-colour display. I wonder what's changed this time round? Chris Tapp opensource@... www.keylevel.com

Hi Paul, Firstly: 1) Are you using the SRCREVs as supplied, or have you updated them? 2) Which version of the bootfiles are you using? Everything is in such a state of flux at the moment that it

I had a need to look at the bitbake manual in the poky/bitbake/doc/manual directory and tried to make pdf. I had all the prerequisites listed in the QS guide. However, I found the make failed due to

Well, FWIW I can't even get a kernel with the default configuration built from meta-raspberrypi to boot - I even tried copying it to a Debian SD-card and it doesn't boot there either. All I get is a

Hi, The problem was because of Ubuntu 12.04 shell being configured by default to use dash, instead of bash. After I reconfigured the shell to use bash using the command: $ sudo dpkg-reconfigure

Hi, How can I source a shell script within a bbclass? For example, in meta-xilinx/classes/xilinx-boot.bbclass, I need to source a script file called settings64.sh, which setups the environment

with the recent discussion on this mailing list on Build Appliance, I thought I'd see what the heck Build Appliance was all about. I quickly realized that I couldn't use it because I have a Macbook

well I think redefining overridden value is right if you dont want to modify the layer policy SRCREV_pn-${PN} is the way to go with this layer then

Hi Khem, What do you recommend I do? Best regards, Elvis Dowson

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hmm I see SRCREV = "AUTOINC" in faulty case which is your problem comes from meta-xilinx layer it sets SRCEREV

Hi, Even adding a PROVIDES += "virtual/kernel" entry to the linux-xilinx recipe did not change the behavior. So for the moment, SRCREV doesn't seem to have any effect, but SRCREV_pn-${PN}

Hi Khem, The output files are rather large. BTW, I do not have a PROVIDES += "virtual/kernel" entry in the linux-xilinx kernel recipes. Is that necessary to get SRCREV to work? Best

? can you port bitbake -e virtual/kernel output with and without change somewhere ?

Hi, I found out that if I specify SRCREV_pn-${PN}, it works and picks up the correct commit id, as follows: SRCREV_pn-${PN} = "a5556fb251253ccb674bd22d9703c37f6f8807a8" However, if you

Has anyone else hit this? I'm running poky master as of the this afternoon: $ bitbake core-image-base ERROR: Nothing PROVIDES 'update-modules-nativesdk'

Hi, I find that specifying a SRCREV doesn't work for kernel git recipes. The following recipe has SRCREV set to the commit id for xilinx_v2.6.37, but during the build process, it is always