Re: [yocto] QEMU in SDK

Good day Chong, Thank you so much for your input! I have also tried the ADT method you mentioned and saw the needed files inside download_image. Yet this is not the path I intended to take since in our poky, we already have our own generated images. The output should be like the ADT installer

Re: [yocto] QEMU in SDK

On 07/09/2014 04:27 PM, Joseph Andrew de la Peña wrote: Good day Chong, Thank you so much for your input! I have also tried the ADT method you mentioned and saw the needed files inside download_image. Yet this is not the path I intended to take since in our poky, we already have our own

Re: [yocto] QEMU in SDK

Great! All clear now! Thanks a lot for your help Chong! - Joseph On Wed, Jul 9, 2014 at 4:53 PM, Chong Lu chong...@windriver.com wrote: On 07/09/2014 04:27 PM, Joseph Andrew de la Peña wrote: Good day Chong, Thank you so much for your input! I have also tried the ADT method you

[yocto] automated hardware testing

Hi, I just noticed this [1] and there are rumors that in the next release hardware testing will also work with yocto-autobuilder. I do have a couple of boards deployer in my lab and build with autobuilder images for them. The consoles of my boards are connected via conservers to ethernet and I

[yocto] How to select defconfig for kernel build with yocto/bitbake

Dear all, I work on the process to compile odroid xu kernel with yocto/bitbake In the kernel sources (from hardkernel) I have the corresponding defconfig file, i.e. in the git folder /arch/arm/configs/odroidxu_ubuntu_defconfig. How can I tell bitbake in my recipe to use

Re: [yocto] How to select defconfig for kernel build with yocto/bitbake

Hi Markus, Try adding the following to your recipe file KERNEL_DEFCONFIG = odroidxu_ubuntu_defconfig do_configure_prepend() { install -m 0644 ${S}/arch/${ARCH}/configs/${KERNEL_DEFCONFIG} ${WORKDIR}/defconfig || die No default configuration for ${MACHINE} / ${KERNEL_DEFCONFIG}

[yocto] delete .git and .repo to check in svn

I want to check in yocto sdk on svn. so i am planning to delete all .git and .repo directory from it. Will it create any problem in new build after check out from svn? -- ___ yocto mailing list yocto@yoctoproject.org

[yocto] Installing a directory tree of files into the target filesystem

Hi Guys First post on here :-) I'd like to create a recipe that copies a whole directory tree of files into a directory on the output filesystem. There's nothing to build here... it's just a web application with html files, image files, .js files, etc. What would be the best way of doing

Re: [yocto] How to select defconfig for kernel build with yocto/bitbake

Ok. Can you try the following instead of the content I gave before KERNEL_DEFCONFIG = odroidxu_ubuntu_defconfig kernel_do_configure_append() { install -m 0644 ${S}/arch/${ARCH}/configs/${KERNEL_DEFCONFIG} ${WORKDIR}/defconfig install -m 0644

Re: [yocto] How to select defconfig for kernel build with yocto/bitbake

Sorry, Markus. Ignore my previous post. It has error. I think you need to check the output of bitbake -e recipe name and see how the .config file is created for your recipe. Based on that only we need to update the recipe. Regards, B.Sathish Kumar -Original Message- From: Sathish Kumar

Re: [yocto] How to select defconfig for kernel build with yocto/bitbake

bitbake -e produces the following output. I have listed the methods dealing with .config. do_kernel_configme() { echo [INFO] doing kernel configme export KMETA=${KMETA} if [ -n ${KCONFIG_MODE} ]; then configmeflags=${KCONFIG_MODE} else # If a defconfig was

Re: [yocto] How to select defconfig for kernel build with yocto/bitbake

On 14-07-09 05:38 AM, Dr. Markus Eich wrote: Dear all, I work on the process to compile odroid xu kernel with yocto/bitbake In the kernel sources (from hardkernel) I have the corresponding defconfig file, i.e. in the git folder /arch/arm/configs/odroidxu_ubuntu_defconfig. How can I tell

Re: [yocto] Aarch64 support

Hi Maxin, I have added three folder “meta-aarch64”, “meta-linaro” and “meta-linaro-toolchain” under my poky directory. I also have updated my bblayer.conf with:- BBLAYERS ?= \ /home/atulk/yocto/poky-master/meta \ /home/atulk/yocto/poky-master/meta-yocto \

Re: [yocto] Understanding Package groups

Hi Rudolf, thank you for your explanation. bash has not been installed, but HOB did some changes on the configuration files and I modified the distribution. I deleted everything and created my own image receipe. It works fine now. Regards, Stefan Am 01.07.2014 um 22:34 schrieb Rudolf Streif

Re: [yocto] Installing a directory tree of files into the target filesystem

Hi Joe, First post on here :-) My first post too. I'd like to create a recipe that copies a whole directory tree of files into a directory on the output filesystem. I faced the same problem, and resorted to cp -r (after making sure the directory was there using install -d). In my case, I

Re: [yocto] File system for alternate partition

I'm not sure without digging into it further (which I'm unable to do at the moment, perhaps someone else can.) Just as an FYI for anyone who might find this thread interesting, I fixed the problem by adding another hook into poky/lib/oe/image.py before the IMAGE_CMD hook. It defaults to doing

