Re: [yocto] [raspberrypi] raspi3 vs raspi2

ssage----- >> From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] >> On Behalf Of Khem Raj >> Sent: samedi 19 novembre 2016 18:30 >> To: Trevor Woerner <twoer...@gmail.com> >> Cc: yocto@yoctoproject.org >> Subject: ***SPAM*** Re: [yo

Re: [yocto] uninative workflow

Excellent! Thanks, Ross, for the explanations :-) On Mon, Nov 21, 2016 at 9:40 AM, Burton, Ross <ross.bur...@intel.com> wrote: > > On 18 November 2016 at 21:30, Trevor Woerner <twoer...@gmail.com> wrote: >> >> To be honest, I'm not entirely sure what the unina

[yocto] uninative workflow

Hi, To be honest, I'm not entirely sure what the uninative stuff is (explanations or pointers to explanations appreciated!) but I'm trying to figure out how to work with it. Previously, generating an eSDK didn't require a uninative-tarball, but now, apparently, it does? Any idea why? So now, in

[yocto] [raspberrypi] raspi3 vs raspi2

Hi, I was wondering if there were any plans to create a MACHINE=raspberrypi3 that treats the raspi3 like the CortexA53 that it is instead of generating images that are backwards compatible with the CortexA7 that is the raspi2? Best regards, Trevor --

Re: [yocto] Yocto 2.2 Morty supported Linux Distros

On 11/01/2016 11:27 AM, Burton, Ross wrote: Scott, can you update the list at http://www.yoctoproject.org/docs/2.2/ref-manual/ref-manual.html#detailed-supported-distros so that it reflects the list in the code: SANITY_TESTED_DISTROS ?= " \ poky-1.8 \n \ poky-2.0 \n \

Re: [yocto] YoctoProject: problem bitbake core-image-minimal

t; _WIFSIGNALED=os.WIFSIGNALED, > 1331:_WTERMSIG=os.WTERMSIG, _WIFEXITED=os.WIFEXITED, > Exception: OSError: [Errno 2] No such file or directory > > ERROR: quilt-native-0.64-r0 do_populate_sysroot: Function failed: > relocatable_binaries_preprocess > ERROR: Logfile

Re: [yocto] YoctoProject: problem bitbake core-image-minimal

Hi Luca, In order for us to help you, could you please provide more information which better describes exactly what you did? I have no experience with any of the paid SUSE products, but I do know that poky can be built fine with openSUSE Leap 42.1 or 13.2 on x86-64 hardware. There is a lot of

Re: [yocto] Migration info - runqemu

On Fri, Oct 14, 2016 at 5:16 AM, Robert Yang wrote: > Yes, the benefit is that the machine knowledge are not hardcoded into > runqemu any more, the bsp can define its own arguments to make it can be > boot by runqemu. And previous usage patterns also be supported.

Re: [yocto] [meta-raspberrypi] taskhash mismatch

On Fri, Oct 14, 2016 at 5:25 AM, Andrei Gherzan wrote: > I know I'm kinda late to the party but just wanted to say that this was > fixed in master. Cheers! Excellent. I just tried 3 builds in a row and they all succeeded! Thanks for the update. --

Re: [yocto] [meta-raspberrypi][PATCH] sdcard_image-rpi.bbclass: remove redundant IMAGEDATESTAMP

On Wed 2016-10-05 @ 11:01:15 AM, Jonathan Liu wrote: > See if the following helps: > bitbake -c cleanall core-image-minimal && bitbake core-image-minimal Odd. I had started this email to say that this wasn't working (since this is exactly what I had tried a couple times over the last several

Re: [yocto] [meta-raspberrypi] taskhash mismatch

> On Oct 3, 2016 1:39 PM, "Trevor Woerner" <twoer...@gmail.com> wrote: > > Odd... even with this patch I'm still seeing sporadic failures :-( On Mon 2016-10-03 @ 02:35:22 PM, Khem Raj wrote: > I guess you need to look at sognatures and see why its changing. Actu

Re: [yocto] [meta-raspberrypi][PATCH] sdcard_image-rpi.bbclass: remove redundant IMAGEDATESTAMP

Unfortunately it doesn't fix the taskhash problem. It still happens on every build I perform: core-image-minimal-1.0-r0 do_image_rpi_sdimg: Taskhash mismatch 536a3bcf4ac29225841c369636b533ff versus 8fadff5d0ef51aa648ed359d5dd7f944 In fact, every time I run a build I get the exact same two

Re: [yocto] [meta-raspberrypi] taskhash mismatch

Odd... even with this patch I'm still seeing sporadic failures :-( On Mon, Oct 3, 2016 at 2:48 PM, Trevor Woerner <twoer...@gmail.com> wrote: > On Mon 2016-10-03 @ 06:45:55 PM, Karim ATIKI wrote: >> Note: I just launched the build again with bitbake -k core-image-x11and >&

Re: [yocto] [meta-raspberrypi] taskhash mismatch

On Mon 2016-10-03 @ 06:45:55 PM, Karim ATIKI wrote: > Note: I just launched the build again with bitbake -k core-image-x11and > > the error did not occur again. > Well, a bit weird. Don't really know why does this error raised though. It looks like the patch to which Khem refers was just

[yocto] [meta-raspberrypi] taskhash mismatch

Hi, For the last week or so my raspberry pi builds have been failing with: ERROR: core-image-minimal-1.0-r0 do_image_rpi_sdimg: Taskhash mismatch 2920e557ac3a011d5679a52590cb664d versus a47bfc12fdfa29c58fe72cf8e0a28e91 for

Re: [yocto] Cortex-M4 build support

On Tue 2016-09-13 @ 01:15:49 PM, Khem Raj wrote: > > > On Sep 13, 2016, at 10:31 AM, robert.berger@gmane > > wrote: > > > > Hi, > > > > Shouldn't it be possible to build a bare-metal Cortex-M4 compiler with the > > YP and build a small RTOS like FreeRTOS

Re: [yocto] gcc-6.1 and raspi

; meta-raspberrypi uses it. > This is the link to the patch: > http://article.gmane.org/gmane.linux.embedded.yocto.general/30093/ Thanks, the patch works great :-) > > Herve > > > On 6 juin 2016, at 04:08, Trevor Woerner <twoer...@gmail.com> wrote: > > > &g

Re: [yocto] gcc-6.1 and raspi

On Sun 2016-06-05 @ 04:55:47 PM, Herve Jourdain wrote: > It seems like you are building the 4.1.21 kernel. > Did you set PREFERRED_VERSION_linux-raspberrypi = "4.4.%" in your > distro.conf or local.conf? I was trying to save myself the time required to rebuild with the 4.4 kernel. I knew from my

Re: [yocto] gcc-6.1 and raspi

On Sun 2016-06-05 @ 02:14:29 PM, Herve Jourdain wrote: > I'm using kernel 4.4, and it does build properly with gcc 6.1. > But the build does fail on other packages later on, so I ended up reverting > to 5.3 for now. Both the official meta-raspberrypi and Khem Raj's meta-raspberrypi layers have

[yocto] gcc-6.1 and raspi

Has anyone tried building a raspi image lately from master? ERROR: linux-raspberrypi-1_4.1.21+gitAUTOINC+ff45bc0e89-r0 do_compile: Function failed: do_compile | In file included from

Re: [yocto] [meta-chip][PATCH] u-boot-chip: fix md5sum

ping On Mon 2016-04-11 @ 02:28:30 PM, Trevor Woerner wrote: > The u-boot master and chip/stable branches have diverged such that the md5sums > of the License README files are now different. The latest master branch has > added a "SIL OPEN FONT LICENSE (OFL-1.1)"

Re: [yocto] [OE-core] Yocto Project Status WW17

On Fri 2016-04-22 @ 08:29:19 PM, Burton, Ross wrote: > On 22 April 2016 at 18:04, Trevor Woerner <twoer...@gmail.com> wrote: > > > > Have the eSDK and CROPS projects been announced publicly? Are they > available > > for us to "play with"? > > > e

Re: [yocto] [OE-core] Yocto Project Status WW17

On Fri 2016-04-22 @ 03:13:21 PM, Jolley, Stephen K wrote: > o Encourage adoption of new tools (toaster, eSDK, CROPS) Have the eSDK and CROPS projects been announced publicly? Are they available for us to "play with"? -- ___ yocto mailing list

Re: [yocto] [meta-chip][PATCH] u-boot-chip: fix md5sum

ping? (this is needed to build successfully) On Mon 2016-04-11 @ 02:28:30 PM, Trevor Woerner wrote: > The u-boot master and chip/stable branches have diverged such that the md5sums > of the License README files are now different. The latest master branch has > added a "SIL OPEN FON

Re: [yocto] [meta-raspberrypi][PATCH v2 3/5] rpi-base.inc: Add overlay for rpi-ft5406

On Wed 2016-03-30 @ 04:35:47 PM, Petter Mabäcker wrote: > rpi-ft5406 is an enabler for Official Raspberry Pi 7 inch > touchscreen support. I have an official raspberry pi 7" touchscreen and it's not obvious to me how I would go about enabling it in my config. If I had one of the others I would

