And thank you for stumbling upon it in the first place :) and your continued help validating it until completion! Thanks Stefan, Bill and everyone else involed. Now let's hope Richard takes it into

Yes, verified it works great! Thanks for figuring this one out. -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates

I updated Stefan's bug w/ more explanation. I verified that Stefan's uImage-bad failed for me and then added the following to uEnv.txt: fdtaddr=0x88000000 uImage-bad (and uImage-good) worked w/ the

We cobbled together our own recipes to build the Go compiler (available upon request), which seem to be working well enough. We didn't need to make any changes to the recipes building the

Gary, et al, I've just submitted a patch to oe-core and yocto MLs that fixes this issue - could you please test it in your setup and confirm? Thanks! -- Denys

From: Denys Dmytriyenko <denys@...> Fix beaglebone boot issue with large kernel images overwriting Device Tree. See very detailed comments inside the patch. The original patch is being reviewed

Jate, You can use the 'hash' property. Just make sure you have no other branch/tag properties in the repo description. So, something like this should work: repos: [{'poky':

I am customizing the Yocto autobuilder for my own project. I would like to specify a checksum for the repourl for poky. What property do I need to add? I have tried adding the property commit, but it

Thank you Michael! Worked as a charm! 2014-04-16 18:48 GMT-03:00 Michael Halstead <michael@...>: -- Ronaldo Nunez

Thats looks reasonable patch to me. Provided it can be forward ported to gcc 4.8+ you should resubmit it for master

Is there a BSP for the J1900 anywhere? I thought I had seen some patches go through for Bay Trail, but I've not found anything obvious in meta-intel. I want to get accelerated GLES under X if that

I posted an RFC patch set last year but it didn't get any traction and we subsequently ruled out use of go so I never followed up on it but it might be a useful starting

Hi Paul, Thanks a lot for your help. I'm sure that there is a good reason why that's not the way it works. I will continue then using individual packages for

On 4/16/14, 1:21 PM, Stewart, David C wrote: Thanks Stewart. That is what I was looking for. regards, Armin > I found the following comments at >

Start by generating the gcc runtime and language support in gcc recipes. add it to RUNTIMETARGET and adjust PACKAGES you also need to add it to LANGUAGES that should get it to some point.

On 04/14/2014 07:41 AM, Martin Jansa wrote: It's a separate issue but as far as the yoctoproject.org infrastructure is concerned our primary SSL termination server runs OpenSSL

On 04/16/2014 02:15 PM, Ronaldo Nunez wrote: It isn't mentioned at http://www.yoctoproject.org/docs/1.6/bitbake-user-manual/bitbake-user-manual.html#git-fetcher but looking at

Hi all! I'm trying to create a custom recipe to a proprietary software from my company. The code should be fetched from a git server, with username and password authentication through a http

I found the following comments at https://wiki.yoctoproject.org/wiki/FAQ#What_is_the_release_cycle_of_the_Yoc to_Project.3F (It does seem like we have been supplying maintenance releases for

Hi Armin - let me do some research on this, just wanted to let you know that I had seen it. I'm not sure we have a formal statement published. -- Jeff Osier-Mixon @Intel Yocto Project Community