Re: [yocto] Honister broken WiFi communication

[tomzy]

Hi JH,

Are you using custom Linux kernel / custom device tree? Maybe there is
some issue there?

Kind regards,
Tomasz Żyjewski
Embedded Systems Engineer
GPG: 5C495EA3EBEECA59
https://3mdeb.com | @3mdeb_com

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55907): https://lists.yoctoproject.org/g/yocto/message/55907
Mute This Topic: https://lists.yoctoproject.org/mt/88505893/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto][linux-yocto v5.10/standard/nxp-sdk-5.10/nxp-soc & v5.10/standard/preempt-rt/nxp-sdk-5.10/nxp-soc][PATCH 1/1] dmaengine: imx-sdma: Fix a build warning in sdma_runtime_resume function

[Xiaolei Wang]

Delete redundant variables 'i' and change disable_clk_ahb to
disable_clk_ipg to void following warning:
warning: unused variable 'i' [-Wunused-variable]
warning: label 'disable_clk_ipg' defined but not used

Fix commit 2da31cfd59da("dmaengine: imx-sdma: Fix a hang when run dma test in 
imx8mq board")
Signed-off-by: Xiaolei Wang 
---
 drivers/dma/imx-sdma.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/dma/imx-sdma.c b/drivers/dma/imx-sdma.c
index e61dd499c3dc..c754f2ba3d90 100644
--- a/drivers/dma/imx-sdma.c
+++ b/drivers/dma/imx-sdma.c
@@ -1639,7 +1639,7 @@ static int sdma_runtime_resume(struct device *dev)
 {
struct platform_device *pdev = to_platform_device(dev);
struct sdma_engine *sdma = platform_get_drvdata(pdev);
-   int i, ret = 0;
+   int ret = 0;
 
/* Do nothing at HW level if audiomix which shared with audio driver
 * not off indeed.
@@ -1723,7 +1723,7 @@ static int sdma_alloc_chan_resources(struct dma_chan 
*chan)
return ret;
ret = clk_enable(sdmac->sdma->clk_ahb);
if (ret)
-   goto disable_clk_ahb;
+   goto disable_clk_ipg;
}
 
ret = sdma_set_channel_priority(sdmac, prio);
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#10845): 
https://lists.yoctoproject.org/g/linux-yocto/message/10845
Mute This Topic: https://lists.yoctoproject.org/mt/88529094/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto] [PATCH] octeontx2: nic: Replace get_cpu()/put_cpu() with get_cpu_ptr()/put_cpu_ptr()

[Ruiqiang Hao]

From: Ruiqiang Hao 

After commit 2baa2d5b94e5(octeontx2-pf: disable preemption while using
per_cpu pointer) applied, the kmalloc function is called in the atomic
context, which leads to the following call trace. It can be solved by
using get_cpu_ptr()/put_cpu_ptr() in function __cn10k_aura_freeptr().

BUG: sleeping function called from invalid context at mm/slab.h:513
in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 1, name: swapper/0
2 locks held by swapper/0/1:
 #0: 800012629730 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock+0x28/0x34
 #1: 000110d956c8 (>lock){+.+.}-{3:3}, at: 
otx2_init_hw_resources+0xa0/0x350
device: '179:24': device_add
Preemption disabled at:
[] otx2_sq_aura_pool_init+0x14c/0x310
CPU: 13 PID: 1 Comm: swapper/0 Not tainted 5.10.89-yocto-standard #1
device: 'mmcblk2boot1': device_add
Hardware name: Marvell OcteonTX CN96XX board (DT)
Call trace:
 dump_backtrace+0x0/0x1e0
 show_stack+0x24/0x30
 dump_stack+0xec/0x154
 ___might_sleep+0x1a0/0x250
 __might_sleep+0x5c/0x94
 __kmalloc+0x2f4/0x450
 otx2_sq_aura_pool_init+0x1ac/0x310
 otx2_init_hw_resources+0x108/0x350
 otx2_open+0xf0/0x5f0
 __dev_open+0x134/0x200
 __dev_change_flags+0x1d8/0x260
 dev_change_flags+0x30/0x70
 ic_open_devs+0x128/0x320
 ip_auto_config+0x184/0x430
 do_one_initcall+0x54/0x190
 kernel_init_freeable+0x1f0/0x26c
 kernel_init+0x20/0x12c
 ret_from_fork+0x10/0x18

Signed-off-by: Ruiqiang Hao 
---
 drivers/net/ethernet/marvell/octeontx2/nic/otx2_common.c | 6 --
 drivers/net/ethernet/marvell/octeontx2/nic/otx2_common.h | 3 ++-
 2 files changed, 2 insertions(+), 7 deletions(-)

diff --git a/drivers/net/ethernet/marvell/octeontx2/nic/otx2_common.c 
b/drivers/net/ethernet/marvell/octeontx2/nic/otx2_common.c
index 669516739481..58ddd0c54a79 100644
--- a/drivers/net/ethernet/marvell/octeontx2/nic/otx2_common.c
+++ b/drivers/net/ethernet/marvell/octeontx2/nic/otx2_common.c
@@ -1006,7 +1006,6 @@ static void otx2_pool_refill_task(struct work_struct 
*work)
rbpool = cq->rbpool;
free_ptrs = cq->pool_ptrs;
 
-   get_cpu();
while (cq->pool_ptrs) {
if (otx2_alloc_rbuf(pfvf, rbpool, )) {
/* Schedule a WQ if we fails to free atleast half of the
@@ -1026,7 +1025,6 @@ static void otx2_pool_refill_task(struct work_struct 
*work)
pfvf->hw_ops->aura_freeptr(pfvf, qidx, bufptr + OTX2_HEAD_ROOM);
cq->pool_ptrs--;
}
-   put_cpu();
cq->refill_task_sched = false;
 }
 
@@ -1365,7 +1363,6 @@ int otx2_sq_aura_pool_init(struct otx2_nic *pfvf)
if (err)
goto fail;
 
-   get_cpu();
/* Allocate pointers and free them to aura/pool */
for (qidx = 0; qidx < hw->tot_tx_queues; qidx++) {
pool_id = otx2_get_pool_idx(pfvf, AURA_NIX_SQ, qidx);
@@ -1389,7 +1386,6 @@ int otx2_sq_aura_pool_init(struct otx2_nic *pfvf)
}
 
 err_mem:
-   put_cpu();
return err ? -ENOMEM : 0;
 
 fail:
@@ -1430,7 +1426,6 @@ int otx2_rq_aura_pool_init(struct otx2_nic *pfvf)
if (err)
goto fail;
 
-   get_cpu();
/* Allocate pointers and free them to aura/pool */
for (pool_id = 0; pool_id < hw->rqpool_cnt; pool_id++) {
pool = >qset.pool[pool_id];
@@ -1443,7 +1438,6 @@ int otx2_rq_aura_pool_init(struct otx2_nic *pfvf)
}
}
 err_mem:
-   put_cpu();
return err ? -ENOMEM : 0;
 fail:
otx2_mbox_reset(>mbox.mbox, 0);
diff --git a/drivers/net/ethernet/marvell/octeontx2/nic/otx2_common.h 
b/drivers/net/ethernet/marvell/octeontx2/nic/otx2_common.h
index 897968477d35..51522518c46a 100644
--- a/drivers/net/ethernet/marvell/octeontx2/nic/otx2_common.h
+++ b/drivers/net/ethernet/marvell/octeontx2/nic/otx2_common.h
@@ -650,7 +650,7 @@ static inline void __cn10k_aura_freeptr(struct otx2_nic 
*pfvf, u64 aura,
u64 size = 0, count_eot = 0;
u64 tar_addr, val = 0;
 
-   lmt_info = per_cpu_ptr(pfvf->hw.lmt_info, smp_processor_id());
+   lmt_info = get_cpu_ptr(pfvf->hw.lmt_info);
tar_addr = (__force u64)otx2_get_regaddr(pfvf, NPA_LF_AURA_BATCH_FREE0);
/* LMTID is same as AURA Id */
val = (lmt_info->lmt_id & 0x7FF) | BIT_ULL(63);
@@ -671,6 +671,7 @@ static inline void __cn10k_aura_freeptr(struct otx2_nic 
*pfvf, u64 aura,
}
dma_wmb();
memcpy((u64 *)lmt_info->lmt_addr, ptrs, sizeof(u64) * num_ptrs);
+   put_cpu_ptr(pfvf->hw.lmt_info);
/* Perform LMTST flush */
cn10k_lmt_flush(val, tar_addr);
 }
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#10844): 
https://lists.yoctoproject.org/g/linux-yocto/message/10844
Mute This Topic: https://lists.yoctoproject.org/mt/88528358/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto][linux-yocto v5.10] kernel code for marvell octeon

[Ruiqiang Hao]

Hi Bruce,

Please help to merge this patch into our linux-yocto repo.

repo:
linux-yocto
branch:
v5.10/standard/cn-sdkv5.4/octeon
v5.10/standard/preempt-rt/cn-sdkv5.4/octeon

Thanks,
Ruiqiang

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#10843): 
https://lists.yoctoproject.org/g/linux-yocto/message/10843
Mute This Topic: https://lists.yoctoproject.org/mt/88528357/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [linux-yocto][yocto-kernel-cache yocto-5.10][PATCH 1/2] Fix a build error undefined reference to `mbox_send_message'

[Bruce Ashfield]

merged.

Bruce

In message: [linux-yocto][yocto-kernel-cache yocto-5.10][PATCH 1/2] Fix a build 
error undefined reference to `mbox_send_message'
on 19/01/2022 Xiaolei Wang wrote:

> refer to commit a86473962139a("arm: arch: enable rpmsg for imx amp soc")
> imx6sx soc has seleted HAVE_IMX_RPMSG, so enable MAILBOX config
> 
> Signed-off-by: Xiaolei Wang 
> ---
>  bsp/nxp-imx6/nxp-imx6.cfg | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/bsp/nxp-imx6/nxp-imx6.cfg b/bsp/nxp-imx6/nxp-imx6.cfg
> index 3b7ae059..dd92c39a 100644
> --- a/bsp/nxp-imx6/nxp-imx6.cfg
> +++ b/bsp/nxp-imx6/nxp-imx6.cfg
> @@ -207,3 +207,5 @@ CONFIG_CMA_AREAS=7
>  CONFIG_GPIO_74X164=y
>  CONFIG_GPIO_MXC=y
>  CONFIG_GPIO_PCA953X=y
> +
> +CONFIG_MAILBOX=y
> -- 
> 2.25.1
> 

In message: [linux-yocto][yocto-kernel-cache yocto-5.10][PATCH 2/2] nxp-imx6: 
Fix a build error undefined reference to `dw_pcie_read_dbi'
on 19/01/2022 Xiaolei Wang wrote:

> refer to commit 4e9a723c0902("pci: imx: add the imx8qxp ep support")
> modify PCI_IMX6 to PCI_IMX6_HOST
> 
> Signed-off-by: Xiaolei Wang 
> ---
>  bsp/nxp-imx6/nxp-imx6.cfg | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/bsp/nxp-imx6/nxp-imx6.cfg b/bsp/nxp-imx6/nxp-imx6.cfg
> index dd92c39a..e19395ff 100644
> --- a/bsp/nxp-imx6/nxp-imx6.cfg
> +++ b/bsp/nxp-imx6/nxp-imx6.cfg
> @@ -150,7 +150,7 @@ CONFIG_NEW_LEDS=y
>  CONFIG_LEDS_CLASS=y
>  
>  CONFIG_PCI=y
> -CONFIG_PCI_IMX6=y
> +CONFIG_PCI_IMX6_HOST=y
>  CONFIG_PCI_MSI=y
>  CONFIG_PCIEPORTBUS=y
>  
> -- 
> 2.25.1
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#10842): 
https://lists.yoctoproject.org/g/linux-yocto/message/10842
Mute This Topic: https://lists.yoctoproject.org/mt/88524735/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [linux-yocto][linux-yocto v5.10/standard/nxp-sdk-5.10/nxp-soc & v5.10/standard/preempt-rt/nxp-sdk-5.10/nxp-soc][PATCH 2/2] drm/imx: Fix a build error No rule to make target 'ipuv3-crtc.o'

[Bruce Ashfield]

merged.

Bruce

In message: [linux-yocto][linux-yocto v5.10/standard/nxp-sdk-5.10/nxp-soc & 
v5.10/standard/preempt-rt/nxp-sdk-5.10/nxp-soc][PATCH 2/2] drm/imx: Fix a build 
error No rule to make target 'ipuv3-crtc.o'
on 18/01/2022 Xiaolei Wang wrote:

> ipuv3 has been moved to a new directory, so delete it from Makefile
> 
> Fixes: 927cbb68a3ab2 ("drm/imx: ipuv3-kms: Move to a new ipuv3 folder")
> Signed-off-by: Xiaolei Wang 
> ---
>  drivers/gpu/drm/imx/Makefile | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/imx/Makefile b/drivers/gpu/drm/imx/Makefile
> index 28f9fe6697a7..4764058d9adf 100644
> --- a/drivers/gpu/drm/imx/Makefile
> +++ b/drivers/gpu/drm/imx/Makefile
> @@ -13,7 +13,6 @@ obj-$(CONFIG_DRM_IMX8QXP_LDB) += imx8qxp-ldb.o
>  obj-$(CONFIG_DRM_IMX8MP_LDB) += imx8mp-ldb.o
>  
>  imx-ipuv3-crtc-objs  := ipuv3-crtc.o ipuv3-plane.o ipuv3-kms.o
> -obj-$(CONFIG_DRM_IMX_IPUV3)  += imx-ipuv3-crtc.o
>  obj-$(CONFIG_DRM_IMX_DPU) += dpu/
>  obj-$(CONFIG_DRM_IMX_IPUV3) += ipuv3/
>  obj-$(CONFIG_DRM_IMX_HDMI) += dw_hdmi-imx.o
> -- 
> 2.25.1
> 

In message: [linux-yocto][linux-yocto v5.10/standard/nxp-sdk-5.10/nxp-soc & 
v5.10/standard/preempt-rt/nxp-sdk-5.10/nxp-soc][PATCH 1/2] clk: imx: Fix a 
build error too many arguments 'imx_register_uart_clocks' in imx6q_clocks_init()
on 18/01/2022 Xiaolei Wang wrote:

> Since commit 247a98a4a2dcb("clk: imx: enable the earlycon
> uart clocks by parsing from dt") imx_register_uart_clocks
> no longer requires parameters, so delete the incoming parameters
> 
> Signed-off-by: Xiaolei Wang 
> ---
>  drivers/clk/imx/clk-imx6q.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/clk/imx/clk-imx6q.c b/drivers/clk/imx/clk-imx6q.c
> index 34c2efc69073..f906b46338f3 100644
> --- a/drivers/clk/imx/clk-imx6q.c
> +++ b/drivers/clk/imx/clk-imx6q.c
> @@ -1058,6 +1058,6 @@ static void __init imx6q_clocks_init(struct device_node 
> *ccm_node)
>  hws[IMX6QDL_CLK_PLL3_USB_OTG]->clk);
>   }
>  
> - imx_register_uart_clocks(2);
> + imx_register_uart_clocks();
>  }
>  CLK_OF_DECLARE(imx6q, "fsl,imx6q-ccm", imx6q_clocks_init);
> -- 
> 2.25.1
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#10841): 
https://lists.yoctoproject.org/g/linux-yocto/message/10841
Mute This Topic: https://lists.yoctoproject.org/mt/88527910/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [linux-yocto]: [kernel for intel-socfpga]: intel-socfpga: improve dts files for FPGA design