[yocto] Inadvertent RootFS permission pollution

Hello, I recently ran into a problem where I had trouble determining why the setgid bit was set in my rootfs. It turns out that debian has this bit set on /usr/local (where I was building from), and thus inherited this bit from that directory tree. This surprised me, so I thought I would

Re: [yocto] Inadvertent RootFS permission pollution

On Wed, Jul 9, 2014 at 7:37 AM, Bollinger, Seth seth.bollin...@digi.com wrote: I recently ran into a problem where I had trouble determining why the setgid bit was set in my rootfs. It turns out that debian has this bit set on /usr/local (where I was building from), and thus inherited this

Re: [yocto] Installing a directory tree of files into the target filesystem

Thanks Adam. I don't have any major permissions issues either, so will definitely try that. I assume I could just explicitly set the permissions on the target directory as a later step in do_install if needed. Thanks also for the link. Cheers! Joe On 2014-07-09 14:56, Adam Hughes

[yocto] Oracle Java for ARM?

Hi Guys What's the best way of bringing in Oracle's Java JRE for ARM? The meta-oracle-java layer looks Intel only at the moment :-( Cheers! Joe -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Inadvertent RootFS permission pollution

On 07/09/2014 08:18 AM, Christopher Larson wrote: On Wed, Jul 9, 2014 at 7:37 AM, Bollinger, Seth seth.bollin...@digi.com wrote: I recently ran into a problem where I had trouble determining why the setgid bit was set in my rootfs. It turns out that debian has this bit set on /usr/local

Re: [yocto] Inadvertent RootFS permission pollution

On 7/9/14, 11:46 AM, Saul Wold s...@linux.intel.com wrote: On 07/09/2014 08:18 AM, Christopher Larson wrote: On Wed, Jul 9, 2014 at 7:37 AM, Bollinger, Seth seth.bollin...@digi.com wrote: I recently ran into a problem where I had trouble determining why the setgid bit was set in my rootfs.

[yocto] Environment Variables being unset by bitbake?

I am trying to run java program from a recipe. I get an error that JAVA_HOME is not set. I can verify that JAVA_HOME is set by echo $JAVA_HOME. I can then run the program without issue, but from within a recipe it seems that $JAVA_HOME is unset. I have verified this with 'bbnote java is here:

Re: [yocto] Environment Variables being unset by bitbake?

Oh! I think I know the answer to this one! Check out BB_ENV_EXTRAWHITE at http://www.yoctoproject.org/docs/current/bitbake-user-manual/bitbake-user-manual.html#var-BB_ENV_EXTRAWHITE. If you set that to something like JAVA_HOME, that might do what you want. --wpd On Wed, Jul 9, 2014 at 4:58

[yocto] [meta-security][PATCH] nmap: update to 6.46

Updated to later version on nmap. remove patch which is included in update Added ndiff package Include zenmap build changes but commented out for now and untested Signed-off-by: Armin Kuster akus...@mvista.com --- recipes-security/nmap/files/lua.patch | 79 ---

[yocto] [meta-security][PATCH] pinentry: Fix do_package_qa issue

This fixes; ERROR: QA Issue: pinentry: The compile log indicates that host include and/or library paths were used. Signed-off-by: Armin Kuster akus...@mvista.com --- recipes-security/pinentry/pinentry_0.8.3.bb | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git

[yocto] [meta-security][PATCH] checksec: Add new alsr pic pie test script

Signed-off-by: Armin Kuster akus...@mvista.com --- recipes-security/checksec/checksec_1.5.bb | 16 + recipes-security/checksec/files/checksec.sh | 882 2 files changed, 898 insertions(+) create mode 100644 recipes-security/checksec/checksec_1.5.bb create mode

[yocto] unable to get checksum SRC_URI file could not be found

I am building yocto for freescale imx6sl evolution kit. For checking in source code on svn , i have deleted all .git and .gitignore from the meta directories. Then i have checkout the source code, and tried to build that. While building i am getting the warning Unable to get checksum for rfkill

Re: [yocto] unable to get checksum SRC_URI file could not be found

On 07/10/2014 01:16 PM, jags gediya wrote: I am building yocto for freescale imx6sl evolution kit. For checking in source code on svn , i have deleted all .git and .gitignore from the meta directories. Then i have checkout the source code, and tried to build that. While building i am getting

[linux-yocto] [PATCH 01/17] net: lsi_acp_net: Added new string to DT match

From: Anders Berg anders.b...@lsi.com Add a the vendor prefixed compatible string to the match table. Signed-off-by: Anders Berg anders.b...@lsi.com --- drivers/net/ethernet/lsi/lsi_acp_net.c |3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git

[linux-yocto] [PATCH 03/17] ARM: axxia: Support MSI on both PCIe controllers

From: Anders Berg anders.b...@lsi.com Add support for PCIe MSI on both controllers. On AXM5516, PCIE0 has the ability to signal MSI interrupts on 16 separate lines to the CPU cores, where as PCIE1 only has a single interrupt line that is used for legacy, status/error and MSI. This patch adds MSI

[linux-yocto] [PATCH 04/17] i2c: axxia: Minor cleanup (cosmetic)

From: Anders Berg anders.b...@avagotech.com Remove unused definitions and remove redundant variable. Signed-off-by: Anders Berg anders.b...@avagotech.com --- drivers/i2c/busses/i2c-axxia.c | 27 +++ 1 file changed, 11 insertions(+), 16 deletions(-) diff --git

[linux-yocto] [PATCH 10/17] gpio: pl061: Fix .init section mismatch

From: Anders Berg anders.b...@avagotech.com Signed-off-by: Anders Berg anders.b...@avagotech.com --- drivers/gpio/gpio-pl061.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpio/gpio-pl061.c b/drivers/gpio/gpio-pl061.c index 9d35136..3d0e9fc 100644 ---

[linux-yocto] [PATCH 13/17] powerpc/sysdev/lsi:adding 3500 PCIe inbound mapping support

From: SangeethaRao sangeetha@lsi.com Signed-off-by: SangeethaRao sangeetha@lsi.com --- arch/powerpc/sysdev/lsi_pci.c | 40 +++- 1 file changed, 35 insertions(+), 5 deletions(-) diff --git a/arch/powerpc/sysdev/lsi_pci.c

[linux-yocto] [PATCH 12/17] misc: lsi-smmon: Add parameter panic_on_fatal

From: Anders Berg anders.b...@avagotech.com Added module parameter panic_on_fatal which when set will cause the driver to call panic() when an uncorrectable ECC error is detected. Signed-off-by: Anders Berg anders.b...@avagotech.com --- drivers/misc/lsi-smmon.c | 27

[linux-yocto] [PATCH 14/17] arch/powerpc: Updated Device Trees for Axxia (3400/3500)

From: John Jacques john.jacq...@lsi.com Also added the 6th Core to the Default 3500 Device Tree Signed-off-by: John Jacques john.jacq...@lsi.com --- arch/powerpc/boot/dts/acp342x.dts | 347 +++-- arch/powerpc/boot/dts/acp344x.dts | 164 --

[linux-yocto] [PATCH 11/17] misc: lsi-smmon: Bug when probing with IRQ pending

From: Anders Berg anders.b...@avagotech.com We must not call the ncr_write function to unmask interrupts with the memory controller interrupt enabled, as this could cause the ISR to be invoked before ncr_write has released the lock used to serialize register accesses. To avoid this, temporarily

[linux-yocto] [PATCH 15/17] arch/powerpc: Update the Axxia NAND Driver to support 3500

From: John Jacques john.jacq...@lsi.com The nand driver changes have to support multiple controllers on multiple targets. This is the simplest way I could see to get there. There is a change from using hard coded defines to using the device tree which was required to accomplish this.

[linux-yocto] [PATCH 17/17] arch/powerpc: Reset Updates for Axxia

From: John Jacques john.jacq...@lsi.com Reset support for 3400/2500/3500 got removed when we were porting to Yocto quite some time back. It has never worked since that port. This restores the original reset code require to support reset on 3400/2500/3500. Signed-off-by: John Jacques

[linux-yocto] [PATCH 16/17] kernel/smp: Allow smp_call_function_single() to be called with a function that doesn't return.

From: John Jacques john.jacq...@lsi.com When we do a reset (core, not chip or system), the core that is doing the reset has to tell all the other cores to reset. To do this, we call smp_call_function_single(). In this case the function specified in smp_call_function_single() doesn't return.

Re: [linux-yocto] [PATCH 0/1] meta: iwlwifi: Add MVM firmware support

On 14-07-08 12:11 PM, Darren Hart wrote: Please apply to 3.14 and -dev. Ack'ing this. I was iterating on some LTSI and 3.16 rebasing, but that is almost done now. So this will be added shortly. Bruce -- ___ linux-yocto mailing list