Re: [yocto] core-image-minimal-xfce error

Thank you for your answers. I checked out the correct branch of meta-openembedded. Now it is building properly i checked for qemux86 machine, * core-image-minimal-xfce* image builded and working fine. Now i am trying to build for odroid-xu3 board. On Tue, Mar 14, 2017 at 3:35 PM, Burton, Ross

[linux-yocto] [linux-yocto v4.1 1/4] mwifiex: enable MSI interrupt support in pcie

From: Avinash Patil commit 7be0f5b5e169a566be9400481c21de32f147ccbe upstream Newer pcie devices (8897 onwards) support MSI. This patch enables it. Signed-off-by: Avinash Patil Signed-off-by: Amitkumar Karwar Signed-off-by: Kalle

[linux-yocto] [linux-yocto v4.1 3/4] mwifiex: support to set multichannel policy to FW

From: Avinash Patil commit d5b036c403f811c6d1856b8e6891a6438cf56f61 upstream This patch adds support for setting multichannel policy as module parameter to FW. Value of 1 indicates Multichannel support is enabled and value of 0 disables it. Signed-off-by: Avinash Patil

[linux-yocto] [linux-yocto v4.1 0/4] net: mwifiex: Enable the DRCS & MSI support

From: Kevin Hao Hi, This targets on standard/intel/4.1.27/leaf-hill branch. In order to support concurrent AP(5G) and client(2.4G) mode, we need to enable the DRCS(Dynamic Rapid Channel Switching) feature in the Wifi module. Pick up two patches from mainline to enable this

[yocto] Release Candidate Build for yocto-2.3_M3.rc1 now available.

A release candidate build for yocto-2.3_M3.rc1 is now available at: http://autobuilder.yoctoproject.org/pub/releases/yocto-2.3_M3.rc1 Please begin QA on this build as soon as possible. Build hash information: meta-intel : 54df72f06e4a946f4bc403c67313f4cb385b4301 meta-qt4 :

Re: [yocto] Why generated locales does not have .UTF-8 suffix?

Hi Khem, I've tried with the GLIBC_GENERATE_LOCALES variable too but locales are still generated without .utf8 suffix. A little bit of info, locales are working, I can see localized strings. E.g. if I set en_US locale and execute "ls --help" I can see the output of ls in english. If i set

Re: [yocto] make[2]: *** No rule to make target 'fitImage'. Stop.

On Tue, 14 Mar 2017, Belisko Marek wrote: > Hi Robert, > > On Tue, Mar 14, 2017 at 9:16 PM, Robert P. J. Day > wrote: > > On Mon, 13 Mar 2017, Robert P. J. Day wrote: > > > >> > >> i'll start a new thread to focus on just this issue. again, building > >>

Re: [yocto] make[2]: *** No rule to make target 'fitImage'. Stop.

Hi Robert, On Tue, Mar 14, 2017 at 9:16 PM, Robert P. J. Day wrote: > On Mon, 13 Mar 2017, Robert P. J. Day wrote: > >> >> i'll start a new thread to focus on just this issue. again, building >> core-image-minimal for mpc8315e-rdb, adding this to local.conf: >> >>

Re: [yocto] make[2]: *** No rule to make target 'fitImage'. Stop.

On Mon, 13 Mar 2017, Robert P. J. Day wrote: > > i'll start a new thread to focus on just this issue. again, building > core-image-minimal for mpc8315e-rdb, adding this to local.conf: > > INHERIT += "kernel-fitimage" <-- do i need this line? > KERNEL_IMAGETYPES_append = "

Re: [yocto] Why generated locales does not have .UTF-8 suffix?

On 3/14/17 9:50 AM, Fabio Emiliani wrote: > Hi Khem, > > unfortunatly doesn't work. > > The IMAGE_LINGUAS variable can be valorized only with the suffixes of > the locale-base-* packages. As of now my list of locale-base-* packages > for en_US is: > >> locale-base-en-us.iso-8859-1 >>

Re: [yocto] Why generated locales does not have .UTF-8 suffix?

Hi Khem, unfortunatly doesn't work. The IMAGE_LINGUAS variable can be valorized only with the suffixes of the locale-base-* packages. As of now my list of locale-base-* packages for en_US is: locale-base-en-us.iso-8859-1 locale-base-en-us no .utf8 suffix. That's strange, I'm not sure that

Re: [yocto] Why generated locales does not have .UTF-8 suffix?

On 3/14/17 8:36 AM, Fabio Emiliani wrote: > Dear all, > > I've generated several locales specifying, in the local.conf file, the > variable: > >> |IMAGE_LINGUAS = "de-de fr-fr en-gb en-gb.iso-8859-1 en-us >> en-us.iso-8859-1 zh-cn"| > inspecting the target file system, both in:

[yocto] Why generated locales does not have .UTF-8 suffix?

Dear all, I've generated several locales specifying, in the local.conf file, the variable: |IMAGE_LINGUAS = "de-de fr-fr en-gb en-gb.iso-8859-1 en-us en-us.iso-8859-1 zh-cn"| inspecting the target file system, both in: /usr/share/locale and /usr/lib/locale, generated locales does not have