[Bruce Ashfield]

In message: [linux-yocto]: [kernel for intel-socfpga]: intel-socfpga: improve 
dts files for FPGA design
on 18/01/2022 Meng Li wrote:

> From: Limeng 
> 
> Hi Bruce,
> 
> There are below 2 pathces to improve dts files for FPGA design
> 
> Could you please help to merge them into linux-ycoto kernel repo, both 
> standard and rt branches
> v5.10/standard/intel-sdk-5.10/intel-socfpga
> v5.10/standard/preempt-rt/intel-sdk-5.10/intel-socfpga

merged.

Bruce

> 
> diffstat info as below:
> 
>  socfpga_stratix10_socdk.dts   |2 ++
>  socfpga_stratix10_socdk_ghrd.dts  |1 +
>  socfpga_stratix10_socdk_pcie.dts  |1 +
>  socfpga_stratix10_socdk_sgmii.dts |3 +++
>  4 files changed, 7 insertions(+)
> 
> 
> thanks,
> Limeng

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#10840): 
https://lists.yoctoproject.org/g/linux-yocto/message/10840
Mute This Topic: https://lists.yoctoproject.org/mt/88505013/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [linux-yocto] [linux-yocto preempt-rt kernel]: nxp-s32g2xx: update linux-yocto to NXP bsp32 rc1

[Bruce Ashfield]

In message: [linux-yocto] [linux-yocto preempt-rt kernel]: nxp-s32g2xx: update 
linux-yocto to NXP bsp32 rc1
on 17/01/2022 Zhantao Tang wrote:

> Hi Bruce,
> 
> There are 17 patches from bsp32 rc2 for updating the following branch
> 
> v5.10/standard/preempt-rt/nxp-sdk-5.10/nxp-s32g2xx
> 
> ould you please help to merge these patches?

thanks for the fixup!

This is now merged.

Bruce

> 
> 
> The patch infos as following:
> 
> The following changes since commit a43e21eb1feeeaae22d8ad048fae9957cb94a2b2:
> 
>   Merge branch 'v5.10/standard/preempt-rt/base' into 
> v5.10/standard/preempt-rt/nxp-sdk-5.10/nxp-s32g2xx (2022-01-16 22:53:43 -0500)
> 
> are available in the Git repository at:
> 
>   https://github.com/zhantaotang/linux-yocto-std 
> v5.10/standard/preempt-rt/nxp-sdk-5.10/nxp-s32g2xx
> 
> for you to fetch changes up to 9a5f71ca20d408aac00daecde6ed17c99fb2997f:
> 
>   devicetree: bindings: Add mc_me and mc_rgm syscons (2022-01-17 12:55:26 
> +0800)
> 
> 
> Thanks,
> Zhantao

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#10839): 
https://lists.yoctoproject.org/g/linux-yocto/message/10839
Mute This Topic: https://lists.yoctoproject.org/mt/88478979/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] [yocto-autobuilder2][PATCH] config.py: enable debian11 for hardknott

[Anuj Mittal]

Signed-off-by: Anuj Mittal 
---
 config.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/config.py b/config.py
index 4c0b83b..0f99557 100644
--- a/config.py
+++ b/config.py
@@ -149,7 +149,7 @@ all_workers = workers + workers_bringup + workers_buildperf 
+ workers_arm
 
 # Worker filtering for older releases
 workers_prev_releases = {
-"hardknott" : ("centos7", "centos8", "debian8", "debian9", "debian10", 
"fedora31", "fedora32", "fedora33", "fedora34", "opensuse152", "ubuntu1604", 
"ubuntu1804", "ubuntu2004", "perf-"),
+"hardknott" : ("centos7", "centos8", "debian8", "debian9", "debian10", 
"debian11", "fedora31", "fedora32", "fedora33", "fedora34", "opensuse152", 
"ubuntu1604", "ubuntu1804", "ubuntu2004", "perf-"),
 "gatesgarth" : ("centos7", "centos8", "debian8", "debian9", "debian10", 
"fedora30", "fedora31", "fedora32", "opensuse150", "opensuse151", 
"opensuse152", "ubuntu1604", "ubuntu1804", "ubuntu1904", "ubuntu2004", "perf-"),
 "dunfell" : ("centos7", "centos8", "debian8", "debian9", "debian10", 
"debian11", "fedora29", "fedora30", "fedora31", "fedora32", "fedora33", 
"fedora34", "opensuse150", "opensuse151", "opensuse152", "ubuntu1604", 
"ubuntu1804", "ubuntu1904", "ubuntu2004", "perf-"),
 "zeus" : ("centos7", "debian8", "debian9", "debian10", "fedora28", 
"fedora29", "fedora30", "opensuse150", "opensuse151", "ubuntu1604", 
"ubuntu1804", "ubuntu1904", "perf-"),
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55906): https://lists.yoctoproject.org/g/yocto/message/55906
Mute This Topic: https://lists.yoctoproject.org/mt/88527653/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Honister broken WiFi communication

[JH]

Hi Rudolf,

Thanks for your response and comments.

> If you run ifconfig -a does your WiFi interface show up? If not there is an
> issue with the driver. Use dmesg and filter for the driver. Often a driver
> cannot load the firmware. What is your WiFi hardware?

Not that bad, the WiFi interfaces was fine, but it could not get dhcp
response and IP address so an automatic private IP address 169.254 was
assigned

mlan0 Link encap:Ethernet  HWaddr D4:CA:6E:A4:E8:B4
  inet addr:169.254.193.101  Bcast:169.254.255.255  Mask:255.255.0.0
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:2 errors:0 dropped:0 overruns:0 frame:0
  TX packets:56 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:330 (330.0 B)  TX bytes:16392 (16.0 KiB)

I could see WiFi information well, it is not a major problem, but the
subtle issues are connman and wpa_supplicant did not set up the WiFi
driver correctly.

Connected to 34:08:04:12:b1:a2 (on mlan0)
SSID: JupiterIoT
freq: 2437
RX: 660 bytes (4 packets)
TX: 46622 bytes (129 packets)
signal: -57 dBm
rx bitrate: 1.0 MBit/s
tx bitrate: 72.2 MBit/s MCS 7 short GI

bss flags:  short-slot-time
dtim period:1
beacon int: 100

> Did you install the regulatory database?

Did you mean to enable CONFIG_CFG80211_INTERNAL_REGDB? No, I did not
install it in the Zeus version either so I don't see that could be an
issue.

> What error messages are you seeing when attempting to connect to a WiFi
> network? Did you look at the connman logs?

No error in connman, I don't think it is connman or wpa_supplicant
issue, my suspicion is something missing in Honister built image to
prevent connman and wpa_supplicant to set up the WiFi driver
correctly.

It is not the first time I have the WiFi setup trouble to get WiFi
169.254 address, when I upgraded from Thud to Zeus, I got the exactly
the same problem that WiFi was assigned by a 169.254 address, no dhcp
response, at time, I was totally convinced it was connman issue, I
spend several months to debug connman and wpa_supplicant without any
results, then after waiting several months to pull updated Zeus again,
that problem was disappeared miraculous, that is why I suspect the
same problem in oe-core and bitbake in Honister as well.

Are there anyone in oe-core and bitbake tested connman, wpa_supplicant
for the current Honister branch? I can help to test and to debug it if
more advanced people in oe-core, bitbake, kernel, WiFi driver mwifiex
can provide me more information.

Thank you.

Kind regards,

- jupiter

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55905): https://lists.yoctoproject.org/g/yocto/message/55905
Mute This Topic: https://lists.yoctoproject.org/mt/88505893/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto][yocto-kernel-cache yocto-5.10][PATCH 2/2] nxp-imx6: Fix a build error undefined reference to `dw_pcie_read_dbi'

[Xiaolei Wang]

refer to commit 4e9a723c0902("pci: imx: add the imx8qxp ep support")
modify PCI_IMX6 to PCI_IMX6_HOST

Signed-off-by: Xiaolei Wang 
---
 bsp/nxp-imx6/nxp-imx6.cfg | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/bsp/nxp-imx6/nxp-imx6.cfg b/bsp/nxp-imx6/nxp-imx6.cfg
index dd92c39a..e19395ff 100644
--- a/bsp/nxp-imx6/nxp-imx6.cfg
+++ b/bsp/nxp-imx6/nxp-imx6.cfg
@@ -150,7 +150,7 @@ CONFIG_NEW_LEDS=y
 CONFIG_LEDS_CLASS=y
 
 CONFIG_PCI=y
-CONFIG_PCI_IMX6=y
+CONFIG_PCI_IMX6_HOST=y
 CONFIG_PCI_MSI=y
 CONFIG_PCIEPORTBUS=y
 
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#10838): 
https://lists.yoctoproject.org/g/linux-yocto/message/10838
Mute This Topic: https://lists.yoctoproject.org/mt/88524819/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto][yocto-kernel-cache yocto-5.10][PATCH 1/2] Fix a build error undefined reference to `mbox_send_message'

[Xiaolei Wang]

refer to commit a86473962139a("arm: arch: enable rpmsg for imx amp soc")
imx6sx soc has seleted HAVE_IMX_RPMSG, so enable MAILBOX config

Signed-off-by: Xiaolei Wang 
---
 bsp/nxp-imx6/nxp-imx6.cfg | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/bsp/nxp-imx6/nxp-imx6.cfg b/bsp/nxp-imx6/nxp-imx6.cfg
index 3b7ae059..dd92c39a 100644
--- a/bsp/nxp-imx6/nxp-imx6.cfg
+++ b/bsp/nxp-imx6/nxp-imx6.cfg
@@ -207,3 +207,5 @@ CONFIG_CMA_AREAS=7
 CONFIG_GPIO_74X164=y
 CONFIG_GPIO_MXC=y
 CONFIG_GPIO_PCA953X=y
+
+CONFIG_MAILBOX=y
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#10837): 
https://lists.yoctoproject.org/g/linux-yocto/message/10837
Mute This Topic: https://lists.yoctoproject.org/mt/88524735/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] gdb with a broken sdk

[Khem Raj]

On 1/16/22 3:26 PM, dacav wrote:

On Wed, Jan 12, 2022 at 02:15:38AM +, dacav wrote:

How can I include aarch64-foobar-gdb in the devshell's PATH?


Follow up on this thread: I've been kindly helped by kroon on #yocto.
The trick consists in adding a build-time dependency to gdb-cross-aarch64
in my recipe:

DEPEND = "gdb-cross-aarch64"


perhaps gdb-cross-${TARGET_ARCH} would be more generic.



At this point I can just use `bitbake -c devshell $myrecipe` and the
debugger is available.

Bonus: the devshell turns out to be very useful as a replacement
for the SDK: the environment allows me to do the cross-compilation
with just a `make`, while earlier I needed to run `bitbake $myrecipe`
and wait several seconds.


- dacav






-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55904): https://lists.yoctoproject.org/g/yocto/message/55904
Mute This Topic: https://lists.yoctoproject.org/mt/88397912/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [linux-yocto] Install apt-get in yocto hardknott 25.0.4

[Alexander Kanavin]

You need to put package_deb first, as the otherwise rpm is used to make an
image and put a package database in it.

Alex

On Tue, 18 Jan 2022 at 17:43,  wrote:

> Iam trying to install apt-get in yocto.
> 1)In the local.conf I added: PACKAGE_CLASSES ?= "package_rpm package_deb"
> EXTRA_IMAGE_FEATURES ?= " package-management " PACKAGE_FEED_URIS = "
> http://local IP:" IMAGE_INSTALL_append +=" apt"enter code here
>
>1.
>
>Then I generate the image with : bitbake core-image-minimal
>2.
>
>Then I execute the image with qemu and I obtained this message:
>
>Reading package lists... Error! E: flAbsPath on /var/lib/dpkg/status
>failed - realpath (2: No such file or dire) E: Could not open file - open
>(2: No such file or directory) E: Problem opening E: The package lists or
>status file could not be parsed or opened.
>
> How can I fix this problem?
> Thanks!
>
> 
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#10836): 
https://lists.yoctoproject.org/g/linux-yocto/message/10836
Mute This Topic: https://lists.yoctoproject.org/mt/88513197/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Advertise lore.kernel.org archives on website?

[Michael Opdenacker]

On 1/18/22 12:04 PM, Richard Purdie wrote:
> On Tue, 2022-01-18 at 10:44 +0100, Michael Opdenacker wrote:
>> Greetings,
>>
>> I see more and more people using links to the lore.kernel.org archives,
>> for example the ones for this list: https://lore.kernel.org/yocto/
>>
>> These look more convenient to use than the ones on
>> https://lists.yoctoproject.org/.
>>
>> So what about advertising such archives on
>> https://www.yoctoproject.org/community/mailing-lists/, at least for the
>> ones which have archives on lore.kernel.org? I was thinking about just
>> adding an "(archives)" or "(archives / public mailbox) link at the end
>> of the description for each list.
>>
>> What do you think?
> Sounds fine to me.


Thanks for the feedback.
Done on https://www.yoctoproject.org/community/mailing-lists/

I added lore.kernel.org links when applicable, and also added the
openembedded-devel mailing list which was missing.
I could shorten "Archives / Public Inbox" by just "Public Inbox" if you
think it makes more sense.

Cheers
Michael.

-- 
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55903): https://lists.yoctoproject.org/g/yocto/message/55903
Mute This Topic: https://lists.yoctoproject.org/mt/88505838/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Building uImage with appended DTB

[Nicolas Jeker]

> On 17 Jan 2022, at 06:41, rgovos...@gmail.com wrote:
> 
> I'm a complete newcomer to Yocto, trying to translate a manual process of 
> building software for an embedded device based on the PHYTEC phyCORE-LPC3250 
> SOM. I did not find an existing BSP layer for this board so I am trying to 
> create my own.

Just a short hint if you didn’t discover it yourself, there is a (very) old BSP 
available from PHYTEC [1]. The downloads don’t seem to work, but they’re 
available on a probably forgotten FTP server [2].

[1]: 
https://web.archive.org/web/20120501212117/http://www.phytec.com/products/linux/bsp-LPC3180.html
[2]: ftp://ftp.phytec.com/temp/PCM-031_phyCORE-LPC3180

> 
> When I build a kernel for this device manually, I use the 
> CONFIG_APPENDED_DTB=y option, which instructs the kernel to find the device 
> tree right after the kernel image itself. I build the zImage, then append my 
> DTB and finally create the uImage file:
> 
> cat arch/arm/boot/zImage ./arch/arm/boot/dts/lpc3250-phy3250.dtb > 
> arch/arm/boot/zImage-dtb
> mkimage -A arm -O linux -C none -T kernel -a 0x80008000 -e 0x80008000 -n 
> Linux -d arch/arm/boot/zImage-dtb arch/arm/boot/uImage-dtb
> 
> I'm trying to figure out how to properly replicate this process in Yocto.
> 
> I see that Poky's meta/classes/kernel-devicetree.bbclass uses the 
> KERNEL_DEVICETREE_BUNDLE variable to do something similar. If I have 
> KERNEL_IMAGETYPE set to "zImage", then it will create a zImage+DTB file.
> 
> However, it expects the zImage file to be called "zImage", and the one that 
> gets built is called "zImage-5.14.6-yocto-standard". Since it cannot find 
> "zImage", the build fails.
> 
> cat: 
> .../tmp/work/lpc3250-poky-linux-gnueabi/linux-yocto/5.14.6+gitAUTOINC+4f4ad2c808_7ae156be3b-r0/image/boot/zImage:
>  No such file or directory
> 
> 
> I also see that meta-ti has a bundle-devicetree.inc file that has a similar 
> aim, but it deals with uImages instead.
> 
> https://git.yoctoproject.org/meta-ti/tree/recipes-kernel/linux/bundle-devicetree.inc
> 
> My concern with using this is that it appends the DTB directly to the uImage. 
> However the uImage header structure includes a field for data size and 
> another one for checksum. These fields are only computed correctly if the DTB 
> is already appended before the uImage file is built.
> 
> 
> I think if I can figure out how to make KERNEL_DEVICETREE_BUNDLE create the 
> zImage+DTB file, then I can write a do_deploy:append() function that invokes 
> mkimage to produce the uImage. But I'm not sure how to diagnose the problem.
> 
> Thanks,
> Ryan
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55902): https://lists.yoctoproject.org/g/yocto/message/55902
Mute This Topic: https://lists.yoctoproject.org/mt/88479144/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto] Install apt-get in yocto hardknott 25.0.4

[nidhameddine . belhadj]

Iam trying to install apt-get in yocto.
1)In the local.conf I added: PACKAGE_CLASSES ?= "package_rpm package_deb" 
EXTRA_IMAGE_FEATURES ?= " package-management " PACKAGE_FEED_URIS = 
"http://local IP:" IMAGE_INSTALL_append +=" apt"enter code here

* 

Then I generate the image with : bitbake core-image-minimal

* 

Then I execute the image with qemu and I obtained this message:

Reading package lists... Error! E: flAbsPath on /var/lib/dpkg/status failed - 
realpath (2: No such file or dire) E: Could not open file - open (2: No such 
file or directory) E: Problem opening E: The package lists or status file could 
not be parsed or opened.

How can I fix this problem?
Thanks!

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#10835): 
https://lists.yoctoproject.org/g/linux-yocto/message/10835
Mute This Topic: https://lists.yoctoproject.org/mt/88513197/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Yocto Project Status WW03`22

[Stephen Jolley]

Current Dev Position: YP 3.5 M2

Next Deadline: 17th Jan. 2022 YP 3.5 M2 build

 

Next Team Meetings:

*   Bug Triage meeting Thursday Jan. 20th 7:30 am PDT (

https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*   Monthly Project Meeting Tuesday Feb. 1st at 8 am PDT (

https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09
 )
*   Weekly Engineering Sync Tuesday Jan. 18th at 8 am PDT (

https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09
 )
*   Twitch -  See https://www.twitch.tv/theyoctojester

 

Key Status/Updates:

*   YP 3.5 M2 is due to build this week
*   Work has progressed on inclusive language and an email should be out
this week about the proposals for that after discussions amongst the
volunteers who stepped up to work on it. Some obsolete variables/code have
already been removed as a prelude to this.
*   Patches to switch to setuptools and away from distutils following
upstream python's lead have merered (thanks Tim!). Whilst the issues are
resolved for core, work remains on other layers such as meta-oe.
*   The autobuilder does look improved from an intermittent failure
perspective but we're seeing hangs for unknown reasons on debian9
oe-selftest (seems python pthread mutex related) and on ltp on the arm
worker. Sadly the open issues are at an all time high.
*   Patches to disable the network outside of do_fetch have merged.
*   Support for improved SPDX info for the kernel has merged (thanks
Saul).
*   CVE issues had a bad week with further significant increases for
master and stable branches. Some patches have merged to improve master
(thanks Ross!).
*   Intermittent issues continue to be at record high levels and help is
very much welcome in trying to resolve them. You can see the list of
failures we're continuing to see by searching for the "AB-INT" tag in
bugzilla:

https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT

 

Ways to contribute:

*   There are bugs identified as possible for newcomers to the project:

https://wiki.yoctoproject.org/wiki/Newcomers
*   There are bugs that are currently unassigned for YP 3.5. See:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.5_Unassigned_Enhan
cements.2FBugs
*   We'd welcome new maintainers for recipes in OE-Core. Please see the
list at:

http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/main
tainers.inc and discuss with the existing maintainer, or ask on the OE-Core
mailing list. We will likely move a chunk of these to "Unassigned" soon to
help facilitate this.

 

YP 3.5 Milestone Dates:

*   YP 3.5 M2 build date 2022/01/17
*   YP 3.5 M2 Release date 2022/01/28
*   YP 3.5 M3 build date 2022/02/21
*   YP 3.5 M3 Release date 2022/03/04
*   YP 3.5 M4 build date 2022/04/04
*   YP 3.5 M4 Release date 2022/04/29

 

Upcoming dot releases:

*   YP 3.1.14 build date 2022/01/24
*   YP 3.1.14 Release date 2022/02/04
*   YP 3.4.2 build date 2022/02/07
*   YP 3.4.2 Release date 2022/02/18
*   YP 3.3.5 build date 2022/02/14
*   YP 3.3.5 Release date 2022/02/25
*   YP 3.1.15 build date 2022/03/14
*   YP 3.1.15 Release date 2022/03/25
*   YP 3.4.3 build date 2022/03/21
*   YP 3.4.3 Release date 2022/04/01
*   YP 3.3.6 build date 2022/03/28
*   YP 3.3.6 Release date 2022/04/08
*   YP 3.1.16 build date 2022/04/25
*   YP 3.1.16 Release date 2022/05/06

 

Tracking Metrics:

*   WDD 2675 (last week 2655) (

https://wiki.yoctoproject.org/charts/combo.html)
*   OE-Core/Poky Patch Metrics

*   Total patches found: 1229 (last week 1234)
*   Patches in the Pending State: 345 (28%) [last week 348 (28%)]

 

The Yocto Project's technical governance is through its Technical Steering
Committee, more information is available at:

 
https://wiki.yoctoproject.org/wiki/TSC

 

The Status reports are now stored on the wiki at:

https://wiki.yoctoproject.org/wiki/Weekly_Status

 

[If anyone has suggestions for other information you'd like to see on this
weekly status update, let us know!]

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com

Re: [yocto] Honister broken WiFi communication

[Rudolf J Streif]

Hi JH,

On Tue, Jan 18, 2022, 01:54 JH  wrote:

> Hi,
>
> Has anyone successfully built a Linux image by Honister to run WiFi
> driver, connman and wpa_supplicant for WiFi interface?
>

Yes, I have, but with Network Manager instead of connman. WiFi works
just fine.

>
> I could build an image by Zeus to run WiFi driver, wpa_supplicant,
> connman and dbus well, but after upgrading to Honister, the Linux
> image building was fie, but the WiFi is now broken, the WiFi failed to
> respond DHCP the WiFi could not connect to Internet, something is
> broken between wpa_supplicant and connman which setting kernel WiFi
> driver, WiFi interface and connection. I don't see any issues in
> kernel WiFi driver, connman and wpa_supplicant, something missing in
> the Linux image failing to set up the WiF network interface.
>

There are a lot of pieces in the chain and it is not obvious from your
description where it is broken.

If you run ifconfig -a does your WiFi interface show up? If not there is an
issue with the driver. Use dmesg and filter for the driver. Often a driver
cannot load the firmware. What is your WiFi hardware?

Did you install the regulatory database?

What error messages are you seeing when attempting to connect to a WiFi
network? Did you look at the connman logs?


>
>
> Appreciate your comments.
>
> Thank you.
>
> Kind regards,
>
> - jupiter
>
> 
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55900): https://lists.yoctoproject.org/g/yocto/message/55900
Mute This Topic: https://lists.yoctoproject.org/mt/88505893/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] gdb with a broken sdk

[dacav]

On Wed, Jan 12, 2022 at 02:15:38AM +, dacav wrote:
> How can I include aarch64-foobar-gdb in the devshell's PATH?

Follow up on this thread: I've been kindly helped by kroon on #yocto.
The trick consists in adding a build-time dependency to gdb-cross-aarch64
in my recipe:

DEPEND = "gdb-cross-aarch64"

At this point I can just use `bitbake -c devshell $myrecipe` and the
debugger is available.

Bonus: the devshell turns out to be very useful as a replacement
for the SDK: the environment allows me to do the cross-compilation
with just a `make`, while earlier I needed to run `bitbake $myrecipe`
and wait several seconds.


- dacav

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55899): https://lists.yoctoproject.org/g/yocto/message/55899
Mute This Topic: https://lists.yoctoproject.org/mt/88397912/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Advertise lore.kernel.org archives on website?

[Richard Purdie]

On Tue, 2022-01-18 at 10:44 +0100, Michael Opdenacker wrote:
> Greetings,
> 
> I see more and more people using links to the lore.kernel.org archives,
> for example the ones for this list: https://lore.kernel.org/yocto/
> 
> These look more convenient to use than the ones on
> https://lists.yoctoproject.org/.
> 
> So what about advertising such archives on
> https://www.yoctoproject.org/community/mailing-lists/, at least for the
> ones which have archives on lore.kernel.org? I was thinking about just
> adding an "(archives)" or "(archives / public mailbox) link at the end
> of the description for each list.
> 
> What do you think?

Sounds fine to me.

Cheers,

Richard


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55898): https://lists.yoctoproject.org/g/yocto/message/55898
Mute This Topic: https://lists.yoctoproject.org/mt/88505838/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Honister broken WiFi communication

[JH]

Hi,

Has anyone successfully built a Linux image by Honister to run WiFi
driver, connman and wpa_supplicant for WiFi interface?

I could build an image by Zeus to run WiFi driver, wpa_supplicant,
connman and dbus well, but after upgrading to Honister, the Linux
image building was fie, but the WiFi is now broken, the WiFi failed to
respond DHCP the WiFi could not connect to Internet, something is
broken between wpa_supplicant and connman which setting kernel WiFi
driver, WiFi interface and connection. I don't see any issues in
kernel WiFi driver, connman and wpa_supplicant, something missing in
the Linux image failing to set up the WiF network interface.

Appreciate your comments.

Thank you.

Kind regards,

- jupiter

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55897): https://lists.yoctoproject.org/g/yocto/message/55897
Mute This Topic: https://lists.yoctoproject.org/mt/88505893/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Advertise lore.kernel.org archives on website?

[Michael Opdenacker]

Greetings,

I see more and more people using links to the lore.kernel.org archives,
for example the ones for this list: https://lore.kernel.org/yocto/

These look more convenient to use than the ones on
https://lists.yoctoproject.org/.

So what about advertising such archives on
https://www.yoctoproject.org/community/mailing-lists/, at least for the
ones which have archives on lore.kernel.org? I was thinking about just
adding an "(archives)" or "(archives / public mailbox) link at the end
of the description for each list.

What do you think?
Cheers
Michael.

-- 
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55896): https://lists.yoctoproject.org/g/yocto/message/55896
Mute This Topic: https://lists.yoctoproject.org/mt/88505838/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto][linux-yocto v5.10/standard/nxp-sdk-5.10/nxp-soc & v5.10/standard/preempt-rt/nxp-sdk-5.10/nxp-soc][PATCH 2/2] drm/imx: Fix a build error No rule to make target 'ipuv3-crtc.o'

[Xiaolei Wang]

ipuv3 has been moved to a new directory, so delete it from Makefile

Fixes: 927cbb68a3ab2 ("drm/imx: ipuv3-kms: Move to a new ipuv3 folder")
Signed-off-by: Xiaolei Wang 
---
 drivers/gpu/drm/imx/Makefile | 1 -
 1 file changed, 1 deletion(-)

diff --git a/drivers/gpu/drm/imx/Makefile b/drivers/gpu/drm/imx/Makefile
index 28f9fe6697a7..4764058d9adf 100644
--- a/drivers/gpu/drm/imx/Makefile
+++ b/drivers/gpu/drm/imx/Makefile
@@ -13,7 +13,6 @@ obj-$(CONFIG_DRM_IMX8QXP_LDB) += imx8qxp-ldb.o
 obj-$(CONFIG_DRM_IMX8MP_LDB) += imx8mp-ldb.o
 
 imx-ipuv3-crtc-objs  := ipuv3-crtc.o ipuv3-plane.o ipuv3-kms.o
-obj-$(CONFIG_DRM_IMX_IPUV3)+= imx-ipuv3-crtc.o
 obj-$(CONFIG_DRM_IMX_DPU) += dpu/
 obj-$(CONFIG_DRM_IMX_IPUV3) += ipuv3/
 obj-$(CONFIG_DRM_IMX_HDMI) += dw_hdmi-imx.o
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#10834): 
https://lists.yoctoproject.org/g/linux-yocto/message/10834
Mute This Topic: https://lists.yoctoproject.org/mt/88505280/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto][linux-yocto v5.10/standard/nxp-sdk-5.10/nxp-soc & v5.10/standard/preempt-rt/nxp-sdk-5.10/nxp-soc][PATCH 1/2] clk: imx: Fix a build error too many arguments 'imx_register_uart_clocks' in

[Xiaolei Wang]

Since commit 247a98a4a2dcb("clk: imx: enable the earlycon
uart clocks by parsing from dt") imx_register_uart_clocks
no longer requires parameters, so delete the incoming parameters

Signed-off-by: Xiaolei Wang 
---
 drivers/clk/imx/clk-imx6q.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/clk/imx/clk-imx6q.c b/drivers/clk/imx/clk-imx6q.c
index 34c2efc69073..f906b46338f3 100644
--- a/drivers/clk/imx/clk-imx6q.c
+++ b/drivers/clk/imx/clk-imx6q.c
@@ -1058,6 +1058,6 @@ static void __init imx6q_clocks_init(struct device_node 
*ccm_node)
   hws[IMX6QDL_CLK_PLL3_USB_OTG]->clk);
}
 
-   imx_register_uart_clocks(2);
+   imx_register_uart_clocks();
 }
 CLK_OF_DECLARE(imx6q, "fsl,imx6q-ccm", imx6q_clocks_init);
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#10833): 
https://lists.yoctoproject.org/g/linux-yocto/message/10833
Mute This Topic: https://lists.yoctoproject.org/mt/88505199/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto]: [kernel for intel-socfpga]: intel-socfpga: improve dts files for FPGA design

[Meng Li]

From: Limeng 

Hi Bruce,

There are below 2 pathces to improve dts files for FPGA design

