[yocto] OpenEmbedded Workshop at FOSDEM20 CFP
We are proud to announce the inaugural OpenEmbedded Workshop. It is being held on 03 February 2020 in Brussels, Belgium. The day after FOSDEM. The Call for Participation is open now. For more information, go to https://pretalx.com/oe-workshop-2020/cfp Early-bird tickets coming soon! Thank you, The OpenEmbedded Board -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] OpenEmbedded event at FOSDEM20
OpenEmbedded is considering creating a mini-conference attached to FOSDEM 2020 (https://fosdem.org/2020/), and we would like your help. Please fill out this short, 10 question, survey to determine the viability of such an effort. https://www.surveymonkey.com/r/9QP76CL Thank you, The OpenEmbedded Board -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [OE-core] OpenEmbedded Developer Meeting on Day 2 of Yocto Project Summit after ELCE
T-shirts for OEDEM are happening. If you plan on attending, please add yourself to the list. If you already are on the list, please verify the size is correct. Please use this size chart if there are any questions or doubts: https://www.customink.com/items/sizing/04600_lineup/standard.htm I will be ordering in ~24 hours, to allow enough time for them to be made and delivered to me prior to the event. So, please sign-up ASAP! Thanks, Jon FAQ: Q: Can I get one? A: If you are coming, yes. If you are not coming, only if there are extras and you arrange for someone present to transport it to you. Q: Who is paying for it? A: Arm is paying for it and there will be a logo somewhere on the shirt On Mon, Sep 16, 2019 at 12:38 PM Philip Balister wrote: > > Boy that is a mouthful. The date is November 1 2019 in Lyon, France. > > On day 2 of the Yocto Project Summit after the Embedded Linux > Conference, we are hosting an OpenEmbedded Developer meeting. This > meeting is part of an ongoing series of meetings held for OpenEmbedded > developers and users to exchange information about the project's > direction and to explain to developers problems people face in the real > world. > > Please sign up here (attendance is capped at 40): > > https://www.openembedded.org/wiki/OEDEM_2019 > > Please add ideas for topics also. (Also add your T-shirt size after your > name, no promises but the information might help us) > > More info and sign up information for the Yocto Project Summit is here: > > https://wiki.yoctoproject.org/wiki/Yocto_Project_Summit_2019 > > Based on talk abstracts I've seen, Day 1 should be very interesting! > > Philip > > PS: For some historical perspective, here is the page from 2007: > https://www.openembedded.org/wiki/Oedem2007 > -- > ___ > Openembedded-core mailing list > openembedded-c...@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [oe] [OE-core] Git commit process question.
On Wed, Apr 3, 2019 at 7:45 AM Tom Rini wrote: > > On Tue, Apr 02, 2019 at 02:24:51PM -0700, akuster808 wrote: > > > > > > On 4/2/19 12:47 PM, Tom Rini wrote: > > > On Tue, Apr 02, 2019 at 04:45:16AM +, Jon Mason wrote: > > >> On Tue, Apr 2, 2019 at 6:41 AM Mark Hatle > > >> wrote: > > >>> On 4/1/19 6:20 PM, akuster808 wrote: > > >>>> > > >>>> On 4/1/19 4:02 PM, Richard Purdie wrote: > > >>>>> On Mon, 2019-04-01 at 15:33 -0700, akuster808 wrote: > > >>>>>> Hello, > > >>>>>> > > >>>>>> I have noticed a large number of git commits with no header > > >>>>>> information being accepted. > > >>>>> Can you be more specific about what "no header information" means? You > > >>>>> mean a shortlog and no full log message? > > >>>> Commits with just a "subject" and signoff. No additional information > > >>> If you can convey the reason for the change in just the subject, that is > > >>> acceptable.. but there is -always- supposed to be a signed-off-by line > > >>> according > > >>> to our guidelines. > > >>> > > >>> So if you see this, I think we need to step back and figure out where > > >>> and why > > >>> it's happening and get it resolved in the future. > > >>> > > >>> (Places I've seen in the past were one-off mistakes and clearly that -- > > >>> so it > > >>> wasn't anything that we needed to work on a correction.) > > >>> > > >>> --Mark > > >>> > > >>>> We tend to reference back to how the kernel does things. > > >>>> > > >>>> https://www.kernel.org/doc/html/latest/process/submitting-patches.html > > >>>> These two sections in particular. > > >>>> > > >>>> > > >>>> 2) Describe your changes > > >>>> > > >>>> Describe your problem. Whether your patch is a one-line bug fix or > > >>>> 5000 lines of > > >>>> a new feature, there must be an underlying problem that motivated you > > >>>> to do this > > >>>> work. Convince the reviewer that there is a problem worth fixing and > > >>>> that it > > >>>> makes sense for them to read past the first paragraph. > > >>>> > > >>>> > > >>>> along with this section. > > >>>> > > >>>> > > >>>> 14) The canonical patch format > > >>>> > > >>>> This section describes how the patch itself should be formatted. Note > > >>>> that, if > > >>>> you have your patches stored in a |git| repository, proper patch > > >>>> formatting can > > >>>> be had with |git format-patch|. The tools cannot create the necessary > > >>>> text, > > >>>> though, so read the instructions below anyway. > > >>>> > > >>>> The canonical patch subject line is: > > >>>> > > >>>> Subject: [PATCH 001/123] subsystem: summary phrase > > >>>> > > >>>> The canonical patch message body contains the following: > > >>>> > > >>>> * A |from| line specifying the patch author, followed by an > > >>>> empty line > > >>>> (only needed if the person sending the patch is not the > > >>>> author). > > >>>> * The body of the explanation, line wrapped at 75 columns, which > > >>>> will be > > >>>> copied to the permanent changelog to describe this patch. > > >>>> * An empty line. > > >>>> * The |Signed-off-by:| lines, described above, which will also > > >>>> go in the > > >>>> changelog. > > >>>> * A marker line containing simply |---|. > > >>>> * Any additional comments not suitable for the changelog. > > >>>> * The actual patch (|diff| output). > > >>>> > > >>>> > > >>>> - Armin > > >> There are existing git hooks that can be used to detect and fail to > > >> merge patches like this. For Linux, I have the following in > > >> .git/hooks/pre-commit > > >> #!/bin/sh > > >> exec git diff --cached | scripts/checkpatch.pl - > > > FWIW, over in U-Boot land I do: > > > ./scripts/checkpatch.pl -q --git origin/master.. > > > as part of checking things prior to pushing to master. > > Having hooks is fine but after the fact. It puts the burden back on the > > Layer maintainer to resolve. If we think more info is better, it needs > > to happen at time of change submittal. > > Note that I'm not talking about a hook, I'm talking about what's part of > my CI process. And when something pops up there is when I grab the > patch in question and push back on the submitter. Exactly! I do the same things for the Linux stuff I own. I'll do a git-am, then redir the output and publicly shame them. Public shaming is a vastly underrated method of behavior modification. Thanks, Jon > > -- > Tom -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [OE-core] Git commit process question.
On Tue, Apr 2, 2019 at 6:41 AM Mark Hatle wrote: > > On 4/1/19 6:20 PM, akuster808 wrote: > > > > > > On 4/1/19 4:02 PM, Richard Purdie wrote: > >> On Mon, 2019-04-01 at 15:33 -0700, akuster808 wrote: > >>> Hello, > >>> > >>> I have noticed a large number of git commits with no header > >>> information being accepted. > >> Can you be more specific about what "no header information" means? You > >> mean a shortlog and no full log message? > > Commits with just a "subject" and signoff. No additional information > > If you can convey the reason for the change in just the subject, that is > acceptable.. but there is -always- supposed to be a signed-off-by line > according > to our guidelines. > > So if you see this, I think we need to step back and figure out where and why > it's happening and get it resolved in the future. > > (Places I've seen in the past were one-off mistakes and clearly that -- so it > wasn't anything that we needed to work on a correction.) > > --Mark > > > We tend to reference back to how the kernel does things. > > > > https://www.kernel.org/doc/html/latest/process/submitting-patches.html > > These two sections in particular. > > > > > > 2) Describe your changes > > > > Describe your problem. Whether your patch is a one-line bug fix or 5000 > > lines of > > a new feature, there must be an underlying problem that motivated you to do > > this > > work. Convince the reviewer that there is a problem worth fixing and that it > > makes sense for them to read past the first paragraph. > > > > > > along with this section. > > > > > > 14) The canonical patch format > > > > This section describes how the patch itself should be formatted. Note that, > > if > > you have your patches stored in a |git| repository, proper patch formatting > > can > > be had with |git format-patch|. The tools cannot create the necessary text, > > though, so read the instructions below anyway. > > > > The canonical patch subject line is: > > > > Subject: [PATCH 001/123] subsystem: summary phrase > > > > The canonical patch message body contains the following: > > > > * A |from| line specifying the patch author, followed by an empty line > > (only needed if the person sending the patch is not the author). > > * The body of the explanation, line wrapped at 75 columns, which will > > be > > copied to the permanent changelog to describe this patch. > > * An empty line. > > * The |Signed-off-by:| lines, described above, which will also go in > > the > > changelog. > > * A marker line containing simply |---|. > > * Any additional comments not suitable for the changelog. > > * The actual patch (|diff| output). > > > > > > - Armin There are existing git hooks that can be used to detect and fail to merge patches like this. For Linux, I have the following in .git/hooks/pre-commit #!/bin/sh exec git diff --cached | scripts/checkpatch.pl - Perhaps something similar can be added to check for this. Thanks, Jon > > > >> Cheers, > >> > >> Richard > >> > > > > > > -- > ___ > Openembedded-core mailing list > openembedded-c...@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 2/2] machine: clean up config files
Beautify the machine config files by making the names and descriptions
more uniform and verbose
Signed-off-by: Jon Mason
---
meta/conf/machine/qemuarm.conf| 4 ++--
meta/conf/machine/qemuarm64.conf | 4 ++--
meta/conf/machine/qemuarmv5.conf | 6 +++---
meta/conf/machine/qemumips.conf | 4 ++--
meta/conf/machine/qemumips64.conf | 4 ++--
meta/conf/machine/qemuppc.conf| 4 ++--
meta/conf/machine/qemux86-64.conf | 4 ++--
meta/conf/machine/qemux86.conf| 4 ++--
8 files changed, 17 insertions(+), 17 deletions(-)
diff --git a/meta/conf/machine/qemuarm.conf b/meta/conf/machine/qemuarm.conf
index 9555046189..0a2c995312 100644
--- a/meta/conf/machine/qemuarm.conf
+++ b/meta/conf/machine/qemuarm.conf
@@ -1,6 +1,6 @@
#@TYPE: Machine
-#@NAME: generic Arm Cortex-A15 machine
-#@DESCRIPTION: Machine configuration for running a generic armv7
+#@NAME: QEMU Arm Cortex-A15 machine
+#@DESCRIPTION: Machine configuration for running an ARMv7 system on QEMU
require conf/machine/include/tune-cortexa15.inc
require conf/machine/include/qemu.inc
diff --git a/meta/conf/machine/qemuarm64.conf b/meta/conf/machine/qemuarm64.conf
index 22f6cb742b..5c8aac1511 100644
--- a/meta/conf/machine/qemuarm64.conf
+++ b/meta/conf/machine/qemuarm64.conf
@@ -1,6 +1,6 @@
#@TYPE: Machine
-#@NAME: generic armv8 machine
-#@DESCRIPTION: Machine configuration for running a generic armv8
+#@NAME: QEMU ARMv8 machine
+#@DESCRIPTION: Machine configuration for running an ARMv8 system on QEMU
require conf/machine/include/arm/arch-armv8a.inc
require conf/machine/include/qemu.inc
diff --git a/meta/conf/machine/qemuarmv5.conf b/meta/conf/machine/qemuarmv5.conf
index e3948a25da..1c21d3342d 100644
--- a/meta/conf/machine/qemuarmv5.conf
+++ b/meta/conf/machine/qemuarmv5.conf
@@ -1,6 +1,6 @@
#@TYPE: Machine
-#@NAME: arm_versatile_926ejs
-#@DESCRIPTION: arm_versatile_926ejs
+#@NAME: QEMU ARM9 machine
+#@DESCRIPTION: Machine configuration for running an ARMv5 system on QEMU
require conf/machine/include/qemu.inc
require conf/machine/include/tune-arm926ejs.inc
@@ -20,4 +20,4 @@ QB_OPT_APPEND += "-object
rng-random,filename=/dev/urandom,id=rng0 -device virti
PREFERRED_VERSION_linux-yocto ??= "5.0%"
QB_DTB = "${@oe.utils.version_less_or_equal('PREFERRED_VERSION_linux-yocto',
'4.7', '', 'zImage-versatile-pb.dtb', d)}"
-KMACHINE_qemuarmv5 = "qemuarm"
\ No newline at end of file
+KMACHINE_qemuarmv5 = "qemuarm"
diff --git a/meta/conf/machine/qemumips.conf b/meta/conf/machine/qemumips.conf
index a60f67aa87..48d9f41d9d 100644
--- a/meta/conf/machine/qemumips.conf
+++ b/meta/conf/machine/qemumips.conf
@@ -1,6 +1,6 @@
#@TYPE: Machine
-#@NAME: mti_malta32_be MIPS
-#@DESCRIPTION: mti_malta32_be
+#@NAME: QEMU MIPS32 machine
+#@DESCRIPTION: Machine configuration for running a MIPS system on QEMU
require conf/machine/include/qemu.inc
require conf/machine/include/tune-mips32r2.inc
diff --git a/meta/conf/machine/qemumips64.conf
b/meta/conf/machine/qemumips64.conf
index 970c0ce7ae..1872e7b62d 100644
--- a/meta/conf/machine/qemumips64.conf
+++ b/meta/conf/machine/qemumips64.conf
@@ -1,6 +1,6 @@
#@TYPE: Machine
-#@NAME: mti-malta64-be MIPS64
-#@DESCRIPTION: mti-malta64-be
+#@NAME: QEMU MIPS64 machine
+#@DESCRIPTION: Machine configuration for running a MIPS64 system on QEMU
require conf/machine/include/qemu.inc
require conf/machine/include/tune-mips64r2.inc
diff --git a/meta/conf/machine/qemuppc.conf b/meta/conf/machine/qemuppc.conf
index 743d26170e..bd88eeb12a 100644
--- a/meta/conf/machine/qemuppc.conf
+++ b/meta/conf/machine/qemuppc.conf
@@ -1,6 +1,6 @@
#@TYPE: Machine
-#@NAME: qemu PPC Emulator setup
-#@DESCRIPTION: Machine configuration for running an PPC system under qemu
emulation
+#@NAME: QEMU PPC machine
+#@DESCRIPTION: Machine configuration for running a PPC system on QEMU
require conf/machine/include/qemu.inc
require conf/machine/include/tune-ppc7400.inc
diff --git a/meta/conf/machine/qemux86-64.conf
b/meta/conf/machine/qemux86-64.conf
index 9966d1a04c..383e3bd6f3 100644
--- a/meta/conf/machine/qemux86-64.conf
+++ b/meta/conf/machine/qemux86-64.conf
@@ -1,6 +1,6 @@
#@TYPE: Machine
-#@NAME: common_pc
-#@DESCRIPTION: Machine configuration for running a common x86
+#@NAME: QEMU x86-64 machine
+#@DESCRIPTION: Machine configuration for running an x86-64 system on QEMU
PREFERRED_PROVIDER_virtual/xserver ?= "xserver-xorg"
PREFERRED_PROVIDER_virtual/libgl ?= "mesa"
diff --git a/meta/conf/machine/qemux86.conf b/meta/conf/machine/qemux86.conf
index e78fb6e87b..ae5187cbd5 100644
--- a/meta/conf/machine/qemux86.conf
+++ b/meta/conf/machine/qemux86.conf
@@ -1,6 +1,6 @@
#@TYPE: Machine
-#@NAME: common_pc
-#@DESCRIPTION: Machine configuration for running a common x86
+#@NAME: QEMU x86 machine
+#@DESCRIPTION: Machine configuration for running an x86 system on QEMU
PREFERRED_PROVIDER_virtual/xserver ?= "xserver-xorg"
PREFERRED_PROVIDER_virtual/libgl ?= &
[yocto] [PATCH 1/2] meta-yocto-bsp: clean up machine config files
Beautify the machine config files by making the names and descriptions more uniform and verbose Signed-off-by: Jon Mason --- meta-yocto-bsp/conf/machine/edgerouter.conf| 2 +- meta-yocto-bsp/conf/machine/genericx86-64.conf | 5 ++--- meta-yocto-bsp/conf/machine/genericx86.conf| 5 ++--- meta-yocto-bsp/conf/machine/mpc8315e-rdb.conf | 3 ++- 4 files changed, 7 insertions(+), 8 deletions(-) diff --git a/meta-yocto-bsp/conf/machine/edgerouter.conf b/meta-yocto-bsp/conf/machine/edgerouter.conf index 78c87f2f87..88592dbc85 100644 --- a/meta-yocto-bsp/conf/machine/edgerouter.conf +++ b/meta-yocto-bsp/conf/machine/edgerouter.conf @@ -1,6 +1,6 @@ #@TYPE: Machine #@NAME: Edgerouter -#@DESCRIPTION: Edgerouter +#@DESCRIPTION: Machine configuration for a generic edgerouter require conf/machine/include/tune-mips64.inc diff --git a/meta-yocto-bsp/conf/machine/genericx86-64.conf b/meta-yocto-bsp/conf/machine/genericx86-64.conf index 12f7c0d200..c489462dca 100644 --- a/meta-yocto-bsp/conf/machine/genericx86-64.conf +++ b/meta-yocto-bsp/conf/machine/genericx86-64.conf @@ -1,7 +1,6 @@ #@TYPE: Machine -#@NAME: Generic X86_64. - -#@DESCRIPTION: Machine configuration for generic X86_64 (64-bit) PCs and servers. Supports a moderately wide range of drivers that should boot and be usable on "typical" hardware. +#@NAME: Generic x86_64 +#@DESCRIPTION: Machine configuration for generic x86_64 (64-bit) PCs and servers. Supports a moderately wide range of drivers that should boot and be usable on "typical" hardware. DEFAULTTUNE ?= "core2-64" require conf/machine/include/tune-core2.inc diff --git a/meta-yocto-bsp/conf/machine/genericx86.conf b/meta-yocto-bsp/conf/machine/genericx86.conf index 798b62ec2b..9929d2788a 100644 --- a/meta-yocto-bsp/conf/machine/genericx86.conf +++ b/meta-yocto-bsp/conf/machine/genericx86.conf @@ -1,7 +1,6 @@ #@TYPE: Machine -#@NAME: Generic X86. - -#@DESCRIPTION: Machine configuration for generic X86 (32-bit) PCs. Supports a moderately wide range of drivers that should boot and be usable on "typical" hardware. +#@NAME: Generic x86 +#@DESCRIPTION: Machine configuration for generic x86 (32-bit) PCs. Supports a moderately wide range of drivers that should boot and be usable on "typical" hardware. DEFAULTTUNE ?= "core2-32" require conf/machine/include/tune-core2.inc diff --git a/meta-yocto-bsp/conf/machine/mpc8315e-rdb.conf b/meta-yocto-bsp/conf/machine/mpc8315e-rdb.conf index 54a34be3aa..e2dce56738 100644 --- a/meta-yocto-bsp/conf/machine/mpc8315e-rdb.conf +++ b/meta-yocto-bsp/conf/machine/mpc8315e-rdb.conf @@ -1,5 +1,6 @@ #@TYPE: Machine -#@DESCRIPTION: Machine configuration for running +#@NAME: Freescale MPC8315E-RDB +#@DESCRIPTION: Machine configuration for Freescale MPC8315E-RDB TARGET_FPU = "" -- 2.17.2 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 0/2] clean up machine config files
General clean-up of the machine config files present in Yocto. Since this encompasses files that would natively be in the oe-core and meta-yocto-bsp repositories, I split them into 2 commits. However, since they are similar, I sent them in the same email thread. I hope this is acceptable. Jon Mason (2): meta-yocto-bsp: clean up machine config files machine: clean up config files meta-yocto-bsp/conf/machine/edgerouter.conf| 2 +- meta-yocto-bsp/conf/machine/genericx86-64.conf | 5 ++--- meta-yocto-bsp/conf/machine/genericx86.conf| 5 ++--- meta-yocto-bsp/conf/machine/mpc8315e-rdb.conf | 3 ++- meta/conf/machine/qemuarm.conf | 4 ++-- meta/conf/machine/qemuarm64.conf | 4 ++-- meta/conf/machine/qemuarmv5.conf | 6 +++--- meta/conf/machine/qemumips.conf| 4 ++-- meta/conf/machine/qemumips64.conf | 4 ++-- meta/conf/machine/qemuppc.conf | 4 ++-- meta/conf/machine/qemux86-64.conf | 4 ++-- meta/conf/machine/qemux86.conf | 4 ++-- 12 files changed, 24 insertions(+), 25 deletions(-) -- 2.17.2 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [linux-yocto] [kernel-cache][RFC 0/3] qemuarm|qemuarm64: graphics support
On Thu, Feb 28, 2019 at 5:09 PM Bruce Ashfield wrote: > > On Wed, Feb 27, 2019 at 10:58 PM Jon Mason wrote: > > > > This series reverts the reversion of qemuarm match for qemuarma15, and > > adds graphics support for both qemuarm and qemuarm64. > > > > I'm sending this out as an RFC as there are some issues with the > > implementation, and this should probably only be included if the > > forthcoming patches for meta/conf/machine/qemuarm64.conf and > > meta/conf/machine/qemuarm.conf are acceptable. > > The series looks fine to me (at least patch 1 and 3). To allow us > flexibility in the > future, I'll leave qemuarm out of the qemuarma15 machine .scc file .. > and instead > can do a patch that adds: > > KMACHINE_qemuarm ?= "qemuarma15" > > to linux-yocto_* in the master branch. > > That will have the same end result, if you build qemuarm, the tools will go > look > for the qemuarma15 match and will find your new definitions for the > kernel build. > > That way, I can backport future config changes to older release branches and > they won't change how the old qemuarm works. > > When we get to the fall release, I can drop the KMACHINE mapping, and make > the change to the kernel meta data directly. Fantastic! Thanks for doing this. Thanks, Jon > > I'll do up a queue with that in it shortly. > > Cheers, > > Bruce > > > > > Thanks, > > Jon > > > > > > Jon Mason (3): > > qemuarma15: Undo the revert of qemuarm match > > qemuarma15: Add graphics support > > qemuarm64: Add graphics support > > > > bsp/qemuarm64/qemuarm64-gfx.cfg | 7 +++ > > bsp/qemuarm64/qemuarm64.scc | 1 + > > bsp/qemuarma15/qemuarma15-gfx.cfg| 7 +++ > > bsp/qemuarma15/qemuarma15-preempt-rt.scc | 1 + > > bsp/qemuarma15/qemuarma15-standard.scc | 1 + > > bsp/qemuarma15/qemuarma15-tiny.scc | 1 + > > bsp/qemuarma15/qemuarma15.cfg| 3 +++ > > bsp/qemuarma15/qemuarma15.scc| 1 + > > 8 files changed, 22 insertions(+) > > create mode 100644 bsp/qemuarm64/qemuarm64-gfx.cfg > > create mode 100644 bsp/qemuarma15/qemuarma15-gfx.cfg > > > > -- > > 2.17.2 > > > > -- > > ___ > > linux-yocto mailing list > > linux-yocto@yoctoproject.org > > https://lists.yoctoproject.org/listinfo/linux-yocto > > > > -- > - Thou shalt not follow the NULL pointer, for chaos and madness await > thee at its end > - "Use the force Harry" - Gandalf, Star Trek II -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [kernel-cache][RFC 1/3] qemuarma15: Undo the revert of qemuarm match
This reverts commit 7223248023d3d822c8c0227fb65d995ba6b7a351. --- bsp/qemuarma15/qemuarma15-preempt-rt.scc | 1 + bsp/qemuarma15/qemuarma15-standard.scc | 1 + bsp/qemuarma15/qemuarma15-tiny.scc | 1 + 3 files changed, 3 insertions(+) diff --git a/bsp/qemuarma15/qemuarma15-preempt-rt.scc b/bsp/qemuarma15/qemuarma15-preempt-rt.scc index 9bd9464a..57a98eeb 100644 --- a/bsp/qemuarma15/qemuarma15-preempt-rt.scc +++ b/bsp/qemuarma15/qemuarma15-preempt-rt.scc @@ -1,4 +1,5 @@ define KMACHINE qemuarma15 +define KMACHINE qemuarm define KTYPE preempt-rt define KARCH arm diff --git a/bsp/qemuarma15/qemuarma15-standard.scc b/bsp/qemuarma15/qemuarma15-standard.scc index 4ab774f7..e05be1b2 100644 --- a/bsp/qemuarma15/qemuarma15-standard.scc +++ b/bsp/qemuarma15/qemuarma15-standard.scc @@ -1,4 +1,5 @@ define KMACHINE qemuarma15 +define KMACHINE qemuarm define KTYPE standard define KARCH arm diff --git a/bsp/qemuarma15/qemuarma15-tiny.scc b/bsp/qemuarma15/qemuarma15-tiny.scc index 4785c5af..35df306d 100644 --- a/bsp/qemuarma15/qemuarma15-tiny.scc +++ b/bsp/qemuarma15/qemuarma15-tiny.scc @@ -1,4 +1,5 @@ define KMACHINE qemuarma15 +define KMACHINE qemuarm define KTYPE tiny define KARCH arm -- 2.17.2 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [kernel-cache][RFC 3/3] qemuarm64: Add graphics support
Signed-off-by: Jon Mason --- bsp/qemuarm64/qemuarm64-gfx.cfg | 7 +++ bsp/qemuarm64/qemuarm64.scc | 1 + 2 files changed, 8 insertions(+) create mode 100644 bsp/qemuarm64/qemuarm64-gfx.cfg diff --git a/bsp/qemuarm64/qemuarm64-gfx.cfg b/bsp/qemuarm64/qemuarm64-gfx.cfg new file mode 100644 index ..f2ec5432 --- /dev/null +++ b/bsp/qemuarm64/qemuarm64-gfx.cfg @@ -0,0 +1,7 @@ +CONFIG_INPUT_TABLET=y +CONFIG_USB=y +CONFIG_USB_HID=y +CONFIG_USB_XHCI_HCD=y + +CONFIG_DRM=y +CONFIG_DRM_BOCHS=y diff --git a/bsp/qemuarm64/qemuarm64.scc b/bsp/qemuarm64/qemuarm64.scc index 3bbf60cc..8da6591f 100644 --- a/bsp/qemuarm64/qemuarm64.scc +++ b/bsp/qemuarm64/qemuarm64.scc @@ -1 +1,2 @@ kconf hardware qemuarm64.cfg +kconf hardware qemuarm64-gfx.cfg -- 2.17.2 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [kernel-cache][RFC 2/3] qemuarma15: Add graphics support
Signed-off-by: Jon Mason --- bsp/qemuarma15/qemuarma15-gfx.cfg | 7 +++ bsp/qemuarma15/qemuarma15.cfg | 3 +++ bsp/qemuarma15/qemuarma15.scc | 1 + 3 files changed, 11 insertions(+) create mode 100644 bsp/qemuarma15/qemuarma15-gfx.cfg diff --git a/bsp/qemuarma15/qemuarma15-gfx.cfg b/bsp/qemuarma15/qemuarma15-gfx.cfg new file mode 100644 index ..f2ec5432 --- /dev/null +++ b/bsp/qemuarma15/qemuarma15-gfx.cfg @@ -0,0 +1,7 @@ +CONFIG_INPUT_TABLET=y +CONFIG_USB=y +CONFIG_USB_HID=y +CONFIG_USB_XHCI_HCD=y + +CONFIG_DRM=y +CONFIG_DRM_BOCHS=y diff --git a/bsp/qemuarma15/qemuarma15.cfg b/bsp/qemuarma15/qemuarma15.cfg index feda7904..3bc219a5 100644 --- a/bsp/qemuarma15/qemuarma15.cfg +++ b/bsp/qemuarma15/qemuarma15.cfg @@ -27,3 +27,6 @@ CONFIG_CRYPTO_AES_ARM_CE=y CONFIG_CRYPTO_GHASH_ARM_CE=y CONFIG_CRYPTO_CRC32_ARM_CE=y CONFIG_CRYPTO_CHACHA20_NEON=y +CONFIG_ARM_LPAE=y +CONFIG_PCI=y +CONFIG_PCI_HOST_GENERIC=y diff --git a/bsp/qemuarma15/qemuarma15.scc b/bsp/qemuarma15/qemuarma15.scc index a7877aab..f5c8959e 100644 --- a/bsp/qemuarma15/qemuarma15.scc +++ b/bsp/qemuarma15/qemuarma15.scc @@ -1 +1,2 @@ kconf hardware qemuarma15.cfg +kconf hardware qemuarma15-gfx.cfg -- 2.17.2 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [kernel-cache][RFC 0/3] qemuarm|qemuarm64: graphics support
This series reverts the reversion of qemuarm match for qemuarma15, and adds graphics support for both qemuarm and qemuarm64. I'm sending this out as an RFC as there are some issues with the implementation, and this should probably only be included if the forthcoming patches for meta/conf/machine/qemuarm64.conf and meta/conf/machine/qemuarm.conf are acceptable. Thanks, Jon Jon Mason (3): qemuarma15: Undo the revert of qemuarm match qemuarma15: Add graphics support qemuarm64: Add graphics support bsp/qemuarm64/qemuarm64-gfx.cfg | 7 +++ bsp/qemuarm64/qemuarm64.scc | 1 + bsp/qemuarma15/qemuarma15-gfx.cfg| 7 +++ bsp/qemuarma15/qemuarma15-preempt-rt.scc | 1 + bsp/qemuarma15/qemuarma15-standard.scc | 1 + bsp/qemuarma15/qemuarma15-tiny.scc | 1 + bsp/qemuarma15/qemuarma15.cfg| 3 +++ bsp/qemuarma15/qemuarma15.scc| 1 + 8 files changed, 22 insertions(+) create mode 100644 bsp/qemuarm64/qemuarm64-gfx.cfg create mode 100644 bsp/qemuarma15/qemuarma15-gfx.cfg -- 2.17.2 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [kernel-cache][PATCH 2/2] qemuarma15: Add Real-Time and Tiny configs
Add tiny and Real-Time configs. Also, add kmachine name to standard config to allow for BSP renaming. Signed-off-by: Jon Mason --- bsp/qemuarma15/qemuarma15-preempt-rt.scc | 13 + bsp/qemuarma15/qemuarma15-standard.scc | 1 + bsp/qemuarma15/qemuarma15-tiny.scc | 13 + 3 files changed, 27 insertions(+) create mode 100644 bsp/qemuarma15/qemuarma15-preempt-rt.scc create mode 100644 bsp/qemuarma15/qemuarma15-tiny.scc diff --git a/bsp/qemuarma15/qemuarma15-preempt-rt.scc b/bsp/qemuarma15/qemuarma15-preempt-rt.scc new file mode 100644 index ..57a98eeb --- /dev/null +++ b/bsp/qemuarma15/qemuarma15-preempt-rt.scc @@ -0,0 +1,13 @@ +define KMACHINE qemuarma15 +define KMACHINE qemuarm +define KTYPE preempt-rt +define KARCH arm + +# no new branch required, re-use the ktypes/preempt-rt/preempt-rt.scc branch +include ktypes/preempt-rt/preempt-rt.scc + +include cfg/virtio.scc +include cfg/dmaengine.scc +include cfg/timer/rtc.scc +include qemuarma15.scc + diff --git a/bsp/qemuarma15/qemuarma15-standard.scc b/bsp/qemuarma15/qemuarma15-standard.scc index 4ab774f7..e05be1b2 100644 --- a/bsp/qemuarma15/qemuarma15-standard.scc +++ b/bsp/qemuarma15/qemuarma15-standard.scc @@ -1,4 +1,5 @@ define KMACHINE qemuarma15 +define KMACHINE qemuarm define KTYPE standard define KARCH arm diff --git a/bsp/qemuarma15/qemuarma15-tiny.scc b/bsp/qemuarma15/qemuarma15-tiny.scc new file mode 100644 index ..35df306d --- /dev/null +++ b/bsp/qemuarma15/qemuarma15-tiny.scc @@ -0,0 +1,13 @@ +define KMACHINE qemuarma15 +define KMACHINE qemuarm +define KTYPE tiny +define KARCH arm + +include ktypes/tiny/tiny.scc +branch qemuarma15 + +include cfg/virtio.scc +include cfg/dmaengine.scc +include cfg/timer/rtc.scc +include qemuarma15.scc + -- 2.17.2 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [kernel-cache][PATCH 0/2] qemuarm: config changes needed for rename
Last 2 config patches needed for the upcoming rename. The first one allows for the current qemuarm to be renamed qemuarmv5, while keeping the existing name for those who still want to access it that way for legacy reasons. The second one adds defconfigs for tiny and RT, as well as adding the kmachine name to allow for qemuarma15 to be renamed to qemuarm. Jon Mason (2): qemuarm: Add qemuarmv5 kmachine name qemuarma15: Add Real-Time and Tiny configs .../arm-versatile-926ejs-preempt-rt.scc | 1 + .../arm-versatile-926ejs-standard.scc | 1 + .../arm-versatile-926ejs-tiny.scc | 1 + bsp/qemuarma15/qemuarma15-preempt-rt.scc| 13 + bsp/qemuarma15/qemuarma15-standard.scc | 1 + bsp/qemuarma15/qemuarma15-tiny.scc | 13 + 6 files changed, 30 insertions(+) create mode 100644 bsp/qemuarma15/qemuarma15-preempt-rt.scc create mode 100644 bsp/qemuarma15/qemuarma15-tiny.scc -- 2.17.2 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [kernel-cache][PATCH 1/2] qemuarm: Add qemuarmv5 kmachine name
Add alternative kmachine name to allow for the configs to be used by soon-to-be-renamed BSPs. Signed-off-by: Jon Mason --- bsp/arm-versatile-926ejs/arm-versatile-926ejs-preempt-rt.scc | 1 + bsp/arm-versatile-926ejs/arm-versatile-926ejs-standard.scc | 1 + bsp/arm-versatile-926ejs/arm-versatile-926ejs-tiny.scc | 1 + 3 files changed, 3 insertions(+) diff --git a/bsp/arm-versatile-926ejs/arm-versatile-926ejs-preempt-rt.scc b/bsp/arm-versatile-926ejs/arm-versatile-926ejs-preempt-rt.scc index 2ef3bde3..477a16ad 100644 --- a/bsp/arm-versatile-926ejs/arm-versatile-926ejs-preempt-rt.scc +++ b/bsp/arm-versatile-926ejs/arm-versatile-926ejs-preempt-rt.scc @@ -1,4 +1,5 @@ define KMACHINE arm-versatile-926ejs +define KMACHINE qemuarmv5 define KMACHINE qemuarm define KTYPE preempt-rt define KARCH arm diff --git a/bsp/arm-versatile-926ejs/arm-versatile-926ejs-standard.scc b/bsp/arm-versatile-926ejs/arm-versatile-926ejs-standard.scc index 21c3e849..1e8da524 100644 --- a/bsp/arm-versatile-926ejs/arm-versatile-926ejs-standard.scc +++ b/bsp/arm-versatile-926ejs/arm-versatile-926ejs-standard.scc @@ -1,4 +1,5 @@ define KMACHINE arm-versatile-926ejs +define KMACHINE qemuarmv5 define KMACHINE qemuarm define KTYPE standard define KARCH arm diff --git a/bsp/arm-versatile-926ejs/arm-versatile-926ejs-tiny.scc b/bsp/arm-versatile-926ejs/arm-versatile-926ejs-tiny.scc index 5503526a..f5288728 100644 --- a/bsp/arm-versatile-926ejs/arm-versatile-926ejs-tiny.scc +++ b/bsp/arm-versatile-926ejs/arm-versatile-926ejs-tiny.scc @@ -1,4 +1,5 @@ define KMACHINE arm-versatile-926ejs +define KMACHINE qemuarmv5 define KMACHINE qemuarm define KTYPE tiny define KARCH arm -- 2.17.2 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [kernel-cache][PATCH 1/2] qemuarma9: remove unused qemuarma9 configs
On Sun, Jan 6, 2019 at 7:39 PM Bruce Ashfield wrote: > > On Fri, Jan 4, 2019 at 4:39 PM Jon Mason wrote: > > > > Nothing in the Yocto Project is currently using the qemuarma9 configs, > > and this appears to be cruft. Also, there are kernel compile warnings > > when attempting to compile on v4.18 kernels. Instead of fixing it, > > simply remove this to clean up the repo. > > These are actually used by some folks, and I know they are in the > process of fixing them up. > They aren't in the core project, since we could never get full > functionality out of the A9 to replace the old versatile emulations. My apologies, I thought since they compiled with an warnings in Yocto and the output kernel doesn't seem to work with QEMU that they were not being actively used/maintained. If we want to keep them, I can spent a little time to get them working again and maybe push a qemuarma9 machine conf to Yocto. I already had one mostly working, so it would be little effort to fix it up. This way, we can avoid the issue of it compiling with warnings on newer kernels, since we can actually test it. :) Let me know if this is something wanted, and I'll bang it out this week. Thanks, Jon > > I'll have a look at the other patches, but will keep the A9 around. > > Bruce > > > > > Signed-off-by: Jon Mason > > --- > > bsp/qemuarma9/hardware.cfg | 8 --- > > bsp/qemuarma9/qemuarma9-gfx.cfg | 7 --- > > bsp/qemuarma9/qemuarma9-standard.scc | 9 --- > > bsp/qemuarma9/qemuarma9.cfg | 88 > > bsp/qemuarma9/qemuarma9.scc | 2 - > > 5 files changed, 114 deletions(-) > > delete mode 100644 bsp/qemuarma9/hardware.cfg > > delete mode 100644 bsp/qemuarma9/qemuarma9-gfx.cfg > > delete mode 100644 bsp/qemuarma9/qemuarma9-standard.scc > > delete mode 100644 bsp/qemuarma9/qemuarma9.cfg > > delete mode 100644 bsp/qemuarma9/qemuarma9.scc > > > > diff --git a/bsp/qemuarma9/hardware.cfg b/bsp/qemuarma9/hardware.cfg > > deleted file mode 100644 > > index 8b922c66.. > > --- a/bsp/qemuarma9/hardware.cfg > > +++ /dev/null > > @@ -1,8 +0,0 @@ > > -CONFIG_CC_OPTIMIZE_FOR_SIZE > > -CONFIG_CRAMFS > > -CONFIG_HIGH_RES_TIMERS > > -CONFIG_JFFS2_FS > > -CONFIG_NO_HZ > > -CONFIG_SERIAL_8250 > > -CONFIG_SERIAL_AMBA_PL011 > > -CONFIG_SERIAL_AMBA_PL011_CONSOLE > > diff --git a/bsp/qemuarma9/qemuarma9-gfx.cfg > > b/bsp/qemuarma9/qemuarma9-gfx.cfg > > deleted file mode 100644 > > index f0bfcd79.. > > --- a/bsp/qemuarma9/qemuarma9-gfx.cfg > > +++ /dev/null > > @@ -1,7 +0,0 @@ > > -CONFIG_FB=y > > -CONFIG_FB_ARMCLCD=y > > -CONFIG_FRAMEBUFFER_CONSOLE=y > > - > > -CONFIG_INPUT_TABLET=y > > -CONFIG_HID_WACOM=y > > -CONFIG_INPUT_MISC=y > > diff --git a/bsp/qemuarma9/qemuarma9-standard.scc > > b/bsp/qemuarma9/qemuarma9-standard.scc > > deleted file mode 100644 > > index c71fe1c5.. > > --- a/bsp/qemuarma9/qemuarma9-standard.scc > > +++ /dev/null > > @@ -1,9 +0,0 @@ > > -define KMACHINE qemuarma9 > > -define KTYPE standard > > -define KARCH arm > > - > > -include ktypes/standard/standard.scc > > -branch arm-versatile-926ejs > > - > > -include qemuarma9.scc > > - > > diff --git a/bsp/qemuarma9/qemuarma9.cfg b/bsp/qemuarma9/qemuarma9.cfg > > deleted file mode 100644 > > index c8a2aa33.. > > --- a/bsp/qemuarma9/qemuarma9.cfg > > +++ /dev/null > > @@ -1,88 +0,0 @@ > > -CONFIG_ARCH_VEXPRESS=y > > - > > -# > > -# Versatile Express platform type > > -# > > -CONFIG_ARCH_VEXPRESS_CA9X4=y > > -CONFIG_PLAT_VERSATILE=y > > -CONFIG_ARM_TIMER_SP804=y > > - > > -# > > -# Bus support > > -# > > -CONFIG_ARM_AMBA=y > > - > > -# > > -# Kernel Features > > -# > > -CONFIG_SMP=y > > -CONFIG_NR_CPUS=4 > > - > > -# > > -# Floating point emulation > > -# > > -CONFIG_VFP=y > > -CONFIG_VFPv3=y > > -CONFIG_NEON=y > > - > > -CONFIG_SMSC911X=y > > - > > -# > > -# Non-8250 serial port support > > -# > > -CONFIG_SERIAL_AMBA_PL011=y > > -CONFIG_SERIAL_AMBA_PL011_CONSOLE=y > > - > > -CONFIG_MTD=y > > -CONFIG_MTD_CMDLINE_PARTS=y > > - > > -# > > -# User Modules And Translation Layers > > -# > > -CONFIG_MTD_BLKDEVS=y > > -CONFIG_MTD_BLOCK=y > > -# > > -# RAM/ROM/Flash chip drivers > > -# > > -CONFIG_MTD_CFI=y > > -CONFIG_MTD_CFI_INTELEXT=y > > - > >
[linux-yocto] [kernel-cache][PATCH 2/2] qemuarma15: Add QEMU Arm Cortex-A15 virtual machine
Add support for a QEMU Arm Cortex-A15 virtual machine Signed-off-by: Jon Mason --- bsp/qemuarma15/qemuarma15-standard.scc | 12 +++ bsp/qemuarma15/qemuarma15.cfg | 29 ++ bsp/qemuarma15/qemuarma15.scc | 1 + 3 files changed, 42 insertions(+) create mode 100644 bsp/qemuarma15/qemuarma15-standard.scc create mode 100644 bsp/qemuarma15/qemuarma15.cfg create mode 100644 bsp/qemuarma15/qemuarma15.scc diff --git a/bsp/qemuarma15/qemuarma15-standard.scc b/bsp/qemuarma15/qemuarma15-standard.scc new file mode 100644 index ..4ab774f7 --- /dev/null +++ b/bsp/qemuarma15/qemuarma15-standard.scc @@ -0,0 +1,12 @@ +define KMACHINE qemuarma15 +define KTYPE standard +define KARCH arm + +include ktypes/standard/standard.scc +branch qemuarma15 + +include cfg/virtio.scc +include cfg/dmaengine.scc +include cfg/timer/rtc.scc +include qemuarma15.scc + diff --git a/bsp/qemuarma15/qemuarma15.cfg b/bsp/qemuarma15/qemuarma15.cfg new file mode 100644 index ..feda7904 --- /dev/null +++ b/bsp/qemuarma15/qemuarma15.cfg @@ -0,0 +1,29 @@ +CONFIG_ARCH_VIRT=y +CONFIG_SMP=y +CONFIG_NR_CPUS=8 +CONFIG_CPU_IDLE=y +CONFIG_ARM_CPUIDLE=y +CONFIG_VFP=y +CONFIG_VFPv3=y +CONFIG_NEON=y +CONFIG_KERNEL_MODE_NEON=y +CONFIG_SERIAL_AMBA_PL011=y +CONFIG_SERIAL_AMBA_PL011_CONSOLE=y +CONFIG_HW_RANDOM=y +CONFIG_SPI=y +CONFIG_SPI_PL022=y +CONFIG_ARM_SP805_WATCHDOG=y +CONFIG_RTC_DRV_PL031=y +CONFIG_PL330_DMA=y +CONFIG_ARM_TIMER_SP804=y +CONFIG_ARM_CRYPTO=y +CONFIG_CRYPTO_SHA1_ARM_NEON=y +CONFIG_CRYPTO_SHA1_ARM_CE=y +CONFIG_CRYPTO_SHA2_ARM_CE=y +CONFIG_CRYPTO_SHA512_ARM=y +CONFIG_CRYPTO_AES_ARM=y +CONFIG_CRYPTO_AES_ARM_BS=y +CONFIG_CRYPTO_AES_ARM_CE=y +CONFIG_CRYPTO_GHASH_ARM_CE=y +CONFIG_CRYPTO_CRC32_ARM_CE=y +CONFIG_CRYPTO_CHACHA20_NEON=y diff --git a/bsp/qemuarma15/qemuarma15.scc b/bsp/qemuarma15/qemuarma15.scc new file mode 100644 index ..a7877aab --- /dev/null +++ b/bsp/qemuarma15/qemuarma15.scc @@ -0,0 +1 @@ +kconf hardware qemuarma15.cfg -- 2.17.2 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [kernel-cache][PATCH 1/2] qemuarma9: remove unused qemuarma9 configs
Nothing in the Yocto Project is currently using the qemuarma9 configs, and this appears to be cruft. Also, there are kernel compile warnings when attempting to compile on v4.18 kernels. Instead of fixing it, simply remove this to clean up the repo. Signed-off-by: Jon Mason --- bsp/qemuarma9/hardware.cfg | 8 --- bsp/qemuarma9/qemuarma9-gfx.cfg | 7 --- bsp/qemuarma9/qemuarma9-standard.scc | 9 --- bsp/qemuarma9/qemuarma9.cfg | 88 bsp/qemuarma9/qemuarma9.scc | 2 - 5 files changed, 114 deletions(-) delete mode 100644 bsp/qemuarma9/hardware.cfg delete mode 100644 bsp/qemuarma9/qemuarma9-gfx.cfg delete mode 100644 bsp/qemuarma9/qemuarma9-standard.scc delete mode 100644 bsp/qemuarma9/qemuarma9.cfg delete mode 100644 bsp/qemuarma9/qemuarma9.scc diff --git a/bsp/qemuarma9/hardware.cfg b/bsp/qemuarma9/hardware.cfg deleted file mode 100644 index 8b922c66.. --- a/bsp/qemuarma9/hardware.cfg +++ /dev/null @@ -1,8 +0,0 @@ -CONFIG_CC_OPTIMIZE_FOR_SIZE -CONFIG_CRAMFS -CONFIG_HIGH_RES_TIMERS -CONFIG_JFFS2_FS -CONFIG_NO_HZ -CONFIG_SERIAL_8250 -CONFIG_SERIAL_AMBA_PL011 -CONFIG_SERIAL_AMBA_PL011_CONSOLE diff --git a/bsp/qemuarma9/qemuarma9-gfx.cfg b/bsp/qemuarma9/qemuarma9-gfx.cfg deleted file mode 100644 index f0bfcd79.. --- a/bsp/qemuarma9/qemuarma9-gfx.cfg +++ /dev/null @@ -1,7 +0,0 @@ -CONFIG_FB=y -CONFIG_FB_ARMCLCD=y -CONFIG_FRAMEBUFFER_CONSOLE=y - -CONFIG_INPUT_TABLET=y -CONFIG_HID_WACOM=y -CONFIG_INPUT_MISC=y diff --git a/bsp/qemuarma9/qemuarma9-standard.scc b/bsp/qemuarma9/qemuarma9-standard.scc deleted file mode 100644 index c71fe1c5.. --- a/bsp/qemuarma9/qemuarma9-standard.scc +++ /dev/null @@ -1,9 +0,0 @@ -define KMACHINE qemuarma9 -define KTYPE standard -define KARCH arm - -include ktypes/standard/standard.scc -branch arm-versatile-926ejs - -include qemuarma9.scc - diff --git a/bsp/qemuarma9/qemuarma9.cfg b/bsp/qemuarma9/qemuarma9.cfg deleted file mode 100644 index c8a2aa33.. --- a/bsp/qemuarma9/qemuarma9.cfg +++ /dev/null @@ -1,88 +0,0 @@ -CONFIG_ARCH_VEXPRESS=y - -# -# Versatile Express platform type -# -CONFIG_ARCH_VEXPRESS_CA9X4=y -CONFIG_PLAT_VERSATILE=y -CONFIG_ARM_TIMER_SP804=y - -# -# Bus support -# -CONFIG_ARM_AMBA=y - -# -# Kernel Features -# -CONFIG_SMP=y -CONFIG_NR_CPUS=4 - -# -# Floating point emulation -# -CONFIG_VFP=y -CONFIG_VFPv3=y -CONFIG_NEON=y - -CONFIG_SMSC911X=y - -# -# Non-8250 serial port support -# -CONFIG_SERIAL_AMBA_PL011=y -CONFIG_SERIAL_AMBA_PL011_CONSOLE=y - -CONFIG_MTD=y -CONFIG_MTD_CMDLINE_PARTS=y - -# -# User Modules And Translation Layers -# -CONFIG_MTD_BLKDEVS=y -CONFIG_MTD_BLOCK=y -# -# RAM/ROM/Flash chip drivers -# -CONFIG_MTD_CFI=y -CONFIG_MTD_CFI_INTELEXT=y - -CONFIG_RTC_HCTOSYS=y -CONFIG_RTC_HCTOSYS_DEVICE="rtc0" - -# -# on-CPU RTC drivers -# -CONFIG_RTC_CLASS=y -CONFIG_RTC_DRV_PL031=y - -# -# Watchdog Device Drivers -# -CONFIG_ARM_SP805_WATCHDOG=y -CONFIG_WATCHDOG_NOWAYOUT=y - -CONFIG_HAVE_ARM_TWD=y -CONFIG_LOCAL_TIMERS=y - -CONFIG_HIGHMEM=y - -CONFIG_SCSI=y -CONFIG_BLK_DEV_SD=y - -CONFIG_USB=y -CONFIG_USB_STORAGE=y - -CONFIG_HOTPLUG_CPU=y - -CONFIG_I2C=y -CONFIG_I2C_VERSATILE=y - -# This is for the keyboard / mouse -CONFIG_SERIO_AMBAKMI=y - -# SD card interface -CONFIG_MMC=y -CONFIG_MMC_BLOCK=y -CONFIG_MMC_ARMMMCI=y - diff --git a/bsp/qemuarma9/qemuarma9.scc b/bsp/qemuarma9/qemuarma9.scc deleted file mode 100644 index cd135d13.. --- a/bsp/qemuarma9/qemuarma9.scc +++ /dev/null @@ -1,2 +0,0 @@ -kconf hardware qemuarma9.cfg -kconf hardware qemuarma9-gfx.cfg -- 2.17.2 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [kernel-cache][PATCH 0/2] qemuarm: update Cortex-A files
In preparation for migrating qemuarm from the ARMv5 emulated platform to a Cortex-A based one, these patches add a Cortex-A15 platform and remove an unused Cortex-A9 one. Jon Mason (2): qemuarma9: remove unused qemuarma9 configs qemuarma15: Add QEMU Arm Cortex-A15 virtual machine bsp/qemuarma15/qemuarma15-standard.scc | 12 bsp/qemuarma15/qemuarma15.cfg | 29 + bsp/qemuarma15/qemuarma15.scc | 1 + bsp/qemuarma9/hardware.cfg | 8 --- bsp/qemuarma9/qemuarma9-gfx.cfg| 7 -- bsp/qemuarma9/qemuarma9-standard.scc | 9 --- bsp/qemuarma9/qemuarma9.cfg| 88 -- bsp/qemuarma9/qemuarma9.scc| 2 - 8 files changed, 42 insertions(+), 114 deletions(-) create mode 100644 bsp/qemuarma15/qemuarma15-standard.scc create mode 100644 bsp/qemuarma15/qemuarma15.cfg create mode 100644 bsp/qemuarma15/qemuarma15.scc delete mode 100644 bsp/qemuarma9/hardware.cfg delete mode 100644 bsp/qemuarma9/qemuarma9-gfx.cfg delete mode 100644 bsp/qemuarma9/qemuarma9-standard.scc delete mode 100644 bsp/qemuarma9/qemuarma9.cfg delete mode 100644 bsp/qemuarma9/qemuarma9.scc -- 2.17.2 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[yocto] QEMU kernel defconfigs
I'm having difficulty determining where the kernel defconfigs are defined and located. I'm specifically looking for the qemuarm and qemuarm64 kernel defconfigs. I've looked at the relevant documentation, https://www.yoctoproject.org/docs/2.5.1/kernel-dev/kernel-dev.html#using-an-in-tree-defconfig-file and no SRC_URI with defconfig or KBUILD_DEFCONFIG_KMACHINE defined in meta/recipes-kernel/linux/linux-yocto_4.18.bb What am I missing? Also, "A defconfig file is simply a .config renamed to "defconfig"." is not correct. A properly created defconfig is created by `make savedefconfig` and is a minimal file which only has the delta between the desired config and defaults from the Kconfig files. https://www.yoctoproject.org/docs/2.5.1/kernel-dev/kernel-dev.html#creating-a-defconfig-file Thanks, Jon -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [OE-core] OEDAM @ SCaLE 2019
On Thu, Nov 1, 2018 at 10:04 AM Trevor Woerner wrote: > > Hello Fellow YP/OE Enthusiasts! > > There were discussions at our recent OEDEM regarding: > - our next developers meeting > - SCaLE 2019 > - expanding/adding to the YP/OE presence at conferences (i.e. our own > miniconf?) > > Please see time indices: 12:13 and 16:45 > https://docs.google.com/document/d/1YDAHjIOXCIgvSZVOKCYLxa8h26dkruX8zspoge7zCpk > > Unfortunately, although lots of opinions were expressed, nothing concrete was > decided. Many people pointed out that their travel budgets are already > strained or maxed out, so adding another conference would be difficult if not > impossible. It's unclear how many "core" YP/OE people might show up at next > year's SCaLE. Also, given that this year's ELC scheduling hiccup is a one-off, > maybe it doesn't make as much sense to put in all the work required to run an > OEDAM at SCaLE if it's only ever going to happen once. Therefore I think I can > safely say the organizing committee for YP/OE Things at SCaLE 2019 is leaning > towards not running an OEDAM. > > It's not too late to change our plans. If a large number of core people reply > to this email saying they want and OEDAM in March and will be available in > Pasadena, then we could accommodate it. It's just that we didn't leave > Edinburgh with the feeling that an OEDAM at SCaLE was feasible. Also, at this > point SCaLE isn't on the radars of many of the core YP/OE people, and > currently the conference tends to attract users rather than developers (or so > is my impression). > > Thoughts? I am planning on being at SCaLE (assuming the OEDEM happens there). Many corporate travel budgets are tied to presenting at conferences. So, if we could somehow get a track there (which might be too late in the game to do now), then we might be able to get enough people present to make it happen and pull in others whose budget is more flexible. Thanks, Jon > > Best regards, > Trevor > -- > ___ > Openembedded-core mailing list > openembedded-c...@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] NAME missing in mpc8315e-rdb.conf
A quick grep over all of the native config files shows that of all the "#@TYPE: Machine", only one lacks a "#@NAME", mpc8315e-rdb.conf. It appears that the file OE version of the file has a real name and description. See http://git.openembedded.org/openembedded/plain/conf/machine/mpc8315e-rdb.conf Is there a reason to not at least copy this and have it provide some useful information? Thanks, Jon -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
