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

2017-03-14 Thread ravikiran j 
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  wrote:

>
> 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 expanding variable
>> PACKAGECONFIG, expression was ${@bb.utils.filter('DISTRO_FEATURES',
>> 'systemd', d)} which triggered exception AttributeError: 'module' object
>> has no attribute 'filter'*
>
>
> This error message tells me that you're using meta-openembedded master,
> not krogoth.  Checkout the correct branch of meta-openembedded.
>
> Ross
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2017-03-14 Thread Kevin Hao 
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 Valo 
[Kevin: replace mwifiex_dbg() with pr_debug()]
Signed-off-by: Kevin Hao 
---
 drivers/net/wireless/mwifiex/pcie.c | 32 +---
 drivers/net/wireless/mwifiex/pcie.h |  1 +
 2 files changed, 26 insertions(+), 7 deletions(-)

diff --git a/drivers/net/wireless/mwifiex/pcie.c 
b/drivers/net/wireless/mwifiex/pcie.c
index bcc7751d883c..dab899d48236 100644
--- a/drivers/net/wireless/mwifiex/pcie.c
+++ b/drivers/net/wireless/mwifiex/pcie.c
@@ -2538,6 +2538,30 @@ static void mwifiex_pcie_cleanup(struct mwifiex_adapter 
*adapter)
kfree(card);
 }
 
