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 :-) -- ___ yocto mailing list y

Re: [yocto] Trying to set up a debian package repository for yocto.

Answering my own question: Use PREFERRED_VERSION_gnupg ?= "2.1.11" and IMAGE_INSTALL_append = " gnupg" Apparently, apt-get needs gpgv and apt-key needs gpg, and only gnupg 2.1.11 delivers both. Cheers! Peter. From: yocto-boun...@yoctoproject.org on

[yocto] Trying to set up a debian package repository for yocto.

I'm trying to construct a debian package repository to deploy packages from. I took all the packages from poky/build/tmp/deploy/deb and followed the instructions at: https://wiki.debian.org/SettingUpSignedAptRepositoryWithReprepro SettingUpSignedAptRepositoryWithReprepro - Debian Wiki

[yocto] QA Test Report for Yocto Project Point Release 2.2.1 rc1

Hi Here is the report for Partial QA Cycle on Point Release 2.2.1 rc1 Full Report : https://wiki.yoctoproject.org/wiki/WW07_-_2017-02-13_-_Full_Point_Release_Test_Cycle_2.2.1_rc1 Summary The QA cycle for point release 2.2.1 is complete, 3 new bugs were found none of them is a big blocker. Th

[yocto] [PATCHv2] yocto-compat-layer.py: Add script to YP Compatible Layer validation

The yocto-compat-layer script serves as a tool to validate the alignament of a layer with YP Compatible Layers Programme [1], is based on an RFC sent to the ML to enable automatic testing of layers [2] that wants to be YP Compatible. The tool takes an layer (or set of layers) via command line opti

Re: [yocto] Problem: Installation

On 20 February 2017 at 18:09, SatyaNarayana Sampangi wrote: > Problem Solved, I did not mention the path properly in the S variable, > > I changed, S = "${WORKDIR}/${PN}-${PV}", which works fine. > > Thanks to Ross, for triggering. > That's the default value, so you can just delete your assignme

Re: [yocto] Problem: Installation

Problem Solved, I did not mention the path properly in the S variable, I changed, S = "${WORKDIR}/${PN}-${PV}", which works fine. Thanks to Ross, for triggering. Regards, satya On Mon, Feb 20, 2017 at 11:14 PM, SatyaNarayana Sampangi < satya.2...@gmail.com> wrote: > Hi Ross, > > Thanks for you

[yocto] rpi-basic-image.bb: do_image_ext3 failed

Hi all. I have a problem when build poky (krogoth) for Raspberry PI. When run with : $bitbake rpi-basic-image I got the following errors: ERROR: rpi-basic-image-1.0-r0 do_image_ext3: Function failed: do_image_ext3 (log file is located at /media/oedev/YoctoLearning/build_rpi/tmp/work/raspberrypi-

[yocto] [patchtest-oe][PATCH] tests: modifies pylint check in the test suite

From: Daniela Plascencia Changes pylint's check current logic using dictionaries and sets for easy operations between pretest and test pylint results. The failing message is now formatted so it is easier for the user to locate errors encountered by the check. [YOCTO #10789] Signed-off-by: Danie

Re: [yocto] Problem: Installation

Hi Ross, Thanks for your reply, by the way the tgz contains, hello.c helloprint.c helloprint.h, and moreover I could see in the ${S}, which is suppose to be ~/yocto/poky/build/tmp/work/cortexa8hf-vfp-neon-poky-linux-gnueabi/hellosatya/1.0-r0/hellosatya-1.0 tree hellosatya-1.0/ hellosatya-1.0/

Re: [yocto] [PATCH] yocto-compat-layer.py: Add script to YP Compatible Layer validation

On 02/17/2017 04:41 PM, Christopher Larson wrote: > On Fri, Feb 17, 2017 at 3:39 PM, Christopher Larson > wrote: > >> On Fri, Feb 17, 2017 at 2:26 PM, Aníbal Limón < >> anibal.li...@linux.intel.com> wrote: >> >>> +parser.add_argument('-l', '--layer', metavar='LAYER_DIR', >>> +he

Re: [yocto] Problem: Installation

On 20 February 2017 at 16:30, SatyaNarayana Sampangi wrote: > 14 SRC_URI = "file://hellosatya-1.0.tgz" > 15 > 16 S = "${WORKDIR}" > What files are in the tgz, and where do they expand to? The error says no such file or directory, so presumably it didn't unpack helloprint.c into the work dire

[yocto] Problem: Installation

Dear All, I am newbie to this yocto project. I faced the problem as shown below, solutions will be greatly appreciated. 1. I wrote the .bb file as shown below ---+ 1 SUMMARY = "Simple Hello World Application" 2 3 DESCRIPTION = "A test app

Re: [yocto] Dependence from image type to image recipe

Hello Andrea, On 20/02/17 15:45, Andrea Adami wrote: > > Hello, > I think you have just to adapt to the changes in oe-core [1] > > -recovery-initramfs:do_rootfs \ > +recovery-initramfs:do_image_complete \ > > Cheers > Andrea > > > [1] > http://cgit.openembedded.org/openembedded-cor

[yocto] Unable to read file uImage--ccimx6sbc-id129.dtb

Hi All, I am new to Yocto. I am trying to learn it by actually doing it. Thus my doubt might be naive. I am using Freescale's Connect Core iMX6 Single Board Computer - Version 1 with board ID - 129. I have created distribution by doing bitbake dey-image-qt with following options in local.conf-

Re: [yocto] Dependence from image type to image recipe

On Mon, Feb 20, 2017 at 1:40 PM, Viguera, Javier wrote: > Hi all, > > > > I need a bit of help to add a dependence from an image type to an image > recipe that build and initramfs. > > > > A bit of background: I have an image type recovery.ubifs that boots using a > ramdisk. The ramdisk is generat

[yocto] Dependence from image type to image recipe

Hi all, I need a bit of help to add a dependence from an image type to an image recipe that build and initramfs. A bit of background: I have an image type recovery.ubifs that boots using a ramdisk. The ramdisk is generated with a different image recipe (recovery-initramfs). So whenever I conf

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

2017-02-19 22:33 GMT+08:00 Eddie Cai : > > > 2017-02-19 22:22 GMT+08:00 Jacob Chen : > >> Hi, >> >> 2017-02-19 10:43 GMT+08:00 Trevor Woerner : >> > This recipe was taken from the Rockchip team's recipe at >> > https://github.com/rockchip-linux/meta-rockchip/commit/6a139 >> d5b7510c7ba36aace82c239