[yocto] [meta-raspberrypi][PATCH] serial console definition split

The latest raspberrypi3 puts its console on ttyS0 instead of ttyAMA0 (like all the preceding boards). Therefore pull this definition out of the common include file and add it separately for each MACHINE. Signed-off-by: Trevor Woerner <twoer...@gmail.com> --- conf/machine/include/rpi-base.i

Re: [yocto] [meta-raspberrypi][PATCH v2 1/2] raspberrypi3: serial console

On Wed 2016-04-13 @ 04:20:36 AM, Andrei Gherzan wrote: > On Mon, Apr 11, 2016 at 05:54:44PM -0400, Trevor Woerner wrote: > > The serial console on the Raspberry Pi 3 is located at /dev/ttyS0 and not > > /dev/ttyAMA0. > > > > Signed-off-by: Trevor Woerner <twoer..

[yocto] [meta-raspberrypi][PATCH v2 2/2] raspberrypi3: set core frequency

Pegging the core frequency at 250 avoids any fluctuations of the baud rate on the console. See: https://www.raspberrypi.org/forums/viewtopic.php?f=107=138223 Signed-off-by: Trevor Woerner <twoer...@gmail.com> --- conf/machine/raspberrypi3.conf | 1 + 1 file changed, 1 insertion(+)

[yocto] [meta-raspberrypi][PATCH v2 1/2] raspberrypi3: serial console

The serial console on the Raspberry Pi 3 is located at /dev/ttyS0 and not /dev/ttyAMA0. Signed-off-by: Trevor Woerner <twoer...@gmail.com> --- conf/machine/raspberrypi3.conf | 2 ++ 1 file changed, 2 insertions(+) diff --git a/conf/machine/raspberrypi3.conf b/conf/machine/raspberrypi

[yocto] [meta-chip][PATCH] u-boot-chip: fix md5sum

X11 x11.txt https://spdx.org/licenses/X11.html Signed-off-by: Trevor Woerner <twoer...@gmail.com> --- recipes-bsp/u-boot/u-boot-chip_git.bb | 2 ++ 1 file changed, 2 insertions(+) diff --git a/recipes-bsp/u-boot/u-boot-chip_git.bb b/recipes-bsp/u-boot/u-boot-c

Re: [yocto] [PATCH][meta-raspberrypi 1/2] raspberrypi3: serial console

On Mon 2016-04-04 @ 08:06:30 AM, Trevor Woerner wrote: > On Mon 2016-04-04 @ 04:32:41 PM, Gary Thomas wrote: > > On 04/04/2016 03:24 PM, Trevor Woerner wrote: > > >The serial console on the Raspberry Pi 3 is located at /dev/ttyS0 and not > > >/dev/ttyAMA0. > > >

Re: [yocto] [meta-raspberry] Raspberry Pi 3

On Sun 2016-04-03 @ 07:29:59 PM, Khem Raj wrote: > On Sun, Apr 3, 2016 at 6:38 PM, Trevor Woerner <twoer...@gmail.com> wrote: > > Thanks to everyone for their help!! It looks like I've got something > > working, > > not sure if this is a "solution" or if m

Re: [yocto] [PATCH][meta-raspberrypi 1/2] raspberrypi3: serial console

On Mon 2016-04-04 @ 04:32:41 PM, Gary Thomas wrote: > On 04/04/2016 03:24 PM, Trevor Woerner wrote: > >The serial console on the Raspberry Pi 3 is located at /dev/ttyS0 and not > >/dev/ttyAMA0. > > > >Signed-off-by: Trevor Woerner <twoer...@gmail.com> > >---

Re: [yocto] [PATCH][meta-raspberrypi 1/2] raspberrypi3: serial console

On Mon 2016-04-04 @ 04:32:41 PM, Gary Thomas wrote: > On 04/04/2016 03:24 PM, Trevor Woerner wrote: > >The serial console on the Raspberry Pi 3 is located at /dev/ttyS0 and not > >/dev/ttyAMA0. > > > >Signed-off-by: Trevor Woerner <twoer...@gmail.com> > >---

[yocto] [PATCH][meta-raspberrypi 1/2] raspberrypi3: serial console

The serial console on the Raspberry Pi 3 is located at /dev/ttyS0 and not /dev/ttyAMA0. Signed-off-by: Trevor Woerner <twoer...@gmail.com> --- conf/machine/raspberrypi3.conf | 2 ++ 1 file changed, 2 insertions(+) diff --git a/conf/machine/raspberrypi3.conf b/conf/machine/raspberrypi