[yocto] suddenly, bunch of circular dependency errors

just updated my poky layer, tried to build core-image-minimal for mpc8315e-rdb, and: ERROR: 171 unbuildable tasks were found. | ETA: 0:00:04 These are usually caused by circular dependencies and any circular dependency chains found will be printed below. Increase the debug level

Re: [yocto] Confusing message

On 14 March 2017 at 06:18, Gary Thomas wrote: > NOTE: Tasks Summary: Attempted 574 tasks of which 507 didn't need to be > rerun and all succeeded. > There were 574 tasks to execute. 507 could be skipped (ie m4:do_fetch :do_unpack :do_patch etc when you already have m4

[yocto] [meta-raspberrypi][morty][PATCH 0/3] Stable branch kernel updates

This series contains backports of patches from Khem's latest combined pull request. I've boot tested a raspberrypi3 (4.4.y and 4.9.y kernels) and a raspberrypi (4.9.y kernel) using these patches and all looks good. Khem Raj (1): linux-raspberrypi_4.9.bb: Update to 4.9.13 Paul Barker (2):

[yocto] [meta-raspberrypi][morty][PATCH 2/3] linux-raspberrypi: Fix uImage build on 4.9.y and later

Signed-off-by: Paul Barker --- recipes-kernel/linux/linux-raspberrypi_4.9.bb | 5 + 1 file changed, 5 insertions(+) diff --git a/recipes-kernel/linux/linux-raspberrypi_4.9.bb b/recipes-kernel/linux/linux-raspberrypi_4.9.bb index 7733bf1..3aba67b 100644 ---

[yocto] [meta-raspberrypi][morty][PATCH 1/3] linux-raspberrypi_4.9.bb: Update to 4.9.13

From: Khem Raj drop upstreamed patch Signed-off-by: Khem Raj --- ...-Add-rules-for-.dtbo-files-for-dts-overla.patch | 29 -- recipes-kernel/linux/linux-raspberrypi_4.9.bb | 5 ++-- 2 files changed, 2 insertions(+), 32

[yocto] [meta-raspberrypi][morty][PATCH 3/3] linux-raspberrypi_4.4: Update to 4.4.50

Signed-off-by: Paul Barker --- recipes-kernel/linux/linux-raspberrypi_4.4.bb | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/recipes-kernel/linux/linux-raspberrypi_4.4.bb b/recipes-kernel/linux/linux-raspberrypi_4.4.bb index b235772..b6be0ec

Re: [yocto] core-image-minimal-xfce error

On 14 March 2017 at 09:20, ravikiran j wrote: > > *ERROR: ExpansionError during parsing > /home/mistral/yocto/poky/meta-openembedded/meta-xfce/recipes-xfce/xfce4-power-manager/xfce4-power-manager_1.6.0.bb > : Failure

Re: [yocto] core-image-minimal-xfce error

Keep things on the list, please. On 14.03.2017 10:49, ravikiran j wrote: The version of xfce-power-manager in the krogoth branch is 1.4.4, not 1.6.0. Probably you are mixing up the revisions. How You are telling that*The version of xfce-power-manager in the krogoth branch is 1.4.4 ? By

Re: [yocto] core-image-minimal-xfce error

On 2017-03-14 10:20, ravikiran j wrote: Hi everybody, I am getting some errors in building of *core-image-minimal-xfce *image. I am using ubuntu 14.04 build system and Yocto 2.1. I added the meta-openembedded layer into poky and configured the bblayers.con ffile as follows.

Re: [yocto] core-image-minimal-xfce error

On 14.03.2017 10:20, ravikiran j wrote: I am using ubuntu 14.04 build system and Yocto 2.1. You probably mean poky/OE 2.1, which is krogoth ERROR: ExpansionError during parsing /home/mistral/yocto/poky/meta-openembedded/meta-xfce/recipes-xfce/xfce4-power-manager/xfce4-power-manager_1.6.0.bb

[yocto] core-image-minimal-xfce error

Hi everybody, I am getting some errors in building of *core-image-minimal-xfce *image. I am using ubuntu 14.04 build system and Yocto 2.1. I added the meta-openembedded layer into poky and configured the bblayers.con ffile as follows. POKY_BBLAYERS_CONF_VERSION = "2" 4 5 BBPATH =

[yocto] R: Autoload kernel module works only once

Thanks Khem for your anwer, The device in question are 2 simple character devices, that just read/write IO registers of the SoC. I don't think they depend on something else, but surely what I've noticed is that first time I power-on the system they're loaded later than successive bootings.

[yocto] Confusing message

Yes, I've seen this for years, but today it bothered me. Exactly how am I to interpret this message from bitbake? NOTE: Tasks Summary: Attempted 574 tasks of which 507 didn't need to be rerun and all succeeded. This was a result of 'bitbake meta-extsdk-toolchain' and I still haven't figured