Re: [yocto] OS-less SDK
On 4/29/22 4:51 AM, Alessio Igor Bogani wrote: Dear Yocto developers, Is there a way to generate an SDK which contains the toolchain for bare-metal systems (i.e. MCU without operating system)? its possible to build baremetal toolchains, e.g. look at meta-riscv baremetal machines e.g. https://github.com/riscv/meta-riscv/blob/master/conf/machine/baremetal-riscv32.conf you can do MACHINE=baremetal-riscv32 bitbake meta-toolchain Which will give you a toolchain, but if you want more like what we can do with MCU OSes like freertos and zephyr take a look at meta-zephyr (https://git.yoctoproject.org/meta-zephyr/) and meta-freertos (https://github.com/aehs29/meta-freertos) Thanks in advance! Ciao, Alessio -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#56964): https://lists.yoctoproject.org/g/yocto/message/56964 Mute This Topic: https://lists.yoctoproject.org/mt/90774037/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Adding systemd to yocto
On Thu, 28 Apr 2022, Joel Winarske wrote: > Line 30-36 include changes to convert a sysvinit image to systemd. > https://github.com/jwinarske/manifests/blob/honister/conf/rpi64_config#L30 The INIT_MANAGER variable added in zeus removes the need to tinker with DISTRO_FEATURES and VIRTUAL-RUNTIME* variables, all it takes to use systemd is INIT_MANAGER = "systemd". See: meta/conf/distro/include/init-manager-systemd.inc for what it tweaks. Scott -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#56963): https://lists.yoctoproject.org/g/yocto/message/56963 Mute This Topic: https://lists.yoctoproject.org/mt/90758452/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Question about initramfs and fitImage
Hello Khoi, This might be is your starting point: https://www.yoctoproject.org/pipermail/yocto/2018-July/041680.html Zee ___ On Thu, Apr 28, 2022 at 11:13 PM Khoi Dinh Trinh wrote: > > Hi All, > > I'm trying to build an image that uses the currently built image as the > initramfs instead of having to specify it in "INITRAMFS_IMAGE". For example, > when I run "bibake image-something", I'm hoping to use the recipe > "image-something" as the initramfs with the end goal that it's used in > creating a fit image. AFAIK, INITRAMFS_IMAGE has to be hardcoded instead of > being dynamically set to the name of the currently built recipe(which I > completely understand since the recipe being built might not necessarily be > an image) and this makes it easy to boot the wrong thing since the recipe > specified with bitbake isn't the thing being used for booting. > > My workaround so far is to create my own image recipe and set it to depend on > the image being built(specifically depend on the .cpio.gz one), however, a > lot of it is duplicate of the current fit image code. > > Our use case is that we use initramfs as our only rootfs storage to make > checksum at boot easier(since the final rootfs is a .cpio.gz blob) and also > to avoid any writes to rootfs to persist across reboot. > > -- > Best, > Khoi Trinh > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#56962): https://lists.yoctoproject.org/g/yocto/message/56962 Mute This Topic: https://lists.yoctoproject.org/mt/90763430/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] Yocto cyrillic characters support #yocto
I am having trouble creating files with cyrillic characters on a yocto generated image. For eg. If I try to create a file like : # touch 1Черная I do get: # ls 1?? I have verified that my locale has utf8 support: # locale LANG=en_GB.utf8 LC_CTYPE="en_GB.utf8" LC_NUMERIC="en_GB.utf8" LC_TIME="en_GB.utf8" LC_COLLATE="en_GB.utf8" LC_MONETARY="en_GB.utf8" LC_MESSAGES="en_GB.utf8" LC_PAPER="en_GB.utf8" LC_NAME="en_GB.utf8" LC_ADDRESS="en_GB.utf8" LC_TELEPHONE="en_GB.utf8" LC_MEASUREMENT="en_GB.utf8" LC_IDENTIFICATION="en_GB.utf8" LC_ALL=en_GB.utf8 What could I be missing and how can I create files with cyrillic characters? Regards Ash -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#56961): https://lists.yoctoproject.org/g/yocto/message/56961 Mute This Topic: https://lists.yoctoproject.org/mt/90776055/21656 Mute #yocto:https://lists.yoctoproject.org/g/yocto/mutehashtag/yocto Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] OS-less SDK
Hello Alessio, > On Fri, 29 Apr 2022, 13:52 Alessio Igor Bogani, > wrote: >> Is there a way to generate an SDK which contains the toolchain for >> bare-metal systems (i.e. MCU without operating system)? Good question. I know Xilinx has put effort to support their MCUs with Yocto. However, define what you mean by SDK? Which libraries or programming languages are you thinking of beyond the C library for example? On Fri, Apr 29, 2022 at 1:58 PM Laurent Gauthier wrote: > Have you had a look at crosstool-ng? > crosstool-ng is mostly the toolchain, I would not consider this an SDK beyond that. This might help: https://elinux.org/images/e/e6/ELC-Yocto-Crosstool-ng.pdf Regards, Leon. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#56960): https://lists.yoctoproject.org/g/yocto/message/56960 Mute This Topic: https://lists.yoctoproject.org/mt/90774037/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] [PATCH yocto-autobuilder-helper] config.json: also build meta-virt for qemuarm
Signed-off-by: Ross Burton
---
config.json | 5 +
1 file changed, 5 insertions(+)
diff --git a/config.json b/config.json
index dc59d7f..afae5e9 100644
--- a/config.json
+++ b/config.json
@@ -954,6 +954,11 @@
"shortname": "Xen for qemuarm64",
"MACHINE": "qemuarm64",
"BBTARGETS" : "xen-image-minimal"
+},
+"step3" : {
+"shortname": "Xen for qemuarm",
+"MACHINE": "qemuarm",
+"BBTARGETS" : "xen-image-minimal"
}
},
"qa-extras" : {
--
2.25.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56959): https://lists.yoctoproject.org/g/yocto/message/56959
Mute This Topic: https://lists.yoctoproject.org/mt/90775427/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [yocto] [qa-build-notification] QA notification for completed autobuilder build (yocto-3.1.16.rc1)
On Fri, 2022-04-29 at 05:32 +, Teoh, Jay Shen wrote: > Hi All, > > This is the full report for yocto-3.1.16.rc1: > https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults > > === Summary > No high milestone defects. > > No new issue found. Thanks! The TSC did discuss the perf issue earlier in the week and were good to release if there were no other issues found, we should therefore be good to release. Cheers, Richard -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#56958): https://lists.yoctoproject.org/g/yocto/message/56958 Mute This Topic: https://lists.yoctoproject.org/mt/90775116/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] [PATCH yocto-autobuilder2 v2] config.py: add meta-virtualization to a-full
On Fri, Apr 29, 2022 at 8:14 AM Ross Burton wrote:
>
> The meta-virtualization builder is reliable and useful now, so add it to
> a-full.
Acked-by: Bruce Ashfield
The meta-virtualization "team" will do my best to respond to breakages
in a timely manner :)
Bruce
>
> Signed-off-by: Ross Burton
> ---
> config.py | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/config.py b/config.py
> index 17ccd21..c1c8c7e 100644
> --- a/config.py
> +++ b/config.py
> @@ -10,7 +10,7 @@ buildertorepos = {
> "a-quick": ["poky", "meta-intel", "oecore", "bitbake",
> "meta-mingw", "meta-gplv2"],
> "a-full": ["poky", "meta-intel", "oecore", "bitbake",
> -"meta-mingw", "meta-gplv2", "meta-arm", "meta-aws",
> "meta-agl", "meta-openembedded"],
> +"meta-mingw", "meta-gplv2", "meta-arm", "meta-aws",
> "meta-agl", "meta-openembedded", "meta-virtualization"],
> "non-gpl3": ["poky", "meta-gplv2"],
> "meta-mingw": ["poky", "meta-mingw"],
> "qa-extras": ["poky", "meta-mingw"],
> @@ -88,7 +88,7 @@ trigger_builders_wait_full = trigger_builders_wait_shared +
> [
> "qemumips-alt", "edgerouter-alt", "qemuppc-alt", "qemux86-world-alt",
> "oe-selftest-ubuntu", "oe-selftest-debian", "oe-selftest-fedora",
> "oe-selftest-centos",
> "qemux86-64-ptest", "qemux86-64-ltp", "qemuarm64-ptest", "qemuarm64-ltp",
> -"meta-intel", "meta-arm", "meta-aws", "meta-agl-core"
> +"meta-intel", "meta-arm", "meta-aws", "meta-agl-core", "meta-virt"
> ]
>
> trigger_builders_wait_quick_releases = {
> --
> 2.25.1
>
>
>
>
--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56957): https://lists.yoctoproject.org/g/yocto/message/56957
Mute This Topic: https://lists.yoctoproject.org/mt/90774395/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] [PATCH yocto-autobuilder-helper] config.json: rename meta-virt to meta-virtualization
I’m retracting this, more places need to handle the rename and we can just live
with the short name.
Ross
> On 29 Apr 2022, at 10:58, Ross Burton via lists.yoctoproject.org
> wrote:
>
> Use the name of the layer instead of a contraction, for clarity.
>
> Signed-off-by: Ross Burton
> ---
> config.json | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/config.json b/config.json
> index dc59d7f..a8d0e20 100644
> --- a/config.json
> +++ b/config.json
> @@ -933,7 +933,7 @@
> "BBTARGETS" : "world -k"
> }
> },
> -"meta-virt" : {
> +"meta-virtualization" : {
> "NEEDREPOS" : ["poky", "meta-openembedded",
> "meta-virtualization"],
> "ADDLAYER" : [
> "${BUILDDIR}/../meta-openembedded/meta-oe",
> --
> 2.25.1
>
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56956): https://lists.yoctoproject.org/g/yocto/message/56956
Mute This Topic: https://lists.yoctoproject.org/mt/90772735/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] [PATCH yocto-autobuilder2 v2] config.py: add meta-virtualization to a-full
The meta-virtualization builder is reliable and useful now, so add it to
a-full.
Signed-off-by: Ross Burton
---
config.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/config.py b/config.py
index 17ccd21..c1c8c7e 100644
--- a/config.py
+++ b/config.py
@@ -10,7 +10,7 @@ buildertorepos = {
"a-quick": ["poky", "meta-intel", "oecore", "bitbake",
"meta-mingw", "meta-gplv2"],
"a-full": ["poky", "meta-intel", "oecore", "bitbake",
-"meta-mingw", "meta-gplv2", "meta-arm", "meta-aws",
"meta-agl", "meta-openembedded"],
+"meta-mingw", "meta-gplv2", "meta-arm", "meta-aws",
"meta-agl", "meta-openembedded", "meta-virtualization"],
"non-gpl3": ["poky", "meta-gplv2"],
"meta-mingw": ["poky", "meta-mingw"],
"qa-extras": ["poky", "meta-mingw"],
@@ -88,7 +88,7 @@ trigger_builders_wait_full = trigger_builders_wait_shared + [
"qemumips-alt", "edgerouter-alt", "qemuppc-alt", "qemux86-world-alt",
"oe-selftest-ubuntu", "oe-selftest-debian", "oe-selftest-fedora",
"oe-selftest-centos",
"qemux86-64-ptest", "qemux86-64-ltp", "qemuarm64-ptest", "qemuarm64-ltp",
-"meta-intel", "meta-arm", "meta-aws", "meta-agl-core"
+"meta-intel", "meta-arm", "meta-aws", "meta-agl-core", "meta-virt"
]
trigger_builders_wait_quick_releases = {
--
2.25.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56955): https://lists.yoctoproject.org/g/yocto/message/56955
Mute This Topic: https://lists.yoctoproject.org/mt/90774395/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] OS-less SDK
Hi Alessio, Have you had a look at crosstool-ng? Best regards, Laurent. On Fri, 29 Apr 2022, 13:52 Alessio Igor Bogani, wrote: > Dear Yocto developers, > > Is there a way to generate an SDK which contains the toolchain for > bare-metal systems (i.e. MCU without operating system)? > > Thanks in advance! > > Ciao, > Alessio > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#56954): https://lists.yoctoproject.org/g/yocto/message/56954 Mute This Topic: https://lists.yoctoproject.org/mt/90774037/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] OS-less SDK
Dear Yocto developers, Is there a way to generate an SDK which contains the toolchain for bare-metal systems (i.e. MCU without operating system)? Thanks in advance! Ciao, Alessio -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#56953): https://lists.yoctoproject.org/g/yocto/message/56953 Mute This Topic: https://lists.yoctoproject.org/mt/90774037/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] [PATCH yocto-autobuilder2] config.py: add meta-virtualization to a-full
The meta-virtualization builder is reliable and useful now, so add it to
a-full.
Signed-off-by: Ross Burton
---
config.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/config.py b/config.py
index 17ccd21..bec61b1 100644
--- a/config.py
+++ b/config.py
@@ -10,7 +10,7 @@ buildertorepos = {
"a-quick": ["poky", "meta-intel", "oecore", "bitbake",
"meta-mingw", "meta-gplv2"],
"a-full": ["poky", "meta-intel", "oecore", "bitbake",
-"meta-mingw", "meta-gplv2", "meta-arm", "meta-aws",
"meta-agl", "meta-openembedded"],
+"meta-mingw", "meta-gplv2", "meta-arm", "meta-aws",
"meta-agl", "meta-openembedded", "meta-virtualization"],
"non-gpl3": ["poky", "meta-gplv2"],
"meta-mingw": ["poky", "meta-mingw"],
"qa-extras": ["poky", "meta-mingw"],
@@ -88,7 +88,7 @@ trigger_builders_wait_full = trigger_builders_wait_shared + [
"qemumips-alt", "edgerouter-alt", "qemuppc-alt", "qemux86-world-alt",
"oe-selftest-ubuntu", "oe-selftest-debian", "oe-selftest-fedora",
"oe-selftest-centos",
"qemux86-64-ptest", "qemux86-64-ltp", "qemuarm64-ptest", "qemuarm64-ltp",
-"meta-intel", "meta-arm", "meta-aws", "meta-agl-core"
+"meta-intel", "meta-arm", "meta-aws", "meta-agl-core",
"meta-virtualization"
]
trigger_builders_wait_quick_releases = {
--
2.25.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56952): https://lists.yoctoproject.org/g/yocto/message/56952
Mute This Topic: https://lists.yoctoproject.org/mt/90772737/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] [PATCH yocto-autobuilder-helper] config.json: rename meta-virt to meta-virtualization
Use the name of the layer instead of a contraction, for clarity.
Signed-off-by: Ross Burton
---
config.json | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/config.json b/config.json
index dc59d7f..a8d0e20 100644
--- a/config.json
+++ b/config.json
@@ -933,7 +933,7 @@
"BBTARGETS" : "world -k"
}
},
-"meta-virt" : {
+"meta-virtualization" : {
"NEEDREPOS" : ["poky", "meta-openembedded", "meta-virtualization"],
"ADDLAYER" : [
"${BUILDDIR}/../meta-openembedded/meta-oe",
--
2.25.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56951): https://lists.yoctoproject.org/g/yocto/message/56951
Mute This Topic: https://lists.yoctoproject.org/mt/90772735/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[linux-yocto] [PATCH 2/2] driver: net: dpaa: release resource when executing kexec
When running kexec feature, it needs to release dpaa ethernet
driver and fman resource so that the second kernel can bootup
normally. So, create shutdown callback functions to improve ethernet
driver.
Signed-off-by: Meng Li
---
.../ethernet/freescale/sdk_dpaa/dpaa_eth.c| 3 +++
.../freescale/sdk_dpaa/dpaa_eth_common.c | 20 +++
.../freescale/sdk_dpaa/dpaa_eth_common.h | 3 +++
.../sdk_fman/src/wrapper/lnxwrp_fm.c | 18 +
4 files changed, 44 insertions(+)
diff --git a/drivers/net/ethernet/freescale/sdk_dpaa/dpaa_eth.c
b/drivers/net/ethernet/freescale/sdk_dpaa/dpaa_eth.c
index e20a4351afb1..7f309229b5f1 100644
--- a/drivers/net/ethernet/freescale/sdk_dpaa/dpaa_eth.c
+++ b/drivers/net/ethernet/freescale/sdk_dpaa/dpaa_eth.c
@@ -1161,6 +1161,9 @@ static struct platform_driver dpa_driver = {
.pm = DPAA_PM_OPS,
},
.probe = dpaa_eth_priv_probe,
+#if defined(CONFIG_KEXEC)
+ .shutdown = dpa_shutdown,
+#endif
.remove = dpa_remove
};
diff --git a/drivers/net/ethernet/freescale/sdk_dpaa/dpaa_eth_common.c
b/drivers/net/ethernet/freescale/sdk_dpaa/dpaa_eth_common.c
index 13a31b59036a..42776555d1f5 100644
--- a/drivers/net/ethernet/freescale/sdk_dpaa/dpaa_eth_common.c
+++ b/drivers/net/ethernet/freescale/sdk_dpaa/dpaa_eth_common.c
@@ -510,6 +510,26 @@ int __cold dpa_remove(struct platform_device *of_dev)
}
EXPORT_SYMBOL(dpa_remove);
+#if defined(CONFIG_KEXEC)
+void __cold dpa_shutdown(struct platform_device *of_dev)
+{
+ struct device *dev;
+ struct net_device *net_dev;
+ struct dpa_priv_s *priv;
+
+ dev = _dev->dev;
+ net_dev = dev_get_drvdata(dev);
+
+ priv = netdev_priv(net_dev);
+
+ dpa_fq_free(dev, >dpa_fq_list);
+
+ dpa_bp_free(priv);
+
+ return;
+}
+#endif
+
struct mac_device * __cold __must_check
__attribute__((nonnull))
dpa_mac_probe(struct platform_device *_of_dev)
diff --git a/drivers/net/ethernet/freescale/sdk_dpaa/dpaa_eth_common.h
b/drivers/net/ethernet/freescale/sdk_dpaa/dpaa_eth_common.h
index c686d04f1c05..a6df8bf97ab6 100644
--- a/drivers/net/ethernet/freescale/sdk_dpaa/dpaa_eth_common.h
+++ b/drivers/net/ethernet/freescale/sdk_dpaa/dpaa_eth_common.h
@@ -158,6 +158,9 @@ int dpa_get_ts(const struct dpa_priv_s *priv, enum
port_type rx_tx,
#endif /* CONFIG_FSL_DPAA_TS */
int dpa_ioctl(struct net_device *dev, struct ifreq *rq, int cmd);
int __cold dpa_remove(struct platform_device *of_dev);
+#if defined(CONFIG_KEXEC)
+void __cold dpa_shutdown(struct platform_device *of_dev);
+#endif
struct mac_device * __cold __must_check
__attribute__((nonnull)) dpa_mac_probe(struct platform_device *_of_dev);
int dpa_set_mac_address(struct net_device *net_dev, void *addr);
diff --git a/drivers/net/ethernet/freescale/sdk_fman/src/wrapper/lnxwrp_fm.c
b/drivers/net/ethernet/freescale/sdk_fman/src/wrapper/lnxwrp_fm.c
index 3fa99df195ac..da327b6accfb 100755
--- a/drivers/net/ethernet/freescale/sdk_fman/src/wrapper/lnxwrp_fm.c
+++ b/drivers/net/ethernet/freescale/sdk_fman/src/wrapper/lnxwrp_fm.c
@@ -1337,6 +1337,21 @@ static int fm_remove(struct platform_device *of_dev)
return 0;
}
+#if defined(CONFIG_KEXEC)
+static void fm_shutdown(struct platform_device *of_dev)
+{
+ t_LnxWrpFmDev *p_LnxWrpFmDev;
+ struct device *dev;
+
+ dev = _dev->dev;
+ p_LnxWrpFmDev = dev_get_drvdata(dev);
+ if (!p_LnxWrpFmDev->active)
+ return;
+
+ FreeFmPcdDev(p_LnxWrpFmDev);
+}
+#endif
+
static const struct of_device_id fm_match[] = {
{
.compatible= "fsl,fman"
@@ -1414,6 +1429,9 @@ static struct platform_driver fm_driver = {
.pm = FM_PM_OPS,
},
.probe = fm_probe,
+#if defined(CONFIG_KEXEC)
+.shutdown = fm_shutdown,
+#endif
.remove = fm_remove
};
--
2.35.3
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#11270):
https://lists.yoctoproject.org/g/linux-yocto/message/11270
Mute This Topic: https://lists.yoctoproject.org/mt/90772519/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] dpaa: make sure FM_PORT_Free work reasonably
From: Tiejun Chen When perform kexec or reboot, kernel may panic as follows: Oops: Kernel access of bad area, sig: 11 [#1] PREEMPT SMP NR_CPUS=8 LTT NESTING LEVEL : 0 B4 QDS Modules linked in: NIP: c0603680 LR: c06037d8 CTR: c0578c70 REGS: c000f83c3470 TRAP: 0300 Tainted: GW (3.4.43-rt56-WR5.0.1.0_preempt-rt) MSR: 80029000 CR: 44024022 XER: SOFTE: 1 DEAR: 0038, ESR: TASK = c000f999c840[1620] 'kexec' THREAD: c000f83c CPU: 7 GPR00: 0005 c000f83c36f0 c116e800 c000f999e000 GPR04: c000f83c3760 0001 0001 GPR08: c79e30d0 06e6 8000 GPR12: 24024082 cc00 10029f88 0001 GPR16: 0002 GPR20: 0002 100327b8 10013400 GPR24: 0002 0fffeb57a4d8 c11ba810 c0ffd038 GPR28: c000f9959600 0018 c10bd6c0 c000f995d800 NIP [c0603680] .FM_PORT_Free+0x90/0x300 LR [c06037d8] .FM_PORT_Free+0x1e8/0x300 Call Trace: [c000f83c36f0] [c06037d8] .FM_PORT_Free+0x1e8/0x300 (unreliable) [c000f83c3790] [c061ad64] .FmHcFree+0x74/0xa0 [c000f83c3820] [c05d742c] .FM_PCD_Free+0xfc/0x2e0 [c000f83c38c0] [c0630f6c] .FreeFmPcdDev+0x2c/0x80 [c000f83c3940] [c062b54c] .FreeFmDev.part.3+0x2c/0x190 [c000f83c39c0] [c0922288] .fm_remove+0xa4/0x198 [c000f83c3a50] [c0518d60] .platform_drv_shutdown+0x40/0x60 [c000f83c3ad0] [c05137b8] .device_shutdown+0x58/0x150 [c000f83c3b60] [c0081314] .kernel_restart_prepare+0x54/0x70 [c000f83c3be0] [c00da798] .kernel_kexec+0x138/0x190 [c000f83c3c90] [c00816a4] .SyS_reboot+0x284/0x2d0 [c000f83c3e30] [c720] syscall_exit+0x0/0x60 Instruction dump: 41de0014 4804f89d 6000 3800 f81f0270 893f0062 38810070 801f003c e87f0020 99210070 3920 90010074 <88090038> 98010078 4bf75fa9 6000 Segmentation fault This is introduced while accessing that invalid p_FmPort->p_FmPortDriverParam by FM_PORT_Free(). So we should check if p_FmPort->p_FmPortDriverParam is already freed somewhere, and especially inside FM_PORT_Free(), we also need to push FmPortDriverParamFree(p_FmPort) downwards to guarantee this. Signed-off-by: Tiejun Chen Signed-off-by: Bin Jiang Signed-off-by: Meng Li --- .../freescale/sdk_fman/Peripherals/FM/Port/fm_port.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/net/ethernet/freescale/sdk_fman/Peripherals/FM/Port/fm_port.c b/drivers/net/ethernet/freescale/sdk_fman/Peripherals/FM/Port/fm_port.c index a0680855dcdf..8ab18f48e1a2 100644 --- a/drivers/net/ethernet/freescale/sdk_fman/Peripherals/FM/Port/fm_port.c +++ b/drivers/net/ethernet/freescale/sdk_fman/Peripherals/FM/Port/fm_port.c @@ -2788,13 +2788,11 @@ t_Error FM_PORT_Free(t_Handle h_FmPort) if (p_FmPort->imEn) FmPortImFree(p_FmPort); -FmPortDriverParamFree(p_FmPort); - memset(, 0, sizeof(fmParams)); fmParams.hardwarePortId = p_FmPort->hardwarePortId; fmParams.portType = (e_FmPortType)p_FmPort->portType; -fmParams.deqPipelineDepth = -p_FmPort->p_FmPortDriverParam->dfltCfg.tx_fifo_deq_pipeline_depth; +if (p_FmPort->p_FmPortDriverParam) + fmParams.deqPipelineDepth = p_FmPort->p_FmPortDriverParam->dfltCfg.tx_fifo_deq_pipeline_depth; FmFreePortParams(p_FmPort->h_Fm, ); @@ -2807,6 +2805,8 @@ t_Error FM_PORT_Free(t_Handle h_FmPort) FM_MURAM_FreeMem(p_FmPort->h_FmMuram, p_FmPort->p_ParamsPage); #endif /* (DPAA_VERSION >= 11) */ +FmPortDriverParamFree(p_FmPort); + if (p_FmPort->h_Spinlock) XX_FreeSpinlock(p_FmPort->h_Spinlock); -- 2.35.3 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#11268): https://lists.yoctoproject.org/g/linux-yocto/message/11268 Mute This Topic: https://lists.yoctoproject.org/mt/90772517/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/kernel-rt]: nxp-ls1046: add patches to improve kexec feature
From: Limeng Hi Bruce, The 2 patches are used to improve kexec feature So, could you please help merge these patches into linux-ycoto kernel, both below 2 branchs? v5.15/standard/nxp-sdk-5.15/nxp-soc v5.15/standard/preempt-rt/nxp-sdk-5.15/nxp-soc diffstat info as below: sdk_dpaa/dpaa_eth.c|3 +++ sdk_dpaa/dpaa_eth_common.c | 20 sdk_dpaa/dpaa_eth_common.h |3 +++ sdk_fman/Peripherals/FM/Port/fm_port.c |8 sdk_fman/src/wrapper/lnxwrp_fm.c | 18 ++ 5 files changed, 48 insertions(+), 4 deletions(-) thanks, Limeng -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#11269): https://lists.yoctoproject.org/g/linux-yocto/message/11269 Mute This Topic: https://lists.yoctoproject.org/mt/90772518/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 preempt-rt kernel v5.15]: nxp-s32g: update to align with NXP SDK
Hi Bruce, There are 33 patches from bsp33 latest update for the following branch v5.15/standard/preempt-rt/nxp-sdk-5.10/nxp-s32g Would you please help to merge these patches? The patch infos as following: The following changes since commit b8d249b238975a0eb25e88b1383c73ad25938dc2: Merge branch 'v5.15/standard/base' into v5.15/standard/preempt-rt/nxp-sdk-5.10/nxp-s32g (2022-04-28 09:27:31 -0400) are available in the Git repository at: https://github.com/zhantaotang/linux-yocto-std v5.15/standard/preempt-rt/nxp-sdk-5.10/nxp-s32g for you to fetch changes up to bbd0b4d662aa04fac9f5cc4d9359b25e066f1e2b: net: can: llce_can: add netdev notifier (2022-04-29 14:27:19 +0800) Thanks, Zhantao -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#11267): https://lists.yoctoproject.org/g/linux-yocto/message/11267 Mute This Topic: https://lists.yoctoproject.org/mt/90771248/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.15/standard/preempt-rt/nxp-sdk-5.15/nxp-soc & v5.15/standard/nxp-sdk-5.15/nxp-soc] [PATCH 1/1] dmaengine: imx-sdma: Fix the build errors for merging of 6b8af9f96749
The merge of the stable commit 6b8af9f96749 ("dmaengine:
imx-sdma: fix init of uart scripts") conflicts with the
SDK patches. That cause two duplicate variables added
and also put part of the codes into the wrong function.
This drops that two duplicate variables and move the
codes into the right function sdma_add_scripts().
Signed-off-by: Xiaolei Wang
---
drivers/dma/imx-sdma.c | 31 +--
1 file changed, 13 insertions(+), 18 deletions(-)
diff --git a/drivers/dma/imx-sdma.c b/drivers/dma/imx-sdma.c
index 945b4f011bbe..f9c4112d3c33 100644
--- a/drivers/dma/imx-sdma.c
+++ b/drivers/dma/imx-sdma.c
@@ -240,8 +240,6 @@ struct sdma_script_start_addrs {
s32 mcu_2_ecspi_addr;
s32 mcu_2_sai_addr;
s32 sai_2_mcu_addr;
- s32 uart_2_mcu_addr;
- s32 uartsh_2_mcu_addr;
s32 i2c_2_mcu_addr;
s32 mcu_2_i2c_addr;
s32 uart_2_mcu_rom_addr;
@@ -816,6 +814,19 @@ static void sdma_add_scripts(struct sdma_engine *sdma,
for (i = 0; i < sdma->script_number; i++)
if (addr_arr[i] > 0)
saddr_arr[i] = addr_arr[i];
+
+ /*
+ * For compatibility with NXP internal legacy kernel before 4.19 which
+ * is based on uart ram script and mainline kernel based on uart rom
+ * script, both uart ram/rom scripts are present in newer sdma
+ * firmware. Use the rom versions if they are present (V3 or newer).
+ */
+if (sdma->script_number >= SDMA_SCRIPT_ADDRS_ARRAY_SIZE_V3) {
+if (addr->uart_2_mcu_rom_addr)
+sdma->script_addrs->uart_2_mcu_addr =
addr->uart_2_mcu_rom_addr;
+if (addr->uartsh_2_mcu_rom_addr)
+sdma->script_addrs->uartsh_2_mcu_addr =
addr->uartsh_2_mcu_rom_addr;
+}
}
static int sdma_load_script(struct sdma_engine *sdma)
@@ -2213,22 +2224,6 @@ static void sdma_issue_pending(struct dma_chan *chan)
pm_runtime_put_autosuspend(sdmac->sdma->dev);
}
- for (i = 0; i < sdma->script_number; i++)
- if (addr_arr[i] > 0)
- saddr_arr[i] = addr_arr[i];
-
- /*
-* For compatibility with NXP internal legacy kernel before 4.19 which
-* is based on uart ram script and mainline kernel based on uart rom
-* script, both uart ram/rom scripts are present in newer sdma
-* firmware. Use the rom versions if they are present (V3 or newer).
-*/
- if (sdma->script_number >= SDMA_SCRIPT_ADDRS_ARRAY_SIZE_V3) {
- if (addr->uart_2_mcu_rom_addr)
- sdma->script_addrs->uart_2_mcu_addr =
addr->uart_2_mcu_rom_addr;
- if (addr->uartsh_2_mcu_rom_addr)
- sdma->script_addrs->uartsh_2_mcu_addr =
addr->uartsh_2_mcu_rom_addr;
- }
}
static void sdma_load_firmware(const struct firmware *fw, void *context)
--
2.25.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#11266):
https://lists.yoctoproject.org/g/linux-yocto/message/11266
Mute This Topic: https://lists.yoctoproject.org/mt/90771125/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Adding systemd to yocto
Line 30-36 include changes to convert a sysvinit image to systemd. https://github.com/jwinarske/manifests/blob/honister/conf/rpi64_config#L30 On Thu, Apr 28, 2022, 10:19 AM Edgar Mobile wrote: > Greetings, > > I tried to add systemd to weston-image-core by adding the following lines > in local.conf: > > DISTRO_FEATURES:append = " systemd" VIRTUAL-RUNTIME_init_manager = > "systemd" > > And indeed, bitbake seems to use them in somve way: > > DISTRO_FEATURES="acl alsa argp bluetooth debuginfod ext2 ipv4 ipv6 > largefile pcmcia usbgadget usbhost wifi xattr nfs zeroconf pci 3g nfc x11 > vfat seccomp largefile opengl ptest multiarch wayland vulkan systemd\" > VIRTUAL-RUNTIME_init_manager = \"systemd pulseaudio sysvinit > gobject-introspection-data ldconfig" > POKY_DEFAULT_DISTRO_FEATURES="largefile opengl ptest multiarch wayland > vulkan" > > However, if I start the system in qemu none of the expected systemd > binaries like systemd, systemd-journal etc. is present. Did I miss > something? > > Regards > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#56950): https://lists.yoctoproject.org/g/yocto/message/56950 Mute This Topic: https://lists.yoctoproject.org/mt/90758452/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