+static int mwifiex_pcie_request_irq(struct mwifiex_adapter *adapter)
+{
+   int ret;
+   struct pcie_service_card *card = adapter->card;
+   struct pci_dev *pdev = card->dev;
+
+   if (pci_enable_msi(pdev) != 0)
+   pci_disable_msi(pdev);
+   else
+   card->msi_enable = 1;
+
+   pr_debug("msi_enable = %d\n", card->msi_enable);
+
+   ret = request_irq(pdev->irq, mwifiex_pcie_interrupt, IRQF_SHARED,
+ "MRVL_PCIE", pdev);
+   if (ret) {
+   pr_err("request_irq failed: ret=%d\n", ret);
+   adapter->card = NULL;
+   return -1;
+   }
+
+   return 0;
+}
+
 /*
  * This function registers the PCIE device.
  *
@@ -2545,20 +2569,14 @@ static void mwifiex_pcie_cleanup(struct mwifiex_adapter 
*adapter)
  */
 static int mwifiex_register_dev(struct mwifiex_adapter *adapter)
 {
-   int ret;
struct pcie_service_card *card = adapter->card;
struct pci_dev *pdev = card->dev;
 
/* save adapter pointer in card */
card->adapter = adapter;
 
-   ret = request_irq(pdev->irq, mwifiex_pcie_interrupt, IRQF_SHARED,
- "MRVL_PCIE", pdev);
-   if (ret) {
-   pr_err("request_irq failed: ret=%d\n", ret);
-   adapter->card = NULL;
+   if (mwifiex_pcie_request_irq(adapter))
return -1;
-   }
 
adapter->dev = >dev;
adapter->tx_buf_size = card->pcie.tx_buf_size;
diff --git a/drivers/net/wireless/mwifiex/pcie.h 
b/drivers/net/wireless/mwifiex/pcie.h
index 0e7ee8b72358..78e3a0aa68ee 100644
--- a/drivers/net/wireless/mwifiex/pcie.h
+++ b/drivers/net/wireless/mwifiex/pcie.h
@@ -284,6 +284,7 @@ struct pcie_service_card {
dma_addr_t sleep_cookie_pbase;
void __iomem *pci_mmap;
void __iomem *pci_mmap1;
+   int msi_enable;
 };
 
 static inline int
-- 
2.9.3

-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

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

2017-03-14 Thread Kevin Hao 
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 
Signed-off-by: Kalle Valo 
---
 drivers/net/wireless/mwifiex/fw.h  |  8 
 drivers/net/wireless/mwifiex/sta_cmd.c | 31 ++
 drivers/net/wireless/mwifiex/sta_cmdresp.c |  1 +
 3 files changed, 40 insertions(+)

diff --git a/drivers/net/wireless/mwifiex/fw.h 
b/drivers/net/wireless/mwifiex/fw.h
index 59d8964dd0dc..1b3b24a3d857 100644
--- a/drivers/net/wireless/mwifiex/fw.h
+++ b/drivers/net/wireless/mwifiex/fw.h
@@ -197,6 +197,7 @@ enum MWIFIEX_802_11_PRIVACY_FILTER {
 
 #define ISSUPP_11NENABLED(FwCapInfo) (FwCapInfo & BIT(11))
 #define ISSUPP_TDLS_ENABLED(FwCapInfo) (FwCapInfo & BIT(14))
+#define ISSUPP_DRCS_ENABLED(FwCapInfo) (FwCapInfo & BIT(15))
 #define ISSUPP_SDIO_SPA_ENABLED(FwCapInfo) (FwCapInfo & BIT(16))
 
 #define MWIFIEX_DEF_HT_CAP (IEEE80211_HT_CAP_DSSSCCK40 | \
@@ -353,6 +354,7 @@ enum MWIFIEX_802_11_PRIVACY_FILTER {
 #define HostCmd_CMD_MGMT_FRAME_REG0x010c
 #define HostCmd_CMD_REMAIN_ON_CHAN0x010d
 #define HostCmd_CMD_11AC_CFG 0x0112
+#define HostCmd_CMD_MC_POLICY 0x0121
 #define HostCmd_CMD_TDLS_OPER 0x0122
 #define HostCmd_CMD_SDIO_SP_RX_AGGR_CFG   0x0223
 
@@ -1908,6 +1910,11 @@ struct host_cmd_ds_coalesce_cfg {
struct coalesce_receive_filt_rule rule[0];
 } __packed;
 
+struct host_cmd_ds_multi_chan_policy {
+   __le16 action;
+   __le16 policy;
+} __packed;
+
 struct host_cmd_ds_command {
__le16 command;
__le16 size;
@@ -1973,6 +1980,7 @@ struct host_cmd_ds_command {
struct host_cmd_ds_tdls_oper tdls_oper;
struct host_cmd_ds_chan_rpt_req chan_rpt_req;
struct host_cmd_sdio_sp_rx_aggr_cfg sdio_rx_aggr_cfg;
+   struct host_cmd_ds_multi_chan_policy mc_policy;
} params;
 } __packed;
 
diff --git a/drivers/net/wireless/mwifiex/sta_cmd.c 
b/drivers/net/wireless/mwifiex/sta_cmd.c
index 49422f2a5380..f58c5d999876 100644
--- a/drivers/net/wireless/mwifiex/sta_cmd.c
+++ b/drivers/net/wireless/mwifiex/sta_cmd.c
@@ -26,6 +26,10 @@
 #include "11n.h"
 #include "11ac.h"
 
+static bool drcs;
+module_param(drcs, bool, 0644);
+MODULE_PARM_DESC(drcs, "multi-channel operation:1, single-channel 
operation:0");
+
 static bool disable_auto_ds;
 module_param(disable_auto_ds, bool, 0);
 MODULE_PARM_DESC(disable_auto_ds,
@@ -1480,6 +1484,22 @@ static int mwifiex_cmd_cfg_data(struct mwifiex_private 
*priv,
 }
 
 static int
+mwifiex_cmd_set_mc_policy(struct mwifiex_private *priv,
+ struct host_cmd_ds_command *cmd,
+ u16 cmd_action, void *data_buf)
+{
+   struct host_cmd_ds_multi_chan_policy *mc_pol = >params.mc_policy;
+   const u16 *drcs_info = data_buf;
+
+   mc_pol->action = cpu_to_le16(cmd_action);
+   mc_pol->policy = cpu_to_le16(*drcs_info);
+   cmd->command = cpu_to_le16(HostCmd_CMD_MC_POLICY);
+   cmd->size = cpu_to_le16(sizeof(struct host_cmd_ds_multi_chan_policy) +
+   S_DS_GEN);
+   return 0;
+}
+
+static int
 mwifiex_cmd_coalesce_cfg(struct mwifiex_private *priv,
 struct host_cmd_ds_command *cmd,
 u16 cmd_action, void *data_buf)
@@ -1931,6 +1951,10 @@ int mwifiex_sta_prepare_cmd(struct mwifiex_private 
*priv, uint16_t cmd_no,
ret = mwifiex_cmd_sdio_rx_aggr_cfg(cmd_ptr, cmd_action,
   data_buf);
break;
+   case HostCmd_CMD_MC_POLICY:
+   ret = mwifiex_cmd_set_mc_policy(priv, cmd_ptr, cmd_action,
+   data_buf);
+   break;
default:
dev_err(priv->adapter->dev,
"PREP_CMD: unknown cmd- %#x\n", cmd_no);
@@ -2047,6 +2071,13 @@ int mwifiex_sta_init_cmd(struct mwifiex_private *priv, 
u8 first_sta, bool init)
if (ret)
return -1;
}
+
+   if (ISSUPP_DRCS_ENABLED(adapter->fw_cap_info))
+   ret = mwifiex_send_cmd(priv, HostCmd_CMD_MC_POLICY,
+  HostCmd_ACT_GEN_SET, 0, ,
+  true);
+   if (ret)
+   return -1;
}
 
/* get tx rate */
diff --git a/drivers/net/wireless/mwifiex/sta_cmdresp.c 
b/drivers/net/wireless/mwifiex/sta_cmdresp.c
index 88dc6b672ef4..e3b7b6adfe69 100644
--- a/drivers/net/wireless/mwifiex/sta_cmdresp.c
+++

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

2017-03-14 Thread Kevin Hao 
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 feature. The other two patches are for the
MSI interrupt support.

Avinash Patil (3):
  mwifiex: enable MSI interrupt support in pcie
  mwifiex: support to set multichannel policy to FW
  mwifiex: advertise multichannel support to cfg80211

Shengzhen Li (1):
  mwifiex: fix interrupt processing corner case in MSI mode

 drivers/net/wireless/mwifiex/cfg80211.c| 14 +-
 drivers/net/wireless/mwifiex/fw.h  |  8 +++
 drivers/net/wireless/mwifiex/main.h|  1 +
 drivers/net/wireless/mwifiex/pcie.c| 81 ++
 drivers/net/wireless/mwifiex/pcie.h|  1 +
 drivers/net/wireless/mwifiex/sta_cmd.c | 36 +
 drivers/net/wireless/mwifiex/sta_cmdresp.c |  1 +
 7 files changed, 130 insertions(+), 12 deletions(-)

-- 
2.9.3

-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

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

2017-03-14 Thread Poky Build User 

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 : 2c7f8df9039be498f8a2232d1428adb7f4e5e800 
meta-mingw : b4ef177e6ebdc0aded3e202e0decbf1cb21c73dd 
meta-qt3 : f33b73a9563f2dfdfd0ee37b61d65d90197a456f 
meta-gplv2 : de001bd6bfcec943d274b649c62be6848cc9c3e6 
poky : 6e20b31d5d17133e0fca086e12a0ad06ab5c4cc8 

\nThis is an automated message from\nThe Yocto Project Autobuilder\nGit: 
git://git.yoctoproject.org/yocto-autobuilder\nEmail: joshua.g.l...@intel.com 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2017-03-14 Thread Fabio Emiliani 

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 zh_CN (chinese) locale and execute "ls 
--help" I can see the output of ls in chinese.


The problem is realted to the encoding of a locale. Until now I have not 
found any way to generate an UTF-8 locale.


Since the encoding is not specified in the file name, how can I check 
the encoding of a locale called "en_US"?


Best regards,

Fabio Emiliani

Il 14/03/2017 18:00, Khem Raj ha scritto:


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
locale-base-en-us

no .utf8 suffix. That's strange, I'm not sure that the en_US locale I've
generated supports UTF-8 encoding.

does this help ?

GLIBC_GENERATE_LOCALES = "de_DE en_US de_DE.UTF-8 en_US.UTF-8"
IMAGE_LINGUAS = "de-de en-us"



I've just opened a bug on bugzilla:


https://bugzilla.yoctoproject.org/show_bug.cgi?id=11153

Any other ideas?

Thanks in advance for your time

Best regards,

Fabio Emiliani

Il 14/03/2017 17:39, Khem Raj ha scritto:

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: /usr/share/locale and
/usr/lib/locale, generated locales does not have the .UTF-8 suffix.


Perhaps adding en-gb.utf8 to IMAGE_LINGUAS might help you.


See:


|/usr/share/locale/ drwxr-xr-x 6 root root 416 Nov 17 2016 . drwxr-xr-x
30 root root 2056 Nov 17 2016 .. drwxr-xr-x 4 root root 296 Nov 17
2016 de drwxr-xr-x 3 root root 232 Nov 17 2016 en_GB drwxr-xr-x 4 root
root 296 Nov 17 2016 fr drwxr-xr-x 4 root root 296 Nov 17 2016 zh_CN|

|and|

||


|/usr/lib/locale/ drwxr-xr-x 9 root root 640 Mar 13 2017 . drwxr-xr-x
32 root root 4 Mar 13 2017 .. drwxr-xr-x 3 root root 1016 Mar 13
2017 de_DE drwxr-xr-x 3 root root 1016 Mar 13 2017 en_GB drwxr-xr-x 3
root root 1016 Mar 13 2017 en_GB.ISO-8859-1 drwxr-xr-x 3 root root
1016 Mar 13 2017 en_US drwxr-xr-x 3 root root 1016 Mar 13 2017
en_US.ISO-8859-1 drwxr-xr-x 3 root root 1016 Mar 13 2017 fr_FR
drwxr-xr-x 3 root root 1016 Mar 13 2017 zh_CN|

What is the character encoding of the following locales: de_DE, en_GB,
en_US, fr_FR, zh_CN?

Thanks in advance for your time

Best regards,

Fabio Emiliani

--

*Fabio Emiliani*

*/Software Engineer/*

/Ph. +39 075 8298 530  /

/fabio.emili...@artgroup-spa.com/ 

DISCLAIMER
This email and any attachment may contain confidential information. If
you are not the intended recipient you are not authorised to copy or
disclose all or any part of it without the prior written consent of ART SpA.

  


/ART SpA – Step Forward With US - //www.artgroup-spa.com/logo_ART_firma-1//

/Ph. +39 075 8298 501 – Fax +39 075 8298 525 /

P*Please consider our environment  before printing this e-mail***

  





--

*Fabio Emiliani*

*/Software Engineer/*

/Ph. +39 075 8298 530  /

/fabio.emili...@artgroup-spa.com/ 

DISCLAIMER
This email and any attachment may contain confidential information. If
you are not the intended recipient you are not authorised to copy or
disclose all or any part of it without the prior written consent of ART SpA.

  


/ART SpA – Step Forward With US - //www.artgroup-spa.com/logo_ART_firma-1//

/Ph. +39 075 8298 501 – Fax +39 075 8298 525 /

P*Please consider our environment  before printing this e-mail***

  



--

*Fabio Emiliani*

*/Software Engineer/*

/Ph. +39 075 8298 530 /

/fabio.emili...@artgroup-spa.com/ 

DISCLAIMER
This email and any attachment may contain confidential information. If 
you are not the intended recipient you are not authorised to copy or 
disclose all or any part of it without the prior written consent of ART SpA.


/ART SpA – Step Forward With US - //www.artgroup-spa.com/logo_ART_firma-1//

/Ph. +39 075 8298 501 – Fax +39 075 8298 525 /

P*Please consider our environment  before printing this e-mail***

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2017-03-14 Thread Robert P. J. Day 
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
> >> core-image-minimal for mpc8315e-rdb, adding this to local.conf:
> >>
> >>   INHERIT += "kernel-fitimage" <-- do i need this line?
> >>   KERNEL_IMAGETYPES_append = " fitImage"
> >>
> >> anyway, run:
> >>
> >>   $ bitbake virtual/kernel
> >>
> >> and eventually get:
> >>
> >>   make[2]: *** No rule to make target 'fitImage'.  Stop.
> >
> > ... snip ...
> >
> >   i would still love to figure out how to generate a simple FIT image
> > when building core-image-minimal for mpc8315e-rdb.
> >
> >   first, based on what i read, my first attempt was to add the
> > following line to local.conf:
> >
> >   KERNEL_IMAGETYPES_append = " fitImage"
> You need probably also add:
>
> KERNEL_CLASSES += "kernel-fitimage"
>
> to local.conf

  that *appears* to have solved the problem ... so why is it i didn't
realize that? where is that written up that i somehow missed it?

  and would it not make sense that selecting FIT image in one variable
should automatically set the other required variables?

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday


-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2017-03-14 Thread Belisko Marek 
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:
>>
>>   INHERIT += "kernel-fitimage" <-- do i need this line?
>>   KERNEL_IMAGETYPES_append = " fitImage"
>>
>> anyway, run:
>>
>>   $ bitbake virtual/kernel
>>
>> and eventually get:
>>
>>   make[2]: *** No rule to make target 'fitImage'.  Stop.
>
> ... snip ...
>
>   i would still love to figure out how to generate a simple FIT image
> when building core-image-minimal for mpc8315e-rdb.
>
>   first, based on what i read, my first attempt was to add the
> following line to local.conf:
>
>   KERNEL_IMAGETYPES_append = " fitImage"
You need probably also add:

KERNEL_CLASSES += "kernel-fitimage"

to local.conf
>
> however:
>
>   $ bitbake virtual/kernel
>
>   ... snip ...
>
>   | NOTE: make -j 8 HOSTCC=gcc  HOSTCPP=gcc  -E uImage
>   CC=powerpc-poky-linux-gcc  -fuse-ld=bfd LD=powerpc-poky-linux-ld.bfd
>   | NOTE: make -j 8 HOSTCC=gcc  HOSTCPP=gcc  -E fitImage
>   CC=powerpc-poky-linux-gcc  -fuse-ld=bfd LD=powerpc-poky-linux-ld.bfd
>
>   ... snip ...
>
>   | make[2]: *** No rule to make target 'fitImage'.  Stop.
>   | Makefile:150: recipe for target 'sub-make' failed
>   | make[1]: *** [sub-make] Error 2
>   | Makefile:24: recipe for target '__sub-make' failed
>   | make: *** [__sub-make] Error 2
>
> which makes sense since there is no such target, "fitImage", in the
> kernel build structure.
>
>   what am i screwing up here? how do i generate a simple FIT image?
>
> rday
>
> --
>
> 
> Robert P. J. Day Ottawa, Ontario, CANADA
> http://crashcourse.ca
>
> Twitter:   http://twitter.com/rpjday
> LinkedIn:   http://ca.linkedin.com/in/rpjday
> 
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

BR,

marek

-- 
as simple and primitive as possible
-
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web: http://open-nandra.com
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2017-03-14 Thread Robert P. J. Day 
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 = " fitImage"
>
> anyway, run:
>
>   $ bitbake virtual/kernel
>
> and eventually get:
>
>   make[2]: *** No rule to make target 'fitImage'.  Stop.

... snip ...

  i would still love to figure out how to generate a simple FIT image
when building core-image-minimal for mpc8315e-rdb.

  first, based on what i read, my first attempt was to add the
following line to local.conf:

  KERNEL_IMAGETYPES_append = " fitImage"

however:

  $ bitbake virtual/kernel

  ... snip ...

  | NOTE: make -j 8 HOSTCC=gcc  HOSTCPP=gcc  -E uImage
  CC=powerpc-poky-linux-gcc  -fuse-ld=bfd LD=powerpc-poky-linux-ld.bfd
  | NOTE: make -j 8 HOSTCC=gcc  HOSTCPP=gcc  -E fitImage
  CC=powerpc-poky-linux-gcc  -fuse-ld=bfd LD=powerpc-poky-linux-ld.bfd

  ... snip ...

  | make[2]: *** No rule to make target 'fitImage'.  Stop.
  | Makefile:150: recipe for target 'sub-make' failed
  | make[1]: *** [sub-make] Error 2
  | Makefile:24: recipe for target '__sub-make' failed
  | make: *** [__sub-make] Error 2

which makes sense since there is no such target, "fitImage", in the
kernel build structure.

  what am i screwing up here? how do i generate a simple FIT image?

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday


-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2017-03-14 Thread Khem Raj 


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
>> locale-base-en-us
> no .utf8 suffix. That's strange, I'm not sure that the en_US locale I've
> generated supports UTF-8 encoding.

does this help ?

GLIBC_GENERATE_LOCALES = "de_DE en_US de_DE.UTF-8 en_US.UTF-8"
IMAGE_LINGUAS = "de-de en-us"


> 
> I've just opened a bug on bugzilla:
> 
>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=11153
> 
> Any other ideas?
> 
> Thanks in advance for your time
> 
> Best regards,
> 
> Fabio Emiliani
> 
> Il 14/03/2017 17:39, Khem Raj ha scritto:
>>
>> 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: /usr/share/locale and
>>> /usr/lib/locale, generated locales does not have the .UTF-8 suffix.
>>>
>> Perhaps adding en-gb.utf8 to IMAGE_LINGUAS might help you.
>>
>>> See:
>>>
 |/usr/share/locale/ drwxr-xr-x 6 root root 416 Nov 17 2016 . drwxr-xr-x
 30 root root 2056 Nov 17 2016 .. drwxr-xr-x 4 root root 296 Nov 17
 2016 de drwxr-xr-x 3 root root 232 Nov 17 2016 en_GB drwxr-xr-x 4 root
 root 296 Nov 17 2016 fr drwxr-xr-x 4 root root 296 Nov 17 2016 zh_CN|
>>> |and|
>>>
>>> ||
>>>
 |/usr/lib/locale/ drwxr-xr-x 9 root root 640 Mar 13 2017 . drwxr-xr-x
 32 root root 4 Mar 13 2017 .. drwxr-xr-x 3 root root 1016 Mar 13
 2017 de_DE drwxr-xr-x 3 root root 1016 Mar 13 2017 en_GB drwxr-xr-x 3
 root root 1016 Mar 13 2017 en_GB.ISO-8859-1 drwxr-xr-x 3 root root
 1016 Mar 13 2017 en_US drwxr-xr-x 3 root root 1016 Mar 13 2017
 en_US.ISO-8859-1 drwxr-xr-x 3 root root 1016 Mar 13 2017 fr_FR
 drwxr-xr-x 3 root root 1016 Mar 13 2017 zh_CN|
>>> What is the character encoding of the following locales: de_DE, en_GB,
>>> en_US, fr_FR, zh_CN?
>>>
>>> Thanks in advance for your time
>>>
>>> Best regards,
>>>
>>> Fabio Emiliani
>>>
>>> -- 
>>>
>>> *Fabio Emiliani*
>>>
>>> */Software Engineer/*
>>>
>>> /Ph. +39 075 8298 530  /
>>>
>>> /fabio.emili...@artgroup-spa.com/ 
>>>
>>> DISCLAIMER
>>> This email and any attachment may contain confidential information. If
>>> you are not the intended recipient you are not authorised to copy or
>>> disclose all or any part of it without the prior written consent of ART SpA.
>>>
>>>  
>>>
>>> /ART SpA – Step Forward With US - //www.artgroup-spa.com/logo_ART_firma-1//
>>>
>>> /Ph. +39 075 8298 501 – Fax +39 075 8298 525 /
>>>
>>> P*Please consider our environment  before printing this e-mail***
>>>
>>>  
>>>
>>>
>>>
> 
> -- 
> 
> *Fabio Emiliani*
> 
> */Software Engineer/*
> 
> /Ph. +39 075 8298 530  /
> 
> /fabio.emili...@artgroup-spa.com/ 
> 
> DISCLAIMER
> This email and any attachment may contain confidential information. If
> you are not the intended recipient you are not authorised to copy or
> disclose all or any part of it without the prior written consent of ART SpA.
> 
>  
> 
> /ART SpA – Step Forward With US - //www.artgroup-spa.com/logo_ART_firma-1//
> 
> /Ph. +39 075 8298 501 – Fax +39 075 8298 525 /
> 
> P*Please consider our environment  before printing this e-mail***
> 
>  
> 



signature.asc
Description: OpenPGP digital signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2017-03-14 Thread Fabio Emiliani 

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 the en_US locale I've 
generated supports UTF-8 encoding.


I've just opened a bug on bugzilla:


https://bugzilla.yoctoproject.org/show_bug.cgi?id=11153


Any other ideas?

Thanks in advance for your time

Best regards,

Fabio Emiliani

Il 14/03/2017 17:39, Khem Raj ha scritto:


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: /usr/share/locale and
/usr/lib/locale, generated locales does not have the .UTF-8 suffix.


Perhaps adding en-gb.utf8 to IMAGE_LINGUAS might help you.


See:


|/usr/share/locale/ drwxr-xr-x 6 root root 416 Nov 17 2016 . drwxr-xr-x
30 root root 2056 Nov 17 2016 .. drwxr-xr-x 4 root root 296 Nov 17
2016 de drwxr-xr-x 3 root root 232 Nov 17 2016 en_GB drwxr-xr-x 4 root
root 296 Nov 17 2016 fr drwxr-xr-x 4 root root 296 Nov 17 2016 zh_CN|

|and|

||


|/usr/lib/locale/ drwxr-xr-x 9 root root 640 Mar 13 2017 . drwxr-xr-x
32 root root 4 Mar 13 2017 .. drwxr-xr-x 3 root root 1016 Mar 13
2017 de_DE drwxr-xr-x 3 root root 1016 Mar 13 2017 en_GB drwxr-xr-x 3
root root 1016 Mar 13 2017 en_GB.ISO-8859-1 drwxr-xr-x 3 root root
1016 Mar 13 2017 en_US drwxr-xr-x 3 root root 1016 Mar 13 2017
en_US.ISO-8859-1 drwxr-xr-x 3 root root 1016 Mar 13 2017 fr_FR
drwxr-xr-x 3 root root 1016 Mar 13 2017 zh_CN|

What is the character encoding of the following locales: de_DE, en_GB,
en_US, fr_FR, zh_CN?

Thanks in advance for your time

Best regards,

Fabio Emiliani

--

*Fabio Emiliani*

*/Software Engineer/*

/Ph. +39 075 8298 530  /

/fabio.emili...@artgroup-spa.com/ 

DISCLAIMER
This email and any attachment may contain confidential information. If
you are not the intended recipient you are not authorised to copy or
disclose all or any part of it without the prior written consent of ART SpA.

  


/ART SpA – Step Forward With US - //www.artgroup-spa.com/logo_ART_firma-1//

/Ph. +39 075 8298 501 – Fax +39 075 8298 525 /

P*Please consider our environment  before printing this e-mail***

  






--

*Fabio Emiliani*

*/Software Engineer/*

/Ph. +39 075 8298 530 /

/fabio.emili...@artgroup-spa.com/ 

DISCLAIMER
This email and any attachment may contain confidential information. If 
you are not the intended recipient you are not authorised to copy or 
disclose all or any part of it without the prior written consent of ART SpA.


/ART SpA – Step Forward With US - //www.artgroup-spa.com/logo_ART_firma-1//

/Ph. +39 075 8298 501 – Fax +39 075 8298 525 /

P*Please consider our environment  before printing this e-mail***

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2017-03-14 Thread Khem Raj 


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: /usr/share/locale and
> /usr/lib/locale, generated locales does not have the .UTF-8 suffix.
> 

Perhaps adding en-gb.utf8 to IMAGE_LINGUAS might help you.

> See:
> 
>> |/usr/share/locale/ drwxr-xr-x 6 root root 416 Nov 17 2016 . drwxr-xr-x
>> 30 root root 2056 Nov 17 2016 .. drwxr-xr-x 4 root root 296 Nov 17
>> 2016 de drwxr-xr-x 3 root root 232 Nov 17 2016 en_GB drwxr-xr-x 4 root
>> root 296 Nov 17 2016 fr drwxr-xr-x 4 root root 296 Nov 17 2016 zh_CN|
> |and|
> 
> ||
> 
>> |/usr/lib/locale/ drwxr-xr-x 9 root root 640 Mar 13 2017 . drwxr-xr-x
>> 32 root root 4 Mar 13 2017 .. drwxr-xr-x 3 root root 1016 Mar 13
>> 2017 de_DE drwxr-xr-x 3 root root 1016 Mar 13 2017 en_GB drwxr-xr-x 3
>> root root 1016 Mar 13 2017 en_GB.ISO-8859-1 drwxr-xr-x 3 root root
>> 1016 Mar 13 2017 en_US drwxr-xr-x 3 root root 1016 Mar 13 2017
>> en_US.ISO-8859-1 drwxr-xr-x 3 root root 1016 Mar 13 2017 fr_FR
>> drwxr-xr-x 3 root root 1016 Mar 13 2017 zh_CN|
> What is the character encoding of the following locales: de_DE, en_GB,
> en_US, fr_FR, zh_CN?
> 
> Thanks in advance for your time
> 
> Best regards,
> 
> Fabio Emiliani
> 
> -- 
> 
> *Fabio Emiliani*
> 
> */Software Engineer/*
> 
> /Ph. +39 075 8298 530  /
> 
> /fabio.emili...@artgroup-spa.com/ 
> 
> DISCLAIMER
> This email and any attachment may contain confidential information. If
> you are not the intended recipient you are not authorised to copy or
> disclose all or any part of it without the prior written consent of ART SpA.
> 
>  
> 
> /ART SpA – Step Forward With US - //www.artgroup-spa.com/logo_ART_firma-1//
> 
> /Ph. +39 075 8298 501 – Fax +39 075 8298 525 /
> 
> P*Please consider our environment  before printing this e-mail***
> 
>  
> 
> 
> 



signature.asc
Description: OpenPGP digital signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2017-03-14 Thread Fabio Emiliani 

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 the .UTF-8 suffix.


See:

|/usr/share/locale/ drwxr-xr-x 6 root root 416 Nov 17 2016 . drwxr-xr-x 
30 root root 2056 Nov 17 2016 .. drwxr-xr-x 4 root root 296 Nov 17 
2016 de drwxr-xr-x 3 root root 232 Nov 17 2016 en_GB drwxr-xr-x 4 root 
root 296 Nov 17 2016 fr drwxr-xr-x 4 root root 296 Nov 17 2016 zh_CN|

|and|

||

|/usr/lib/locale/ drwxr-xr-x 9 root root 640 Mar 13 2017 . drwxr-xr-x 
32 root root 4 Mar 13 2017 .. drwxr-xr-x 3 root root 1016 Mar 13 
2017 de_DE drwxr-xr-x 3 root root 1016 Mar 13 2017 en_GB drwxr-xr-x 3 
root root 1016 Mar 13 2017 en_GB.ISO-8859-1 drwxr-xr-x 3 root root 
1016 Mar 13 2017 en_US drwxr-xr-x 3 root root 1016 Mar 13 2017 
en_US.ISO-8859-1 drwxr-xr-x 3 root root 1016 Mar 13 2017 fr_FR 
drwxr-xr-x 3 root root 1016 Mar 13 2017 zh_CN|
What is the character encoding of the following locales: de_DE, en_GB, 
en_US, fr_FR, zh_CN?


Thanks in advance for your time

Best regards,

Fabio Emiliani

--

*Fabio Emiliani*

*/Software Engineer/*

/Ph. +39 075 8298 530 /

/fabio.emili...@artgroup-spa.com/ 

DISCLAIMER
This email and any attachment may contain confidential information. If 
you are not the intended recipient you are not authorised to copy or 
disclose all or any part of it without the prior written consent of ART SpA.


/ART SpA – Step Forward With US - //www.artgroup-spa.com/logo_ART_firma-1//

/Ph. +39 075 8298 501 – Fax +39 075 8298 525 /

P*Please consider our environment  before printing this e-mail***

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] suddenly, bunch of circular dependency errors

2017-03-14 Thread Robert P. J. Day 

  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 to see a list of unbuildable tasks.

Identifying dependency loops (this may take a short while)...

ERROR: An uncaught exception occurred in runqueue

  is anyone else seeing this?

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday


-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Confusing message

2017-03-14 Thread Burton, Ross 
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 deployed).  All of the
tasks succeeded (skipping is success).

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2017-03-14 Thread Paul Barker 
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):
  linux-raspberrypi: Fix uImage build on 4.9.y and later
  linux-raspberrypi_4.4: Update to 4.4.50

 ...-Add-rules-for-.dtbo-files-for-dts-overla.patch | 29 --
 recipes-kernel/linux/linux-raspberrypi_4.4.bb  |  5 ++--
 recipes-kernel/linux/linux-raspberrypi_4.9.bb  | 10 +---
 3 files changed, 10 insertions(+), 34 deletions(-)
 delete mode 100644 
recipes-kernel/linux/linux-raspberrypi-4.9/0001-build-arm64-Add-rules-for-.dtbo-files-for-dts-overla.patch

-- 
2.11.0

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2017-03-14 Thread Paul Barker 
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
--- a/recipes-kernel/linux/linux-raspberrypi_4.9.bb
+++ b/recipes-kernel/linux/linux-raspberrypi_4.9.bb
@@ -6,3 +6,8 @@ SRCREV = "28ea32b9afb5d813986c4ab940c26fe298d80ed2"
 SRC_URI = 
"git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.9.y \
 "
 require linux-raspberrypi.inc
+
+# A LOADADDR is needed when building a uImage format kernel. This value is not
+# set by default in rpi-4.8.y and later branches so we need to provide it
+# manually. This value unused if KERNEL_IMAGETYPE is not uImage.
+KERNEL_EXTRA_ARGS += "LOADADDR=0x8000"
-- 
2.11.0

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2017-03-14 Thread Paul Barker 
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 deletions(-)
 delete mode 100644 
recipes-kernel/linux/linux-raspberrypi-4.9/0001-build-arm64-Add-rules-for-.dtbo-files-for-dts-overla.patch

diff --git 
a/recipes-kernel/linux/linux-raspberrypi-4.9/0001-build-arm64-Add-rules-for-.dtbo-files-for-dts-overla.patch
 
b/recipes-kernel/linux/linux-raspberrypi-4.9/0001-build-arm64-Add-rules-for-.dtbo-files-for-dts-overla.patch
deleted file mode 100644
index e8bc52e..000
--- 
a/recipes-kernel/linux/linux-raspberrypi-4.9/0001-build-arm64-Add-rules-for-.dtbo-files-for-dts-overla.patch
+++ /dev/null
@@ -1,29 +0,0 @@
-From 922ce1fd0eb810b713f6ffa9a7ab97c11b6e38cf Mon Sep 17 00:00:00 2001
-From: Khem Raj 
-Date: Fri, 10 Feb 2017 17:57:08 -0800
-Subject: [PATCH] build/arm64: Add rules for .dtbo files for dts overlays
-
-We now create overlays as .dtbo files.
-
-Signed-off-by: Khem Raj 

- arch/arm64/Makefile | 3 +++
- 1 file changed, 3 insertions(+)
-
-diff --git a/arch/arm64/Makefile b/arch/arm64/Makefile
-index 3635b8662724..822fefeb1cd0 100644
 a/arch/arm64/Makefile
-+++ b/arch/arm64/Makefile
-@@ -113,6 +113,9 @@ zinstall install:
- %.dtb: scripts
-   $(Q)$(MAKE) $(build)=$(boot)/dts $(boot)/dts/$@
- 
-+%.dtbo: | scripts
-+  $(Q)$(MAKE) $(build)=$(boot)/dts MACHINE=$(MACHINE) $(boot)/dts/$@
-+
- PHONY += dtbs dtbs_install
- 
- dtbs: prepare scripts
--- 
-2.11.1
-
diff --git a/recipes-kernel/linux/linux-raspberrypi_4.9.bb 
b/recipes-kernel/linux/linux-raspberrypi_4.9.bb
index dcca369..7733bf1 100644
--- a/recipes-kernel/linux/linux-raspberrypi_4.9.bb
+++ b/recipes-kernel/linux/linux-raspberrypi_4.9.bb
@@ -1,9 +1,8 @@
 FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"
 
-LINUX_VERSION ?= "4.9.10"
+LINUX_VERSION ?= "4.9.13"
 
-SRCREV = "095c4480e1f623bdc8a221a171ef13b2223706b1"
+SRCREV = "28ea32b9afb5d813986c4ab940c26fe298d80ed2"
 SRC_URI = 
"git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.9.y \
-   
file://0001-build-arm64-Add-rules-for-.dtbo-files-for-dts-overla.patch \
 "
 require linux-raspberrypi.inc
-- 
2.11.0

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2017-03-14 Thread Paul Barker 
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 100644
--- a/recipes-kernel/linux/linux-raspberrypi_4.4.bb
+++ b/recipes-kernel/linux/linux-raspberrypi_4.4.bb
@@ -1,9 +1,10 @@
 FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"
 
-LINUX_VERSION ?= "4.4.48"
+LINUX_VERSION ?= "4.4.50"
 
-SRCREV = "7ddf96fbb7d637b79b449c7bd1c8d35f00571e4b"
+SRCREV = "04c8e47067d4873c584395e5cb260b4f170a99ea"
 SRC_URI = 
"git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.4.y \
file://0001-fix-dtbo-rules.patch \
 "
+
 require linux-raspberrypi.inc
-- 
2.11.0

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2017-03-14 Thread Burton, Ross 
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 expanding variable
> PACKAGECONFIG, expression was ${@bb.utils.filter('DISTRO_FEATURES',
> 'systemd', d)} which triggered exception AttributeError: 'module' object
> has no attribute 'filter'*


This error message tells me that you're using meta-openembedded master, not
krogoth.  Checkout the correct branch of meta-openembedded.

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2017-03-14 Thread Josef Holzmayr 

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 looking at:
http://git.openembedded.org/meta-openembedded/tree/meta-xfce/recipes-xfce/xfce4-power-manager?h=krogoth



*
Fixing a layer revision means i need to change the file
xfce4-power-manager.1.6.0.bb 
extension from 1.6.0 to 1.4.4 ?
*


No, it means that the checkouts of all layers you use (which obviously 
is at least meta-openembedded) have to match the version of poky that 
you use. Have a look at the branches.


Greetz
--
Josef Holzmayr
Software Developer Embedded Systems

Tel: +49 8444 9204-48
Fax: +49 8444 9204-50

R-S-I Elektrotechnik GmbH & Co. KG
Woelkestrasse 11
D-85301 Schweitenkirchen
www.rsi-elektrotechnik.de
———
Amtsgericht Ingolstadt – GmbH: HRB 191328 – KG: HRA 170393
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
Ust-IdNr: DE 128592548

_
Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
USt-IdNr.: DE 128592548

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2017-03-14 Thread Gary Thomas 

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.


 POKY_BBLAYERS_CONF_VERSION = "2"
  4
  5 BBPATH = "${TOPDIR}"
  6 BBFILES ?= ""
  7
  8 BBLAYERS ?= " \
 *9   /home/mistral/yocto/poky/meta \
 10   /home/mistral/yocto/poky/meta-poky \
 11   /home/mistral/yocto/poky/meta-yocto-bsp \
 12   /home/mistral/yocto/poky/meta-openembedded/meta-oe \
 13   /home/mistral/yocto/poky/meta-openembedded/meta-gnome \
 14   /home/mistral/yocto/poky/meta-openembedded/meta-multimedia \
 15   /home/mistral/yocto/poky/meta-openembedded/meta-python \
 16   /home/mistral/yocto/poky/meta-openembedded/meta-xfce \
 17   "
*

i am getting following error after *bitbake* *core-image-minimal-xfce


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 expanding variable 
PACKAGECONFIG, expression was
${@bb.utils.filter('DISTRO_FEATURES', 'systemd', d)} which triggered exception 
AttributeError: 'module' object has no
attribute 'filter'

*
What is the problem and how to solve this problem  ?


It looks like you have a mixture of branches, probably the latest
master from meta-openembedded and krogoth (v2.1) from Poky/Yocto
These need to be in sync or you'll run into problems like this.

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2017-03-14 Thread Josef Holzmayr 

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
: Failure expanding variable
PACKAGECONFIG, expression was ${@bb.utils.filter('DISTRO_FEATURES',
'systemd', d)} which triggered exception AttributeError: 'module' object
has no attribute 'filter'


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.



What is the problem and how to solve this problem  ?


Version mismatch, fix your layer revisions.

Greetz
--
Josef Holzmayr
Software Developer Embedded Systems

Tel: +49 8444 9204-48
Fax: +49 8444 9204-50

R-S-I Elektrotechnik GmbH & Co. KG
Woelkestrasse 11
D-85301 Schweitenkirchen
www.rsi-elektrotechnik.de
———
Amtsgericht Ingolstadt – GmbH: HRB 191328 – KG: HRA 170393
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
Ust-IdNr: DE 128592548

_
Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
USt-IdNr.: DE 128592548

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] core-image-minimal-xfce error

2017-03-14 Thread ravikiran j 
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 = "${TOPDIR}"
  6 BBFILES ?= ""
  7
  8 BBLAYERS ?= " \









* 9   /home/mistral/yocto/poky/meta \ 10
/home/mistral/yocto/poky/meta-poky \ 11
/home/mistral/yocto/poky/meta-yocto-bsp \ 12
/home/mistral/yocto/poky/meta-openembedded/meta-oe \ 13
/home/mistral/yocto/poky/meta-openembedded/meta-gnome \ 14
/home/mistral/yocto/poky/meta-openembedded/meta-multimedia \ 15
/home/mistral/yocto/poky/meta-openembedded/meta-python \ 16
/home/mistral/yocto/poky/meta-openembedded/meta-xfce \ 17   "*

i am getting following error after *bitbake*




*core-image-minimal-xfceERROR: ExpansionError during parsing
/home/mistral/yocto/poky/meta-openembedded/meta-xfce/recipes-xfce/xfce4-power-manager/xfce4-power-manager_1.6.0.bb
: Failure expanding variable
PACKAGECONFIG, expression was ${@bb.utils.filter('DISTRO_FEATURES',
'systemd', d)} which triggered exception AttributeError: 'module' object
has no attribute 'filter'*
What is the problem and how to solve this problem  ?
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] R: Autoload kernel module works only once

2017-03-14 Thread Andrea Laini 
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.

What I've also seen is that very first time the system started, the device 
number of my module in /dev/mydevice and /sys/class/myclass/mydevice/dev are 
exactly the same 

/dev/mydevice   Major = 247, Minor = 0
/sys/class/myclass/mydevice/dev Major = 247, Minor = 0

while from the time I reboot the system the one in 
/sys/class/myclass/mydevice/dev is increment by 1 respect to the other 

/dev/mydevice   Major = 247, Minor = 0
/sys/class/myclass/mydevice/dev Major = 248, Minor = 0


Andrea Laini


-Messaggio originale-
Da: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] Per 
conto di Khem Raj
Inviato: lunedì 13 marzo 2017 21:29
A: yocto@yoctoproject.org
Oggetto: Re: [yocto] Autoload kernel module works only once



On 3/13/17 7:36 AM, Andrea Laini wrote:
> Hi everybody,
> 
>  
> 
> I'm getting some errors after building my Linux distro with the use of 
> KERNEL_MODULE_AUTOLOAD to allow autoloading 2 of my custom out-of-tree 
> device at boot time. We've a Poky 1.7 version.
> 
>  
> 
> So, before building the new image with the Yocto keyword 
> KERNEL_MODULE_AUTOLOAD, I was able to load and open (and, obviously,
> use) my devices simply by calling 'modprobe mydevice' after logging in.
> Restarting the board, everything was still working well.
> 
> Since I've rebuild a new image enabling module autoload at boot time, 
> modules are always loaded, but I'm able to open (and use) them only 
> really first time I switched on the board after downloading new image.
> After the first reboot, LKMs are still loaded (calling 'lsmod' show
> them) but I can't open them, neither from my C program nor 
> reading/writing them from '/dev/mydevice'.

look out for any race conditions for dependencies. Since it will now autoload 
the modules and its possible that you were depending on some system behavior 
that was enabled late in boot process, but it worked since you did it after 
logging in and manually doing modprobe.

> 
>  
> 
> To me it sound a very strange behavior.
> 
>  
> 
> Hope anyone can help,
> 
> Many thanks
> 
>  
> 
> Andrea
> 
>  
> 
> 
>  
> 
> 
> 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Confusing message

2017-03-14 Thread Gary Thomas 

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 out what that did...

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto