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

[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

[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

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

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] 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] [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] [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

[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-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

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] 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] 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] [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

[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] 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] 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] [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

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] 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

[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] 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

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

; 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] [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

[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

[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

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] [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

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:

[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

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] [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 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 @ 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] [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] [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..

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] [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] [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] [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

Re: [yocto] [PATCH 0/7] introduce rockchip offical linux support to meta-rockchip

Hi Jacob, Sorry for the delay, I hadn't noticed the patches initially because the tag was missing, then I was busy with other things. I'm taking a look at them now. On Thu, Jan 19, 2017 at 10:17 AM, Leon Woestenberg wrote: > Hi Jacob, > > On Thu, Jan 19, 2017 at 11:09 AM,

Re: [yocto] [meta-rockchip][PATCH 2/7] machine: Add machine file for the rk3288 linux Boards

On Fri, Jan 27, 2017 at 9:37 AM, Romain Perier wrote: > Could you: > - Make one patch per new machine file and not one patch for all new added > machine Agreed. Are all of these machines actual devices? The evb one doesn't sound real. Are all of these machines released

Re: [yocto] Delivery Status Notification (Failure)

emote-MTA: dns; mxwcom.263xmail.com. (38.83.106.84, the server for the > domain rock-chips.com.) > Diagnostic-Code: smtp; 550 jacob-c...@rock-chips.com:user not exist > Last-Attempt-Date: Fri, 27 Jan 2017 11:41:36 -0800 (PST) > > > -- Forwarded message -- > From: Tre

Re: [yocto] [meta-rockchip][PATCH 6/7] rk3288.inc: add some variables

Hi Romain, On Fri, Jan 27, 2017 at 10:01 AM, Romain Perier wrote: > Hi all, > > It remembers me a discussion that I wanted to have with Trevor: do we want > specific TUNES (like these ones) in the machines files ? it is distro > specific ? Awesome! I'm happy to see

Re: [yocto] [meta-rockchip][PATCH 4/7] recipes-graphics: Add support for mali-userspace

On Fri, Jan 27, 2017 at 9:41 AM, Romain Perier wrote: > Hi all, > > Correct me if I am wrong, but these are generic mali userpace binaries ? > meta-rockchip is a bsp meta layer, it should only contains files and recipes > to make rockchip board working or things specific

[yocto] [meta-rockchip][PATCH v2 0/5] various updates

message for the image bbclass Trevor Woerner (5): machine: rk3288: enable SoC-specific assignments u-boot-rockchip: add machine: firefly-rk3288: specify bootloader classes: rockchip-gpt-img: add machine: rk3288: GPT image support classes/rockchip-gpt-img.bbclass | 132

Re: [yocto] [meta-rockchip][PATCH 3/3] rockchip-next-img: add image for rockchip next-dev u-boot

On Sat 2017-02-18 @ 06:50:05 PM, Romain Perier wrote: > 1 patch per feature or per different component. So I should get a patch > for rk3288.inc and another one for the class :) I could argue that this is one patch since the only way to flash (for example) the Firefly is to use the image this

[yocto] [meta-rockchip][PATCH v2 4/5] classes: rockchip-gpt-img: add

e.g. the Firefly board). Signed-off-by: Trevor Woerner <twoer...@gmail.com> --- classes/rockchip-gpt-img.bbclass | 132 +++ 1 file changed, 132 insertions(+) create mode 100644 classes/rockchip-gpt-img.bbclass diff --git a/classes/rockchip-gpt-img.bbcl

[yocto] [meta-rockchip][PATCH v2 5/5] machine: rk3288: GPT image support

Configure any rk3288 build to generate the new GPT image which is then either flashed to eMMC or dd'ed to an SDcard. Signed-off-by: Trevor Woerner <twoer...@gmail.com> --- conf/machine/include/rk3288.inc | 3 +++ 1 file changed, 3 insertions(+) diff --git a/conf/machine/include/rk3288

[yocto] [meta-rockchip][PATCH v2 3/5] machine: firefly-rk3288: specify bootloader

Set the default preferred bootloader for firefly-rk3288 to be u-boot-rockchip and set the default name of the SPL binary. Signed-off-by: Trevor Woerner <twoer...@gmail.com> --- conf/machine/firefly-rk3288.conf | 1 + conf/machine/include/rk3288.inc | 3 +++ 2 files changed, 4 inse

[yocto] [meta-rockchip][PATCH v2 2/5] u-boot-rockchip: add

This recipe was taken from the Rockchip team's recipe at https://github.com/rockchip-linux/meta-rockchip/commit/6a139d5b7510c7ba36aace82c239b894d5741cac It was mostly written by Jacob Chen <jacob-c...@iotwrt.com> and I've made a couple small modifications. Signed-off-by: Trevor Woerner

[yocto] [meta-rockchip][PATCH v2 1/5] machine: rk3288: enable SoC-specific assignments

Enable machine overrides for RK3288. Signed-off-by: Trevor Woerner <twoer...@gmail.com> --- conf/machine/include/rk3288.inc | 3 +++ 1 file changed, 3 insertions(+) diff --git a/conf/machine/include/rk3288.inc b/conf/machine/include/rk3288.inc index 86fc567..769e5c1 100644 --- a/conf/m

[yocto] [meta-rockchip][PATCH 3/3] rockchip-next-img: add image for rockchip next-dev u-boot

From: Jacob Chen <jacob-c...@iotwrt.com> Being different from the previous rk-boot which use parameter, next-dev u-boot use gpt partition, so it needs to generate a different image. Reviewed-by: Trevor Woerner <twoer...@gmail.com> Signed-off-by: Jacob Chen <jacob-c...@iotwrt.co

[yocto] [meta-rockchip][PATCH 0/3] firefly gpt emmc update

This set of patches adds to meta-rockchip the ability to create an update image using the latest GPT-style image for flashing to a firefly-rk3288's eMMC. Jacob Chen (2): u-boot-rockchip: add rockchip-next-img: add image for rockchip next-dev u-boot Trevor Woerner (1): remove DEFAULTTUNEs

Re: [yocto] [meta-rockchip][morty][PATHV2 0/6] add main line kernel support

Hi Eddie (and the rest of the Rockchip team), First let me reiterate how happy I am to see that Rockchip is interested in supporting Yocto/OE builds, this is great! I hope this trend continues. Second, thank you so much for your patience while I reviewed these patches. I don't like my review to

[yocto] [meta-rockchip][PATCH 2/3] u-boot-rockchip: add

From: Jacob Chen <jacob-c...@iotwrt.com> Rockchip next-dev U-boot is the next generation of rockchip u-boot, will also be an upstream tracking branch At present, this branch is just a rebased upstream u-boot. Reviewed-by: Trevor Woerner <twoer...@gmail.com> Signed-off-by: Jacob C

Re: [yocto] [meta-rockchip][PATCH v2 1/5] machine: rk3288: enable SoC-specific assignments

<eddie.cai.li...@gmail.com> wrote: > Hi Trevor > > Is this the same one i submit before? > https://www.mail-archive.com/yocto@yoctoproject.org/msg33572.html > > 2017-02-19 10:43 GMT+08:00 Trevor Woerner <twoer...@gmail.com>: >> Enable machine overrides for

Re: [yocto] [meta-rockchip][PATCH v2 2/5] u-boot-rockchip: add

ation from your build? That way I could see what layers you're enabling and at what revisions? Mine is: meta-rockchip = devs/twoerner/feb-updates-2:c252843cf2bf8326ccf2b552b59209f7a2ac3f16 meta = master:def3800c7e58d9d1b54ea1df27b190a0f6d1d544 On Tue, Feb 21, 2017 at 11:01 AM, Trev

Re: [yocto] [meta-rockchip][PATCH v2 4/5] classes: rockchip-gpt-img: add

com>: >> >> Hi all, >> >> >> Eddie Cai wrote on 2017年02月19日 14:32: >> >> Hi Trevor >> >> 2017-02-19 10:43 GMT+08:00 Trevor Woerner <twoer...@gmail.com>: >> > This bbclass was taken from the Rockchip team's work at >> > &

Re: [yocto] [meta-rockchip][PATCH v2 2/5] u-boot-rockchip: add

at 6:14 AM, Eddie Cai <eddie.cai.li...@gmail.com> wrote: > > > 2017-02-19 22:33 GMT+08:00 Eddie Cai <eddie.cai.li...@gmail.com>: >> >> >> >> 2017-02-19 22:22 GMT+08:00 Jacob Chen <jacobchen...@gmail.com>: >>> >>> Hi,

Re: [yocto] [meta-rockchip][morty][PATHV2 0/6] add main line kernel support

Hi Eddie, On Sat, Feb 18, 2017 at 8:42 AM, Eddie Cai wrote: > OK, So We have to set DEFAULTTUNE in conf/local.conf file when we want > to get a optimized build. Absolutely, there's nothing wrong with having that setting :-) --

Re: [yocto] Change ssh key for meta-raspberrypi

On Wed, Feb 15, 2017 at 7:11 PM, Andrei Gherzan wrote: > Who do > I have to talk to get this configured? Michael Halstead (CC'ed) -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-rockchip][morty][PATHV2 0/6] add main line kernel support

Hi Eddie, On Fri 2017-02-17 @ 04:56:28 PM, Eddie Cai wrote: > 2017-02-17 11:33 GMT+08:00 Trevor Woerner <twoer...@gmail.com>: > > You've put "morty" in the subject lines which to me means you're hoping > > these > > patches will be applied against the

Re: [yocto] [OE-core] Patchwork and incoming patch testing

On Wed 2017-01-18 @ 07:05:58 AM, Paul Eggleton wrote: > This should give us a bit more visibility into > where patches are at in the process, although we are still working on a few > places where patch series status needs to be updated (e.g. when a patch goes > into testing). Is the testing

Re: [yocto] [meta-raspberrypi][PATCH v2] linux-raspberrypi-rt: add

Hi Paul, On Thu 2017-01-05 @ 09:59:16 PM, Paul Barker wrote: > Also, are you thinking of moving the -rt recipe to the 4.9 series when > upstream linux-raspberrypi declares that stable? I just want to confirm that 4.9 is going to be the next stable series? How do we know 4.8 isn't going to be the

Re: [yocto] [meta-rockchip][PATCH v4] classes: rockchip-gpt-img: add

Hi Eddie, On Tue 2017-02-28 @ 08:48:16 AM, Eddie Cai wrote: > Could you also copy ${BOOT_IMG} to ${DEPLOY_DIR_IMAGE} . That is much > earier for people find boot image. In case they want to flash boot > partition alone. All of this work is always done in DEPLOY_DIR_IMAGE. $ bitbake

Re: [yocto] [meta-rockchip][PATCH v2 1/5] machine: rk3288: enable SoC-specific assignments

pushed, thanks! On Tue, Feb 21, 2017 at 9:20 PM, Eddie Cai <eddie.cai.li...@gmail.com> wrote: > Hi Trevor > > 2017-02-22 6:25 GMT+08:00 Trevor Woerner <twoer...@gmail.com>: >> >> Almost. The file you created a patch against had DEFAULTTUNE which >> has been

Re: [yocto] [meta-rockchip][PATCH v2 5/5] machine: rk3288: GPT image support

applied, thanks! On Sun, Feb 19, 2017 at 1:33 AM, Eddie Cai <eddie.cai.li...@gmail.com> wrote: > Hi Trevor > > > 2017-02-19 10:43 GMT+08:00 Trevor Woerner <twoer...@gmail.com>: >> >> Configure any rk3288 build to generate the new GPT image which is then &

Re: [yocto] [meta-rockchip][PATCH v2 3/5] machine: firefly-rk3288: specify bootloader

applied, thanks! On Tue, Feb 21, 2017 at 5:22 PM, Trevor Woerner <twoer...@gmail.com> wrote: > Great, thanks for the review! > > On Sun, Feb 19, 2017 at 3:17 AM, Jacob Chen <jacobchen...@gmail.com> wrote: >> Hi Trevor, >> >> 2017-02-19 13:03 GMT+08:00 Eddie

Re: [yocto] [meta-rockchip][PATCH v3] classes: rockchip-gpt-img: add

Oops!! Please ignore, sent wrong file... On Mon, Feb 27, 2017 at 2:15 PM, Trevor Woerner <twoer...@gmail.com> wrote: > This bbclass was taken from the Rockchip team's work at > https://github.com/rockchip-linux/meta-rockchip/commit/53d2e2e474a3014e3013d0059fd1da773fb0e2b7 > It was

[yocto] [meta-rockchip][PATCH v4 0/1] classes: rockchip-gpt-img: add

round, and this new logic does that in a different way and maintains a symlink to the latest Changes since v1: - break large commits into smaller ones - rename the class and improve the commit message Trevor Woerner (1): classes: rockchip-gpt-img: add

[yocto] [meta-rockchip][PATCH v4] classes: rockchip-gpt-img: add

rk3288 SoCs (e.g. the Firefly board). Reviewd-by: Eddie Cai <eddie.cai.li...@gmail.com> Signed-off-by: Jacob Chen <jacob-c...@iotwrt.com> Signed-off-by: Trevor Woerner <twoer...@gmail.com> --- classes/rockchip-gpt-img.bbclass | 133 +++ 1 file chang

[yocto] [meta-rockchip][PATCH v3] classes: rockchip-gpt-img: add

rk3288 SoCs (e.g. the Firefly board). Reviewd-by: Eddie Cai <eddie.cai.li...@gmail.com> Signed-off-by: Jacob Chen <jacob-c...@iotwrt.com> Signed-off-by: Trevor Woerner <twoer...@gmail.com> --- classes/rockchip-gpt-img.bbclass | 132 +++ 1 file chang

[yocto] [meta-rockchip][PATCH v3 0/1] classes: rockchip-gpt-img: add

ntains a symlink to the latest Changes since v1: - break large commits into smaller ones - rename the class and improve the commit message Trevor Woerner (1): classes: rockchip-gpt-img: add classes/rockchip-gpt-img.bbclass | 132 +++

Re: [yocto] [meta-rockchip][PATCH v2 4/5] classes: rockchip-gpt-img: add

> what about use BOOT_IMG = "boot-${MACHINE}-${DATETIME}.img" instead? That > will leave the previous build for debug and avoid trouble. Using boot-${MACHINE}-${DATETIME}.img doesn't work, it leads to the following errors: ERROR: When reparsing

<    1   2   3   4   5   >