Re: [yocto] [meta-rockchip][kirkstone][PATCH] rk3588(s): add
On Thu 2023-10-05 @ 11:00:16 AM, Quentin Schulz wrote:
> From: Trevor Woerner
>
> Unfortunately the TF-A project does not currently have support for
> the rk3588. Therefore, for the time-being, the only way to supply a
> TPL/DDR-init for the rk3588 is to use the closed-source rkbin binaries
> from Rockchip. If/when TF-A adds support for the rk3588 we can investigate
> switching.
>
> The rk3588 comes in two variants: rk3588 and rk3588s. The "s" option is a
> stripped-down version of the rk3588. In the Linux kernel these two SoCs are
> kept separate, with the rk3588 building on the rk3588s, so we've mimicked that
> same behaviour here.
>
> Signed-off-by: Quentin Schulz
> Signed-off-by: Trevor Woerner
> [backported from f8af59dd7cd7 ("rock-5b: add")]
> [removed support for rock-5b since no decent linux-yocto support in kirkstone]
> [removed KERNEL_FEATURES and kmeta since no decent linux-yocto support in
> kirkstone]
> [renamed INIT_FIRMWARE_DEPENDS to ATF_DEPENDS]
> [tested on downstream board with downstream kernel and u-boot]
> Signed-off-by: Quentin Schulz
> ---
> conf/machine/include/rk3588.inc | 6
> conf/machine/include/rk3588s.inc| 16 +++
> recipes-bsp/rkbin/rockchip-rkbin_git.bb | 37 +
> recipes-bsp/u-boot/u-boot%.bbappend | 6
> 4 files changed, 65 insertions(+)
> create mode 100644 conf/machine/include/rk3588.inc
> create mode 100644 conf/machine/include/rk3588s.inc
> create mode 100644 recipes-bsp/rkbin/rockchip-rkbin_git.bb
Applied to meta-rockchip, kirkstone branch.
Thanks!
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61340): https://lists.yoctoproject.org/g/yocto/message/61340
Mute This Topic: https://lists.yoctoproject.org/mt/101773111/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] any interest in a YP riscv mailing list?
On 2023-10-13 11:14, Ross Burton wrote: On 13 Oct 2023, at 15:20, Robert P. J. Day via lists.yoctoproject.org wrote: given that other acrhitectures have their own ML, is it reasonable that risc-v have its own mailing list? meta-arm, meta-intel etc are primarily because they take patches via the mailing list. meta-riscv (https://github.com/riscv/meta-riscv) does pull requests and issues via GitHub. If the yocto@ list ended up getting swamped with riscv-specific discussion then there’s be a case for creating a list, but architecture-specific discussion is rare. understood. rday -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#61339): https://lists.yoctoproject.org/g/yocto/message/61339 Mute This Topic: https://lists.yoctoproject.org/mt/101940855/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] any interest in a YP riscv mailing list?
On 13 Oct 2023, at 15:20, Robert P. J. Day via lists.yoctoproject.org wrote: > given that other acrhitectures have their own ML, is it reasonable > that risc-v have its own mailing list? meta-arm, meta-intel etc are primarily because they take patches via the mailing list. meta-riscv (https://github.com/riscv/meta-riscv) does pull requests and issues via GitHub. If the yocto@ list ended up getting swamped with riscv-specific discussion then there’s be a case for creating a list, but architecture-specific discussion is rare. Ross -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#61338): https://lists.yoctoproject.org/g/yocto/message/61338 Mute This Topic: https://lists.yoctoproject.org/mt/101940855/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/leave/6691583/21656/737036229/xyzzy [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] any interest in a YP riscv mailing list?
On Fri, Oct 13, 2023 at 7:25 AM Robert P. J. Day wrote: > > > given that other acrhitectures have their own ML, is it reasonable > that risc-v have its own mailing list? We do not have generic architecture specific layers, existing mailing lists should suffice for that matter. I think you are referring to BSP layer specific mailing list they also happen to main proponents of architecture, these are member maintained layers. > > rday > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#61337): https://lists.yoctoproject.org/g/yocto/message/61337 Mute This Topic: https://lists.yoctoproject.org/mt/101940855/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] [yocto-autobuilder-helper][PATCH v2] config.json: add reproducible-openembedded build
Thank you both for your comments. Jose, I just sent a fix with --newbuildir, it's quite convenient in this case, thx. Fabien -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#61336): https://lists.yoctoproject.org/g/yocto/message/61336 Mute This Topic: https://lists.yoctoproject.org/mt/101713575/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] [yocto-autobuilder-helper][PATCH] config.json : Fix repro-meta-oe layer dependency
Fix meta-filesystem build issue due to hidden dependencies (not set by
LAYERDEPENDS) smbnetfs(meta-filesystem) depends on
samba(meta-networking) that depends on python3-dnspython (meta-python)
Create new build-st dir for each layer to avoid chain of
failure between steps
Signed-off-by: Fabien Thomas
Reviewed-by: Yoann Congal
---
config.json | 22 --
1 file changed, 12 insertions(+), 10 deletions(-)
diff --git a/config.json b/config.json
index 3acb710..c01a453 100644
--- a/config.json
+++ b/config.json
@@ -303,15 +303,17 @@
],
"step1" : {
"shortname" : "Repro meta-oe/meta-filesystems",
-"EXTRACMDS" : ["${SCRIPTSDIR}/checkvnc;
OEQA_DEBUGGING_SAVED_OUTPUT=${BASE_SHAREDDIR}/pub/repro-fail-openembedded/meta-filesystems/
DISPLAY=:1 oe-selftest -r reproducible"],
+"EXTRACMDS" : ["${SCRIPTSDIR}/checkvnc;
OEQA_DEBUGGING_SAVED_OUTPUT=${BASE_SHAREDDIR}/pub/repro-fail-openembedded/meta-filesystems/
DISPLAY=:1 oe-selftest --newbuilddir $BBPATH/build-st-meta-filesystems -r
reproducible"],
"ADDLAYER" : [
"${BUILDDIR}/../meta-openembedded/meta-oe",
+"${BUILDDIR}/../meta-openembedded/meta-python",
"${BUILDDIR}/../meta-openembedded/meta-networking",
"${BUILDDIR}/../meta-openembedded/meta-filesystems"
],
"extravars" : [
"EXCLUDE_FROM_WORLD:layer-openembedded-layer = '1'",
"EXCLUDE_FROM_WORLD:layer-networking-layer = '1'",
+"EXCLUDE_FROM_WORLD:layer-meta-python = '1'",
"USERADD_UID_TABLES:append = '
files/static-passwd-meta-filesystems'",
"USERADD_GID_TABLES:append = '
files/static-group-meta-networking'",
"USERADD_UID_TABLES:append = '
files/static-passwd-meta-networking'",
@@ -321,7 +323,7 @@
},
"step2" : {
"shortname" : "Repro meta-oe/meta-gnome",
-"EXTRACMDS" : ["${SCRIPTSDIR}/checkvnc;
OEQA_DEBUGGING_SAVED_OUTPUT=${BASE_SHAREDDIR}/pub/repro-fail-openembedded/meta-gnome/
DISPLAY=:1 oe-selftest -r reproducible"],
+"EXTRACMDS" : ["${SCRIPTSDIR}/checkvnc;
OEQA_DEBUGGING_SAVED_OUTPUT=${BASE_SHAREDDIR}/pub/repro-fail-openembedded/meta-gnome/
DISPLAY=:1 oe-selftest --newbuilddir $BBPATH/build-st-meta-gnome -r
reproducible"],
"ADDLAYER" : [
"${BUILDDIR}/../meta-openembedded/meta-oe",
"${BUILDDIR}/../meta-openembedded/meta-python",
@@ -341,14 +343,14 @@
},
"step3" : {
"shortname" : "Repro meta-oe/meta-initramfs",
-"EXTRACMDS" : ["${SCRIPTSDIR}/checkvnc;
OEQA_DEBUGGING_SAVED_OUTPUT=${BASE_SHAREDDIR}/pub/repro-fail-openembedded/meta-initramfs/
DISPLAY=:1 oe-selftest -r reproducible"],
+"EXTRACMDS" : ["${SCRIPTSDIR}/checkvnc;
OEQA_DEBUGGING_SAVED_OUTPUT=${BASE_SHAREDDIR}/pub/repro-fail-openembedded/meta-initramfs/
DISPLAY=:1 oe-selftest --newbuilddir $BBPATH/build-st-meta-initramfs -r
reproducible"],
"ADDLAYER" : [
"${BUILDDIR}/../meta-openembedded/meta-initramfs"
]
},
"step4" : {
"shortname" : "Repro meta-oe/meta-multimedia",
-"EXTRACMDS" : ["${SCRIPTSDIR}/checkvnc;
OEQA_DEBUGGING_SAVED_OUTPUT=${BASE_SHAREDDIR}/pub/repro-fail-openembedded/meta-multimedia/
DISPLAY=:1 oe-selftest -r reproducible"],
+"EXTRACMDS" : ["${SCRIPTSDIR}/checkvnc;
OEQA_DEBUGGING_SAVED_OUTPUT=${BASE_SHAREDDIR}/pub/repro-fail-openembedded/meta-multimedia/
DISPLAY=:1 oe-selftest --newbuilddir $BBPATH/build-st-meta-multimedia -r
reproducible"],
"ADDLAYER" : [
"${BUILDDIR}/../meta-openembedded/meta-oe",
"${BUILDDIR}/../meta-openembedded/meta-python",
@@ -365,7 +367,7 @@
},
"step5" : {
"shortname" : "Repro meta-oe/meta-networking",
-"EXTRACMDS" : ["${SCRIPTSDIR}/checkvnc;
OEQA_DEBUGGING_SAVED_OUTPUT=${BASE_SHAREDDIR}/pub/repro-fail-openembedded/meta-networking/
DISPLAY=:1 oe-selftest -r reproducible"],
+"EXTRACMDS" : ["${SCRIPTSDIR}/checkvnc;
OEQA_DEBUGGING_SAVED_OUTPUT=${BASE_SHAREDDIR}/pub/repro-fail-openembedded/meta-networking/
DISPLAY=:1 oe-selftest --newbuilddir $BBPATH/build-st-meta-networking -r
reproducible"],
"ADDLAYER" : [
"${BUILDDIR}/../meta-openembedded/meta-oe",
"${BUILDDIR}/../meta-openembedded/meta-networking"
@@ -380,7 +382,7 @@
},
"step6" : {
"shortname" : "Repro meta-oe/meta-oe",
-"EXTRACMDS" : ["${SCRIPTSDIR}/checkvnc;
[yocto] FYI: New CVSS 4.0 version to be released end of month.
Not sure who may be aware of these changes coming. See https://www.first.org/cvss/v4-0/ for more info. BR, Armin -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#61334): https://lists.yoctoproject.org/g/yocto/message/61334 Mute This Topic: https://lists.yoctoproject.org/mt/101940920/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] any interest in a YP riscv mailing list?
given that other acrhitectures have their own ML, is it reasonable that risc-v have its own mailing list? rday -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#61333): https://lists.yoctoproject.org/g/yocto/message/61333 Mute This Topic: https://lists.yoctoproject.org/mt/101940855/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] are there any plans for a RISC-V reference board?
On Fri, 2023-10-13 at 03:09 -0400, Robert P. J. Day wrote: > On Tue, 10 Oct 2023, Josef Holzmayr wrote: > > It has been discussed at numerous occasions. The main blocker is: we > > need a commitment for the maintenance. So if a high-ranking member > > decides to push forwards with this and allocate resources, or a new > > member from the RISC-V ecosystem steps up to make it happen, then > > the project is all ears. > > > > Greetz, > > Josef > >Ask and ye shall receive. I just got the following private note > from jiaqi.d...@starfivetech.com, who obviously saw my earlier post > (and agreed to let me reproduce his response to me to the list): > > > I think VisionFive 2 is an appropriate reference board. We offer > > Long Term Support for JH7110 and VisionFive 2. After being upgraded, > > VisionFive 2 with big improvements in the processor work frequency, > > multimedia processing capabilities, and scalability. Since August of > > last year, we have continued to promote the ecosystem of VF2, it has > > successively adapted to Deepin OS, Ubuntu OS, UEFI EDK2, OpenWrt, > > PPSSPP…you can check out the RVspace forum. So we would like to work > > with the developers and provide LTS if there are specific project > > requirements. > > Sound promising? The project has been talking to the RISC-V Foundation for a while about this. The tricky part is that adding official support for a new architecture isn't a cheap or easy undertaking for the project. The autobuilder for example has hardware to pay for as well as bandwidth and power costs. If we add a new architecture, the test matrix is larger and the costs rise. There is also the increased human load of more tests, more failures and more work to do. Intel, AMD and ARM are platinum members and this partly allows for the architecture support. MIPS and PowerPC are on the list for legacy reasons and their testing scope is being scaled back. We've discussed and agreed that adding a new architecture with all the work it entails is at least around a platinum membership level of impact for us. Therefore, to have official support of a new architecture, we've asked that there be support either from existing membership or new members of around that level. When you look at the details of what you get, that price tag is actually quite reasonable for the level of automated testing performed. We've been clear about our position on this for a while. There are actually discussions in progress about it with both the foundation and RISE and I have some reasons to be optimistic but some of this has been going back and forth for a number of years. FWIW, personally I would love to see the support officially there and it in our test matrix. Cheers, Richard -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#61332): https://lists.yoctoproject.org/g/yocto/message/61332 Mute This Topic: https://lists.yoctoproject.org/mt/101869785/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/leave/6691583/21656/737036229/xyzzy [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] [PATCH yocto-autobuilder-helper] Add very basic testimage for poky-tiny
From: Ross Burton
Now that the _qemutiny test case actually works, we can ensure that all
of the tested poky-tiny machines actually at least boot.
This is a very low bar, but it's better than nothing.
Signed-off-by: Ross Burton
---
config.json | 4
1 file changed, 4 insertions(+)
diff --git a/config.json b/config.json
index 3acb710..c82772e 100644
--- a/config.json
+++ b/config.json
@@ -946,6 +946,10 @@
"poky-tiny" : {
"DISTRO" : "poky-tiny",
"BBTARGETS" : "core-image-minimal",
+"SANITYTARGETS" : "core-image-minimal:do_testimage",
+"extravars" : [
+"TEST_SUITES = '_qemutiny'"
+],
"step1" : {
"MACHINE" : "qemux86",
"shortname" : "qemux86 poky-tiny"
--
2.34.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61331): https://lists.yoctoproject.org/g/yocto/message/61331
Mute This Topic: https://lists.yoctoproject.org/mt/101937691/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe:
https://lists.yoctoproject.org/g/yocto/leave/6691583/21656/737036229/xyzzy
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] [GIT-TAG] How do I include the aligned version of a Git tag in the build?
Hi, I need to include the Git tag in my project's recipe build in order to implement automatic versioning. If the tag is set before the prefetch step is performed, I can read the tag after prefetching. Then, when the project is built, the tag is correctly stored in the executable file. However, if I change the tag on the Git repository (server-side), the BitBake recipe is not re-executed, and the new tag version is not included in the build. Is there a method to execute the recipe only when a new tag is set in the remote repository? Many thanks -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#61330): https://lists.yoctoproject.org/g/yocto/message/61330 Mute This Topic: https://lists.yoctoproject.org/mt/101936820/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] are there any plans for a RISC-V reference board?
On Fri, 13 Oct 2023, Alexander Kanavin wrote: > Can you clarify please what LTS means here? > > Alex > > On Fri 13. Oct 2023 at 9.09, Robert P. J. Day wrote: > On Tue, 10 Oct 2023, Josef Holzmayr wrote: > > > Hi Robert, > > > It has been discussed at numerous occasions. The main blocker is: we > > need a commitment for the maintenance. So if a high-ranking member > > decides to push forwards with this and allocate resources, or a new > > member from the RISC-V ecosystem steps up to make it happen, then > > the project is all ears. > > > > Greetz, > > Josef > > Ask and ye shall receive. I just got the following private note > from jiaqi.d...@starfivetech.com, who obviously saw my earlier post > (and agreed to let me reproduce his response to me to the list): > > > I think VisionFive 2 is an appropriate reference board. We offer > > Long Term Support for JH7110 and VisionFive 2. After being upgraded, > > VisionFive 2 with big improvements in the processor work frequency, > > multimedia processing capabilities, and scalability. Since August of > > last year, we have continued to promote the ecosystem of VF2, it has > > successively adapted to Deepin OS, Ubuntu OS, UEFI EDK2, OpenWrt, > > PPSSPP…you can check out the RVspace forum. So we would like to work > > with the developers and provide LTS if there are specific project > > requirements. I don't know, this is just the email I got from someone at StarFive who considered me the right contact person because I asked the question in the first place. rday -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#61329): https://lists.yoctoproject.org/g/yocto/message/61329 Mute This Topic: https://lists.yoctoproject.org/mt/101869785/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] are there any plans for a RISC-V reference board?
Can you clarify please what LTS means here? Alex On Fri 13. Oct 2023 at 9.09, Robert P. J. Day wrote: > On Tue, 10 Oct 2023, Josef Holzmayr wrote: > > > Hi Robert, > > > It has been discussed at numerous occasions. The main blocker is: we > > need a commitment for the maintenance. So if a high-ranking member > > decides to push forwards with this and allocate resources, or a new > > member from the RISC-V ecosystem steps up to make it happen, then > > the project is all ears. > > > > Greetz, > > Josef > >Ask and ye shall receive. I just got the following private note > from jiaqi.d...@starfivetech.com, who obviously saw my earlier post > (and agreed to let me reproduce his response to me to the list): > > > I think VisionFive 2 is an appropriate reference board. We offer > > Long Term Support for JH7110 and VisionFive 2. After being upgraded, > > VisionFive 2 with big improvements in the processor work frequency, > > multimedia processing capabilities, and scalability. Since August of > > last year, we have continued to promote the ecosystem of VF2, it has > > successively adapted to Deepin OS, Ubuntu OS, UEFI EDK2, OpenWrt, > > PPSSPP…you can check out the RVspace forum. So we would like to work > > with the developers and provide LTS if there are specific project > > requirements. > > Sound promising? > > rday > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#61328): https://lists.yoctoproject.org/g/yocto/message/61328 Mute This Topic: https://lists.yoctoproject.org/mt/101869785/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] are there any plans for a RISC-V reference board?
On Tue, 10 Oct 2023, Josef Holzmayr wrote: > Hi Robert, > It has been discussed at numerous occasions. The main blocker is: we > need a commitment for the maintenance. So if a high-ranking member > decides to push forwards with this and allocate resources, or a new > member from the RISC-V ecosystem steps up to make it happen, then > the project is all ears. > > Greetz, > Josef Ask and ye shall receive. I just got the following private note from jiaqi.d...@starfivetech.com, who obviously saw my earlier post (and agreed to let me reproduce his response to me to the list): > I think VisionFive 2 is an appropriate reference board. We offer > Long Term Support for JH7110 and VisionFive 2. After being upgraded, > VisionFive 2 with big improvements in the processor work frequency, > multimedia processing capabilities, and scalability. Since August of > last year, we have continued to promote the ecosystem of VF2, it has > successively adapted to Deepin OS, Ubuntu OS, UEFI EDK2, OpenWrt, > PPSSPP…you can check out the RVspace forum. So we would like to work > with the developers and provide LTS if there are specific project > requirements. Sound promising? rday -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#61327): https://lists.yoctoproject.org/g/yocto/message/61327 Mute This Topic: https://lists.yoctoproject.org/mt/101869785/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-6.1] Rename marvell-cn106xx to marvell-cn10xxx
Hi Bruce, Please help to merge this patch into our linux-yocto repo. repo: yocto-kernel-cache branch: yocto-6.1 Thanks, Ruiqiang -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13182): https://lists.yoctoproject.org/g/linux-yocto/message/13182 Mute This Topic: https://lists.yoctoproject.org/mt/101935165/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] marvell-cn10xxx: rename marvell-cn106xx to new name
From: Ruiqiang Hao
To add support for marvell-cn102xx and marvell-cn103xx, rename origin
name to marvell-cn10xxx.
Signed-off-by: Ruiqiang Hao
---
.../marvell-cn10xxx-preempt-rt.scc} | 4 ++--
.../marvell-cn10xxx-standard.scc} | 4 ++--
.../marvell-cn10xxx.cfg} | 0
.../marvell-cn10xxx.scc} | 2 +-
4 files changed, 5 insertions(+), 5 deletions(-)
rename bsp/{marvell-cn106xx/marvell-cn106xx-preempt-rt.scc =>
marvell-cn10xxx/marvell-cn10xxx-preempt-rt.scc} (54%)
rename bsp/{marvell-cn106xx/marvell-cn106xx-standard.scc =>
marvell-cn10xxx/marvell-cn10xxx-standard.scc} (62%)
rename bsp/{marvell-cn106xx/marvell-cn106xx.cfg =>
marvell-cn10xxx/marvell-cn10xxx.cfg} (100%)
rename bsp/{marvell-cn106xx/marvell-cn106xx.scc =>
marvell-cn10xxx/marvell-cn10xxx.scc} (86%)
diff --git a/bsp/marvell-cn106xx/marvell-cn106xx-preempt-rt.scc
b/bsp/marvell-cn10xxx/marvell-cn10xxx-preempt-rt.scc
similarity index 54%
rename from bsp/marvell-cn106xx/marvell-cn106xx-preempt-rt.scc
rename to bsp/marvell-cn10xxx/marvell-cn10xxx-preempt-rt.scc
index 8733cbad..a0ed4819 100644
--- a/bsp/marvell-cn106xx/marvell-cn106xx-preempt-rt.scc
+++ b/bsp/marvell-cn10xxx/marvell-cn10xxx-preempt-rt.scc
@@ -1,7 +1,7 @@
-define KMACHINE marvell-cn106xx
+define KMACHINE marvell-cn10xxx
define KTYPE preempt-rt
define KARCH arm64
include ktypes/preempt-rt
-include marvell-cn106xx.scc
+include marvell-cn10xxx.scc
diff --git a/bsp/marvell-cn106xx/marvell-cn106xx-standard.scc
b/bsp/marvell-cn10xxx/marvell-cn10xxx-standard.scc
similarity index 62%
rename from bsp/marvell-cn106xx/marvell-cn106xx-standard.scc
rename to bsp/marvell-cn10xxx/marvell-cn10xxx-standard.scc
index 037540b1..03115305 100644
--- a/bsp/marvell-cn106xx/marvell-cn106xx-standard.scc
+++ b/bsp/marvell-cn10xxx/marvell-cn10xxx-standard.scc
@@ -1,8 +1,8 @@
# SPDX-License-Identifier: MIT
-define KMACHINE marvell-cn106xx
+define KMACHINE marvell-cn10xxx
define KTYPE standard
define KARCH arm64
include ktypes/standard
-include marvell-cn106xx.scc
+include marvell-cn10xxx.scc
diff --git a/bsp/marvell-cn106xx/marvell-cn106xx.cfg
b/bsp/marvell-cn10xxx/marvell-cn10xxx.cfg
similarity index 100%
rename from bsp/marvell-cn106xx/marvell-cn106xx.cfg
rename to bsp/marvell-cn10xxx/marvell-cn10xxx.cfg
diff --git a/bsp/marvell-cn106xx/marvell-cn106xx.scc
b/bsp/marvell-cn10xxx/marvell-cn10xxx.scc
similarity index 86%
rename from bsp/marvell-cn106xx/marvell-cn106xx.scc
rename to bsp/marvell-cn10xxx/marvell-cn10xxx.scc
index a809af52..f72630d7 100644
--- a/bsp/marvell-cn106xx/marvell-cn106xx.scc
+++ b/bsp/marvell-cn10xxx/marvell-cn10xxx.scc
@@ -1,5 +1,5 @@
# SPDX-License-Identifier: MIT
-kconf hardware marvell-cn106xx.cfg
+kconf hardware marvell-cn10xxx.cfg
kconf hardware features/edac/edac.cfg
include cfg/usb-mass-storage.scc
--
2.39.2
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13181):
https://lists.yoctoproject.org/g/linux-yocto/message/13181
Mute This Topic: https://lists.yoctoproject.org/mt/101935164/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