Could you please help to merge them into linux-ycoto kernel repo, both standard 
and rt branches
v5.10/standard/intel-sdk-5.10/intel-socfpga
v5.10/standard/preempt-rt/intel-sdk-5.10/intel-socfpga

diffstat info as below:

 socfpga_stratix10_socdk.dts   |2 ++
 socfpga_stratix10_socdk_ghrd.dts  |1 +
 socfpga_stratix10_socdk_pcie.dts  |1 +
 socfpga_stratix10_socdk_sgmii.dts |3 +++
 4 files changed, 7 insertions(+)


thanks,
Limeng

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#10830): 
https://lists.yoctoproject.org/g/linux-yocto/message/10830
Mute This Topic: https://lists.yoctoproject.org/mt/88505013/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto] [PATCH 1/2] aarch: arm64: dts: add #clock-cells property in gmac node

[Meng Li]

When kernel boots up, there is below log info:
OF: /soc/bridge@8000/phy@0x10040: could not get #clock-cells for 
/soc/ethernet@ff802000
Because of lacking the #clock-cells property in gmac node, add it
refer to patch in below link:
https://releases.rocketboards.org/release/2021.11/dts-source/stratix10/gsrd/

Signed-off-by: Meng Li 
---
 arch/arm64/boot/dts/altera/socfpga_stratix10_socdk_sgmii.dts | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/arch/arm64/boot/dts/altera/socfpga_stratix10_socdk_sgmii.dts 
b/arch/arm64/boot/dts/altera/socfpga_stratix10_socdk_sgmii.dts
index 902262ed3ac2..76395decd44d 100644
--- a/arch/arm64/boot/dts/altera/socfpga_stratix10_socdk_sgmii.dts
+++ b/arch/arm64/boot/dts/altera/socfpga_stratix10_socdk_sgmii.dts
@@ -74,12 +74,14 @@
 
  {
 altr,gmii-to-sgmii-converter = <_1_gmii2sgmii>;
+   #clock-cells = <1>;
 phy-mode = "sgmii";
 status = "okay";
 };
 
  {
 altr,gmii-to-sgmii-converter = <_2_gmii2sgmii>;
+   #clock-cells = <1>;
 phy-mode = "sgmii";
 status = "okay";
 };
-- 
2.17.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#10831): 
https://lists.yoctoproject.org/g/linux-yocto/message/10831
Mute This Topic: https://lists.yoctoproject.org/mt/88505015/21656
Mute 
#clock-cells:https://lists.yoctoproject.org/g/linux-yocto/mutehashtag/clock-cells
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto] [PATCH 2/2] aarch: arm64: dts: add condition to include qse dtsi file

[Meng Li]

This issue is introduced by sdk commit 2345bf39fa33("HSD#1509827762:
arm64: dts: stratix10: add Intel FPGA Quad Speed Ethernet for Stratix10").
The qse feature is included latest Intel standard PFGA design by default, so
above commit add qse related dts node, and is included in dts files. But for
other FPGA designs(PCIe, GPIO and SGMII), the recorresponding dts files
don't need the qse feature, so add a condition to control whether include
the qse dtsi file or not.

Signed-off-by: Meng Li 
---
 arch/arm64/boot/dts/altera/socfpga_stratix10_socdk.dts   | 2 ++
 arch/arm64/boot/dts/altera/socfpga_stratix10_socdk_ghrd.dts  | 1 +
 arch/arm64/boot/dts/altera/socfpga_stratix10_socdk_pcie.dts  | 1 +
 arch/arm64/boot/dts/altera/socfpga_stratix10_socdk_sgmii.dts | 1 +
 4 files changed, 5 insertions(+)

diff --git a/arch/arm64/boot/dts/altera/socfpga_stratix10_socdk.dts 
b/arch/arm64/boot/dts/altera/socfpga_stratix10_socdk.dts
index c3624e455d21..6af2ebafbc35 100644
--- a/arch/arm64/boot/dts/altera/socfpga_stratix10_socdk.dts
+++ b/arch/arm64/boot/dts/altera/socfpga_stratix10_socdk.dts
@@ -4,7 +4,9 @@
  */
 
 #include "socfpga_stratix10.dtsi"
+#ifndef DISABLE_QSE
 #include "socfpga_stratix10_qse.dtsi"
+#endif
 
 / {
model = "SoCFPGA Stratix 10 SoCDK";
diff --git a/arch/arm64/boot/dts/altera/socfpga_stratix10_socdk_ghrd.dts 
b/arch/arm64/boot/dts/altera/socfpga_stratix10_socdk_ghrd.dts
index a05fd640b2e5..ccacd54e536c 100644
--- a/arch/arm64/boot/dts/altera/socfpga_stratix10_socdk_ghrd.dts
+++ b/arch/arm64/boot/dts/altera/socfpga_stratix10_socdk_ghrd.dts
@@ -3,6 +3,7 @@
  * Copyright Altera Corporation (C) 2021. All rights reserved.
  */
 
+#define DISABLE_QSE
 #include "socfpga_stratix10_socdk.dts"
 
 /{
diff --git a/arch/arm64/boot/dts/altera/socfpga_stratix10_socdk_pcie.dts 
b/arch/arm64/boot/dts/altera/socfpga_stratix10_socdk_pcie.dts
index 9b9f9d730142..37a5c6c1c74b 100644
--- a/arch/arm64/boot/dts/altera/socfpga_stratix10_socdk_pcie.dts
+++ b/arch/arm64/boot/dts/altera/socfpga_stratix10_socdk_pcie.dts
@@ -3,6 +3,7 @@
  * Copyright Altera Corporation (C) 2019. All rights reserved.
  */
 
+#define DISABLE_QSE
 #include "socfpga_stratix10_socdk.dts"
 
 / {
diff --git a/arch/arm64/boot/dts/altera/socfpga_stratix10_socdk_sgmii.dts 
b/arch/arm64/boot/dts/altera/socfpga_stratix10_socdk_sgmii.dts
index 76395decd44d..725bfceb3535 100644
--- a/arch/arm64/boot/dts/altera/socfpga_stratix10_socdk_sgmii.dts
+++ b/arch/arm64/boot/dts/altera/socfpga_stratix10_socdk_sgmii.dts
@@ -3,6 +3,7 @@
  * Copyright Altera Corporation (C) 2021. All rights reserved.
  */
 
+#define DISABLE_QSE
 #include "socfpga_stratix10_socdk.dts"
 
 /{
-- 
2.17.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#10832): 
https://lists.yoctoproject.org/g/linux-yocto/message/10832
Mute This Topic: https://lists.yoctoproject.org/mt/88505019/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-