[yocto] [PATCH][meta-raspberrypi 2/2] raspberrypi3: set core frequency

Pegging the core frequency at 250 avoids any fluctuations of the baud rate on the console. See: https://www.raspberrypi.org/forums/viewtopic.php?f=107=138223 Signed-off-by: Trevor Woerner <twoer...@gmail.com> --- conf/machine/raspberrypi3.conf | 1 + 1 file changed, 1 insertion(+)

Re: [yocto] [meta-raspberry] Raspberry Pi 3

Thanks to everyone for their help!! It looks like I've got something working, not sure if this is a "solution" or if most would just consider it a work-around: 1) use Andrei's meta-raspberrypi layer (which selects linux kernel 4.1 by default) 2) add the following to your local.conf:

Re: [yocto] [meta-raspberry] Raspberry Pi 3

On Fri 2016-04-01 @ 03:17:29 PM, Trevor Woerner wrote: > As far as I can tell there are two raspberry pi OE layers which include this > commit: > > 1. git://git.yoctoproject.org/meta-raspberrypi::master > 2. https://github.com/kraj/meta-raspberrypi.git::kraj/master [..

Re: [yocto] [meta-raspberry] Raspberry Pi 3

On Thu 2016-03-31 @ 09:36:16 AM, Khem Raj wrote: > > > On Mar 31, 2016, at 8:26 AM, Trevor Woerner <twoer...@gmail.com> wrote: > > > > On Fri 2016-03-18 @ 10:15:39 AM, David Weisgerber wrote: > >> Hi, > >> did anyone succeed in building an imag

Re: [yocto] [meta-raspberry] Raspberry Pi 3

On Fri 2016-03-18 @ 10:15:39 AM, David Weisgerber wrote: > Hi, > did anyone succeed in building an image that runs on Raspberry Pi 3? I set my > conf/local.conf to > > MACHINE ??= "raspberrypi3" > GPU_MEM = "128" > DISABLE_OVERSCAN = "1" > > and built rpi-basic-image but when booting the Pi 3

Re: [yocto] [OE-core] [oe] OEDAM, April 8 in San Diego after ELC

On Wed 2016-03-23 @ 09:36:40 AM, akuster808 wrote: > There are only 10 people signed up. > Is that enough people to justify the expense room or even meet? I have no idea what the budget might be or what a room might cost. I'll leave it to those who do know to worry about the costs versus the

Re: [yocto] Raspberry Pi 2 BSP build problem

This looks like the problem we were experiencing a while back when we were switching from gcc-4x to gcc-5x. If I remember correctly, a certain range of slightly older kernel/u-boot could not be compiled by gcc-5x toolchains without a patch. You could look around for that patch. Or you could

Re: [yocto] [Openembedded-architecture] Standalone image writer

On 02/28/16 20:46, Khem Raj wrote: On Feb 28, 2016, at 4:17 PM, Paul Eggleton wrote: (changing subject line so people don't miss this slight tangent) I'd almost completely forgotten, but the part of what we wrote for Hob to write images to a USB stick or SD

Re: [yocto] [meta-raspberrypi][PATCH] linux-raspberrypi: Adjust for libexecdir changes

On 02/23/16 23:21, Khem Raj wrote: You can try to use github.com/kraj/meta-raspberrypi kraj/master I plan to test out more and more pending submissions on that branch Thanks, and done. It's too bad meta-raspberrypi didn't have a master-next branch :-) --

Re: [yocto] [meta-raspberrypi][PATCH] linux-raspberrypi: Adjust for libexecdir changes

On 02/24/16 15:28, Anders Darander wrote: If the rest of the patches in that series is non-controversial, could we have them applied? Otherwise, could we have Khem's patch applied, and the other series rebased upon that? We've had the master branch non-building for quite a while now... I'm

Re: [yocto] Layer manifest (topic touched at ELCE)

On 01/06/16 17:42, Mark Hatle wrote: > But using a combination of the defined dependencies and the layer index you > should be able to resolve "known" layers. (Would also be nice if the index > looked for collisions as well...) I wrote a silly script[1] that probes the layer index and presents

Re: [yocto] Best practice for files copied directly into sysroot?

On 12/04/15 09:03, Bryan Evenson wrote: > Although I am having issues with the license; I haven't figured out where to > put it and what to set LIC_FILES_CHKSUM to in the recipe so that bitbake can > find the license. If anyone has a good answer for that, let me know. You could try:

Re: [yocto] [meta-darwin][PATCH] osx-runtime: OSX Yosemite v10.10

On 08/12/15 16:01, Bystricky, Juro wrote: > yes, I ran into the same libgcc problem, I plan on tackling it eventually. > Likely some paths are not set correctly. > For what is worth, try to build the SDK against the poky "dizzy" branch. > I was able to build Darwin SDK with it. You may need to

Re: [yocto] [meta-chip] Yocto on the 9$ computer

On 10/24/15 15:58, Nicolas Aguirre wrote: > 2015-10-24 19:26 GMT+02:00 Andrei Gherzan : > >> Have a C.H.I.P. 9$ computer? It works with Yocto now. >> >> http://layers.openembedded.org/layerindex/branch/master/layer/meta-chip/ >> > Good job. > IMO it make sense to add C.H.I.P

Re: [yocto] [meta-chip] Yocto on the 9$ computer

On 10/24/15 18:14, Trevor Woerner wrote: > Unfortunately the distinction between SoCs, boards, > MACHINEs, DEFAULTTUNEs, and DISTROs isn't as clear and as clean as one > would like. Oops! The distinction between these ideas is clear, what isn't clear is how to divide them up into lay

Re: [yocto] [linux-yocto] [raspberryp2] Error during the build of linux kernel

On 10/02/15 07:58, Karim ATIKI wrote: > Hello Trevor, > > Thanks for your feedback. > You really think that "Fido" is an older release ? Sorry, I didn't mean to imply it was "old" and therefore should be avoided, I meant to point out that it was something that was released before the switch to

Re: [yocto] Webkit2gtk opengl issue

On 09/23/15 07:53, Mark O'Donovan wrote: > I am working on an am335x based project, with a webkitgtk > program on the screen, displaying a simple webpage. > > I want to use a standard yocto kernel, which I believe > means I must do without the SGX hardware acceleration > until an open-source

Re: [yocto] [meta-raspberrypi] du giving non-integer result?

On 09/23/15 16:12, Andrei Gherzan wrote: > On Thu, Sep 17, 2015 at 02:14:21PM +1000, Jonathan Liu wrote: >> On 11 September 2015 at 11:37, Trevor Woerner <twoer...@gmail.com> wrote: >>> From the feedback, it looks like I'm the only one seeing this issue. >>> That's

[yocto] sunxi mali binary driver

Hello, I'm trying to build an image for my cubietruck that uses the binary accelerated mali driver (sunxi-mali) and have a couple questions. It was my impression that the binary user-space libraries (sunxi-mali?) only work with specific versions of the kernel. By default the cubietruck machine

Re: [yocto] sunxi mali binary driver

Hi Nicolas, On 09/22/15 14:34, Nicolas Aguirre wrote: > 2015-09-22 19:27 GMT+02:00 Trevor Woerner <twoer...@gmail.com>: >> Hello, >> > Hi Trevor, > >> I'm trying to build an image for my cubietruck that uses the binary >> accelerated mali driver (

Re: [yocto] packageconfig for non-autotooled project

On 09/21/15 22:04, 신택현 (Taek Hyun Shin) wrote: > > Create a sunxi-mali_git.bbappend file, to see the pc file of the MESA > Project can be used to manually create a .pc file. > Thanks for your reply. I think this is best fixed in the meta-sunxi layer itself, instead of requiring users to bbappend

[yocto] specify compiler version in recipe

Hello, It looks like I already know the answer to this one... ;-) I'm guessing it isn't possible to specify the compiler version in a recipe? That's probably way too late in the parse stage? There are some vendor Linux kernels for some BSPs that are old enough to pre-date the: fatal error:

[yocto] packageconfig for non-autotooled project

Hello, libepoxy needs its EGL support to have a packageconfig (*.pc) file but the EGL I want to use in my project (meta-sunxi/recipes-graphics/libgles/sunxi-mali_git.bb, which points to gitsm://github.com/linux-sunxi/sunxi-mali.git) isn't autotooled. There are a couple ways around this problem,

Re: [yocto] [OE-core] packageconfig for non-autotooled project

Hey Khem, On 09/21/15 13:03, Khem Raj wrote: > > Look at the patches I have posted for raspberry pi layer > Found them. Awesome, thanks! :-) -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] I hate busybox!

On 09/15/15 13:01, Bob Cochran wrote: > On 09/15/2015 12:38 PM, Romain Perier wrote: >> Hi all, >> >> I disagree, >> Unfortunately some embedded devices in the industry are not like most >> of the tablets and smartphones in the market (no quad or octo cores >> with few GB of ram... and few GB of

Re: [yocto] Dumping sysvinit

On 09/15/15 12:03, Andy Pont wrote: > Mark wrote... > >>> Bit of a newbie question (probably) but what is the easiest way to dump >>> sysvinit and use Busybox init in a core-image-minimal image? >> It has been a while since I've done this. But unless things have changed >> dramatically. You will

Re: [yocto] I hate busybox!

On 09/15/15 04:26, Paul D. DeRocco wrote: > My embedded system has enough room in it for full-featured command line > tools, instead of the wretched busybox. Does the Yocto meta-data include a > layer that provides such tools? Or does OE? And how would I disable > busybox in order to use the

Re: [yocto] I hate busybox!

On 09/15/15 10:47, Trevor Woerner wrote: > The only place busybox (and > toybox) are needed today are in the MMU-less-type systems, such as > Cortex-Ms etc. Actually, the presence or lack of MMU is irrelevant, I meant to single out those systems with limited on-

Re: [yocto] [meta-raspberrypi] rootfs fails

Ah good, someone else is seeing the problems I've been seeing :-) In my case it has nothing to do with anything that I'm adding to my image, it just happens (apparently) randomly. Try building again, it might succeed this time. In my case I'm just building plain old "core-image-minimal" with

Re: [yocto] [meta-raspberrypi] du giving non-integer result?

>From the feedback, it looks like I'm the only one seeing this issue. That's okay, but I'll update this issue with new information in case it's useful to others. Today I also had some other strangeness with the "make sd card image" portion of a build, this time for cubietruck (meta-sunxi):

Re: [yocto] [meta-raspberrypi] du giving non-integer result?

On 09/07/15 03:21, Khem Raj wrote: >> On Sep 6, 2015, at 7:40 PM, Trevor Woerner <twoer...@gmail.com> wrote: >> >> I can't explain why, but when I build "core-image-minimal" for >> MACHINE=raspberrpi2 I get the following SD creation error: >> > wh

[yocto] [meta-raspberrypi] du giving non-integer result?

I can't explain why, but when I build "core-image-minimal" for MACHINE=raspberrpi2 I get the following SD creation error: ERROR: Error: The image creation script '/z/layerindex-master/raspi2/tmp/work/raspberrypi2-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/create_image.rpi-sdimg'

Re: [yocto] [meta-darwin][PATCH] osx-runtime: OSX Yosemite v10.10

On 08/11/15 17:48, Juro Bystricky wrote: Set of patches to allow building against OSX Yosemite v10.10 runtime. Excellent! My build failed, then I noticed your patches. Even with this patch applied, however, my build fails with native-libffi in do_patch. It appears the existing darwinfix.patch

Re: [yocto] [meta-darwin][PATCH] README: steps to create OSX-sdk.zip

On 08/10/15 19:02, Juro Bystricky wrote: osx-runtime requires the file OSX-sdk.zip. This file must be created by the user. This patch describes the typical steps to create this file using a Mac computer. Signed-off-by: Juro Bystricky juro.bystri...@intel.com Excellent, thanks for the

[yocto] [meta-darwin] Re: building an SDK for MacOSX

Hi Richard (and everyone), Any thoughts on this, is my understanding correct? It would be fantastically great if I could generate MacOSX-hosted OE SDKs built on my Linux machine to target embedded ARM boards... it would *really* help sell OE to the people at work :-D On 08/05/15 16:53, Trevor

Re: [yocto] building an SDK for MacOSX

On 08/09/15 19:41, Richard Purdie wrote: On Wed, 2015-08-05 at 16:53 -0400, Trevor Woerner wrote: Hi, I came across RP's meta-darwin today that I'm hoping will enable me to build an OpenEmbedded SDK that can be used by my colleagues who work in a MacOSX environment? Is my understanding

[yocto] ipk zImage in master-next

When packaging a zImage kernel for IPK in master-next the following error shows up: | kernel-image-zImage-4.1.2-fslc+g95d9e15 | *** Error: Package name contains illegal characters, (other than [a-z0-9.+-]) It looks like the newer kernel.bbclass is much more sophisticated about generating

[yocto] building an SDK for MacOSX

Hi, I came across RP's meta-darwin today that I'm hoping will enable me to build an OpenEmbedded SDK that can be used by my colleagues who work in a MacOSX environment? Is my understanding correct? Has anyone tried this lately? The last commit was from almost exactly a year ago. The

Re: [yocto] Selecting different kernel inside an image recipe

Hi Klaus, On 08/04/15 00:15, Klaus Knopper wrote: So, can you confirm that it is not possible to set PREFERRED_PROVIDER_virtual/kernel inside an image recipe? Confirmed, this is not possible. I too thought it would make sense to choose one's kernel based on which image you want to build. I

Re: [yocto] Which repo for meta-altera ?

On 07/30/15 13:02, Khem Raj wrote: On Thu, Jul 30, 2015 at 12:50 AM, Paul Eggleton paul.eggle...@linux.intel.com wrote: (Adding Khem and Yves, the maintainers of the github repo, to CC) In the interests of keeping the layer index accurate, can we get some clarification on which repo is the

Re: [yocto] include all kernel modules in image

On 07/27/15 08:04, Nicolas Dechesne wrote: On Mon, Jul 27, 2015 at 1:03 PM, Trevor Woerner twoer...@gmail.com wrote: are you doing a minimal OE-core build? I'm creating a BSP for the Firefly using vendor-ish u-boot and kernel from: http://wiki.t-firefly.com/index.php/Firefly-RK3288

Re: [yocto] include all kernel modules in image

Hey Nicolas, On 07/27/15 04:50, Nicolas Dechesne wrote: On Sun, Jul 26, 2015 at 8:04 PM, Trevor Woerner twoer...@gmail.com wrote: adding kernel-modules should work. it's a meta package that RDEPENDS on kernel-modules-*, e.g. in my build (oe-core/master) For some reason adding

Re: [yocto] include all kernel modules in image

On 07/27/15 08:04, Nicolas Dechesne wrote: On Mon, Jul 27, 2015 at 1:03 PM, Trevor Woerner twoer...@gmail.com wrote: well, something's definitely wrong here.. are you doing a minimal OE-core build? can you try to reproduce / narrow down? Are you running recent master? I have no idea what

Re: [yocto] include all kernel modules in image

On 07/27/15 08:17, Trevor Woerner wrote: inherit kernel ... DEPENDS = rk2918-tools-native ...and the DEPENDS = needs to be a DEPENDS += since the inherit kernel above already sets a bunch of DEPENDS and if the + isn't used, the recipe loses the DEPENDS on the cross toolchain (for example

Re: [yocto] include all kernel modules in image

Hey Nicolas, Thanks for taking a poke at this and for verifying it should otherwise work ;-) It turns out it was a version issue (as I suspected), the -rc1 should have been in a variable named LINUX_VERSION_EXTENSION leaving the rest in LINUX_VERSION as before: SRC_URI =

[yocto] include all kernel modules in image

Hi, When I build my kernel, in packages-split, I end up with dozens of packages: kernel kernel-base kernel-dev kernel-firmware-boot kernel-firmware-boot2 kernel-firmware-down kernel-firmware-down2 kernel-firmware-down3 kernel-firmware-keyspan-pda

[yocto] [PATCH][meta-yocto] SANITY_TESTED_DISTROS: fix lsb name for openSUSE 13.2

Signed-off-by: Trevor Woerner twoer...@gmail.com --- meta-yocto/conf/distro/poky.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta-yocto/conf/distro/poky.conf b/meta-yocto/conf/distro/poky.conf index e3d3c78..80861f6 100644 --- a/meta-yocto/conf/distro/poky.conf +++ b

Re: [yocto] layerindex

Thanks Nathan and Paul! Any chance the database schema drawing is available somewhere? I'm guessing the machines.layerbranch points to layerItems.id? -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto

[yocto] layerindex

Hi, Does the layer index provide a REST api? -or- Would (could) it be possible to somehow grab/access the data that drives the layer index (preferably without scraping)? Best regards, Trevor -- ___ yocto mailing list yocto@yoctoproject.org

Re: [yocto] overriding equals

On 05/29/15 19:13, Khem Raj wrote: On May 29, 2015, at 2:58 PM, Trevor Woerner twoer...@gmail.com wrote: If a BSP layer sets a preferred kernel using an equals sign (e.g. PREFERRED_PROVIDER_virtual/kernel = linux-raspberrypi) is there any way of overriding this decision that doesn't involve

Re: [yocto] getting started...

Hi Ed, On 05/27/15 16:32, Ed Sutter wrote: This year I have two ongoing iMX6 based linux projects, and may need to use a beaglebone or RPi for some other small project. The point of the above detail is that I'd like to backup a bit and attempt to use Yocto to organize all four of these

[yocto] overriding equals

If a BSP layer sets a preferred kernel using an equals sign (e.g. PREFERRED_PROVIDER_virtual/kernel = linux-raspberrypi) is there any way of overriding this decision that doesn't involve: 1) forking the layer 2) hoping the maintainer accepts a relevant patch 3) creating my own DISTRO ? If I

Re: [yocto] Keybinding on Matchbox, press a key and run an app

Hi Robert, On 05/18/15 13:50, Robert Tulke wrote: Hi i’ve a question, how i can create a keybinding or mapping for a specific key to run an application? So what i want, i’ll press for example F12 and that will start a application? It depends. If you're running a GUI environment with a

Re: [yocto] Question on building out-of-tree modules on the target

Hi Scott, On 05/18/15 10:42, Rifenbark, Scott M wrote: I have a section in the YP Linux Kernel Development Manual that talks about building out-of-tree-modules on the target - Interestingly enough, I was just reading through that document the other day. As soon as I saw a section titled

Re: [yocto] Question on building out-of-tree modules on the target

On 05/29/15 15:28, Nicholas Krause wrote: On May 29, 2015 3:21:04 PM EDT, Trevor Woerner twoer...@gmail.com wrote: If it were me, I'd just remove that section altogether. I'm of the opinion that doing development work on the target is wrong (if for no other reason than to prove your cross

[yocto] [meta-raspberrypi][PATCH] bcm2835: update SRC_URI

It appears as though the location of this tarball has changed. The current SRC_URI works but is redirected to this new location. Signed-off-by: Trevor Woerner twoer...@gmail.com --- recipes-devtools/bcm2835/bcm2835_1.38.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [yocto] Toolchain and SDK

On 05/11/15 03:52, Keskinarkaus, Teemu wrote: I’ve learned that there is command: bitbake image-recipe –c populate_sdk that’ll create the sdk. The thing is that it contains the sysroots, but toolchain is not there. Just to clarify, you're not literally typing bitbake image-recipe -c

Re: [yocto] [oe] Odroid-xu3 support

On 15-05-07 02:56 AM, Christian Ege wrote: From the ODROID family I do only own a ODROID-C1. If there will be a combined Layer for all odroid devices I will port my recipes to this and can help on supporting it. I am mostly interested in Multimedia stuff and I do plan to setup a separate layer

Re: [yocto] bitbake error during image build for VIA Embedded VAB-820 BSP

I tried the build myself, following the instructions to which you linked. There were a couple gotchas along the way (noted, with work-arounds, below [*]), but otherwise the build succeeded. Could you try it again, following the steps exactly, and if it fails again, please list out exactly

Re: [yocto] [oe] Odroid-xu3 support

On 05/06/15 16:24, akuster808 wrote: On 05/06/2015 01:17 PM, Trevor Woerner wrote: It'd be nice if someone could put together one meta-odroid that would support them all ;-) Yep. looking into that. That's great to hear :-D Which device(s) do you have, just the -xu3? My -c1 arrived yesterday

Re: [yocto] [oe] Odroid-xu3 support

On 05/04/15 23:56, akuster808 wrote: I have added support for the Odroid XU3 board. This layer can be found at https://github.com/akuster/meta-odroid. It supports XFCE graphics and has sdcard image support. Sounds great! In addition to your meta-odroid there are also:

Re: [yocto] Replacing HOB in Build Appliance for YP 1.9

On 04/30/15 12:06, Georgescu, Alexandru C wrote: Since HOB is started automatically in BA in order to help users get started quickly with YP, I have the following proposal for updating BA in 1.9 and to replace HOB: ... and updating relevant documentation, such as:

Re: [yocto] creating images which include actively developed applications

On 04/22/15 13:58, Paul Eggleton wrote: Hi Brian, On Wednesday 22 April 2015 15:32:06 Brian Karcz wrote: Is there a way to create a recipe to build actively developed code located in an external source directory? Basically skip the fetch and unpack steps and always execute the compile and

Re: [yocto] Yocto Realtime tests on beaglebone black

Hi Stephen, (replying to really old post, sorry) On 02/10/15 08:06, Stephen Flowers wrote: I have built the realtime kernel using Yocto and deployed on the beaglebone black (specifically core-image-rt-sdk). I'm curious to know how you built your image. When I try bitbake core-image-rt or

[yocto] unpacking poky-dora-10.0.4.tar.bz2

Hi, When I download and unpack poky-dora-10.0.4.tar.bz2 from http://downloads.yoctoproject.org/releases/yocto/yocto-1.5.4/poky-dora-10.0.4.tar.bz2 I end up with a directory called poky-de14d21bc6633ddeb810cef051b91ee322276496 instead of (the expected?) poky-dora-10.0.4. Is this expected? Best

<    1   2   3   4   5   >