From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Jonathan Liu <net147@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 5/5] linux-yocto: introduce v3.10
Date: Sat, 24 Aug 2013 09:36:25 -0400 [thread overview]
Message-ID: <5218B6D9.4040805@windriver.com> (raw)
In-Reply-To: <52180512.8020603@gmail.com>
On 13-08-23 8:57 PM, Jonathan Liu wrote:
> On 24/08/2013 4:08 AM, Bruce Ashfield wrote:
>> Introduce the 3.10 kernel. This is based on the 3.10.9 upstream kernel
>> and replaces the 3.8 recipes, which will be removed once all reference
>> boards have been updated.
>>
>> 3.10 also the latest LTSI and will be updated with that content when it
>> becomes available.
>>
>> Other features of the 3.10 kernel include:
>>
>> - refreshed -rt support
>> - refreshed yaffs2, aufs3
>> - cryptodev
>> - bfs, edf, and OCF staged features
>> - scrubbed and updated meta data for v3.10
>> - improved tools support for meta data updates and queue maintenance
>> - patch carry forward from all previous linux-yocto kernels and
>> configuration.
>>
>> This kernel has been built and boot tested on all qemu machines and
>> architectures.
>>
>> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
>> ---
>> meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 30
>> ++++++++++++++++++++
>> meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 25
>> ++++++++++++++++
>> meta/recipes-kernel/linux/linux-yocto_3.10.bb | 30
>> ++++++++++++++++++++
>> 3 files changed, 85 insertions(+)
>> create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
>> create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
>> create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.10.bb
>>
>> diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
>> b/meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
>> new file mode 100644
>> index 0000000..4139be8
>> --- /dev/null
>> +++ b/meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
>> @@ -0,0 +1,30 @@
>> +require recipes-kernel/linux/linux-yocto.inc
>> +
>> +KBRANCH = "standard/preempt-rt/base"
>> +KBRANCH_qemuppc = "standard/preempt-rt/qemuppc"
>> +
>> +SRCREV_machine ?= "77c5842818867366c3d08ca1dec19dc43aee0e91"
>> +SRCREV_machine_qemuppc ?= "7be83bc1124d2a2c75f99df94baaf718659722ea"
>> +SRCREV_meta ?= "1b9b113837f353fd94148beb6bd00a3b7b35d01d"
>> +
>> +SRC_URI =
>> "git://git.yoctoproject.org/linux-yocto-3.10.git;protocol=git;bareclone=1;branch=${KBRANCH},meta;name=machine,meta"
>>
>> +
>> +LINUX_VERSION ?= "3.10.9"
>> +
>> +PV = "${LINUX_VERSION}+git${SRCPV}"
>> +
>> +KMETA = "meta"
>> +
>> +LINUX_KERNEL_TYPE = "preempt-rt"
>> +
>> +# Omit broken machines from COMPATIBLE_MACHINE
>> +# qemuppc hangs at boot
>> +# qemumips panics at boot
>> +COMPATIBLE_MACHINE = "(qemux86|qemux86-64|qemuarm)"
> I see COMPATIBLE_MACHINE has been carried over from the 3.4 and 3.8
> linux-rt recipes. Is linux-rt still broken on qemuppc and qemumips?
It is still the case, for the most part. -rt works fine on both ppc and
mips, just not in qemu.
The first port of any new kernel, I carry support over exactly as it is.
Only changing the kernel + headers, stabilize the existing support and
then look at adding new functionality and boards. That's the only way to
reasonably control the changes.
Cheers,
Bruce
>
>> +
>> +# Functionality flags
>> +KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc
>> features/taskstats/taskstats.scc"
>> +KERNEL_FEATURES_append = " ${KERNEL_EXTRA_FEATURES}"
>> +KERNEL_FEATURES_append_qemux86=" cfg/sound.scc cfg/paravirt_kvm.scc"
>> +KERNEL_FEATURES_append_qemux86-64=" cfg/sound.scc"
>> +KERNEL_FEATURES_append = " ${@bb.utils.contains("TUNE_FEATURES",
>> "mx32", " cfg/x32.scc", "" ,d)}"
>> diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
>> b/meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
>> new file mode 100644
>> index 0000000..1c2ad37
>> --- /dev/null
>> +++ b/meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
>> @@ -0,0 +1,25 @@
>> +require recipes-kernel/linux/linux-yocto.inc
>> +
>> +# We need lzma (as CONFIG_KERNEL_LZMA=y)
>> +DEPENDS += "xz-native"
>> +
>> +KBRANCH_DEFAULT = "standard/tiny/base"
>> +KBRANCH = "${KBRANCH_DEFAULT}"
>> +LINUX_KERNEL_TYPE = "tiny"
>> +KCONFIG_MODE = "--allnoconfig"
>> +
>> +LINUX_VERSION ?= "3.10.9"
>> +
>> +KMETA = "meta"
>> +
>> +SRCREV_machine ?= "6c1528b2b78d1ec7e75bb7a9880074ec35aa1aa0"
>> +SRCREV_meta ?= "1b9b113837f353fd94148beb6bd00a3b7b35d01d"
>> +
>> +PV = "${LINUX_VERSION}+git${SRCPV}"
>> +
>> +SRC_URI =
>> "git://git.yoctoproject.org/linux-yocto-3.10.git;protocol=git;bareclone=1;branch=${KBRANCH},meta;name=machine,meta"
>>
>> +
>> +COMPATIBLE_MACHINE = "(qemux86)"
>> +
>> +# Functionality flags
>> +KERNEL_FEATURES = ""
>> diff --git a/meta/recipes-kernel/linux/linux-yocto_3.10.bb
>> b/meta/recipes-kernel/linux/linux-yocto_3.10.bb
>> new file mode 100644
>> index 0000000..ea6ad2a
>> --- /dev/null
>> +++ b/meta/recipes-kernel/linux/linux-yocto_3.10.bb
>> @@ -0,0 +1,30 @@
>> +require recipes-kernel/linux/linux-yocto.inc
>> +
>> +KBRANCH_DEFAULT = "standard/base"
>> +KBRANCH = "${KBRANCH_DEFAULT}"
>> +
>> +SRCREV_machine_qemuarm ?= "8675d3d0a3c17135f70ef474d5c362397c02e62a"
>> +SRCREV_machine_qemumips ?= "992b743b905edd21d3a4a27c92b5c6a9e44d7d73"
>> +SRCREV_machine_qemuppc ?= "09388c3572e26c78b34554e46e077f12be7b2401"
>> +SRCREV_machine_qemux86 ?= "6c1528b2b78d1ec7e75bb7a9880074ec35aa1aa0"
>> +SRCREV_machine_qemux86-64 ?= "6c1528b2b78d1ec7e75bb7a9880074ec35aa1aa0"
>> +SRCREV_machine_qemumips64 ?= "203679cb23c752fdcbc0180a55a81728d7462561"
>> +SRCREV_machine ?= "6c1528b2b78d1ec7e75bb7a9880074ec35aa1aa0"
>> +SRCREV_meta ?= "1b9b113837f353fd94148beb6bd00a3b7b35d01d"
>> +
>> +SRC_URI =
>> "git://git.yoctoproject.org/linux-yocto-3.10.git;protocol=git;bareclone=1;branch=${KBRANCH},${KMETA};name=machine,meta"
>>
>> +
>> +LINUX_VERSION ?= "3.10.9"
>> +
>> +PV = "${LINUX_VERSION}+git${SRCPV}"
>> +
>> +KMETA = "meta"
>> +
>> +COMPATIBLE_MACHINE =
>> "qemuarm|qemux86|qemuppc|qemumips|qemumips64|qemux86-64"
>> +
>> +# Functionality flags
>> +KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc"
>> +KERNEL_FEATURES_append = " ${KERNEL_EXTRA_FEATURES}"
>> +KERNEL_FEATURES_append_qemux86=" cfg/sound.scc cfg/paravirt_kvm.scc"
>> +KERNEL_FEATURES_append_qemux86-64=" cfg/sound.scc"
>> +KERNEL_FEATURES_append = " ${@bb.utils.contains("TUNE_FEATURES",
>> "mx32", " cfg/x32.scc", "" ,d)}"
> Regards,
> Jonathan
next prev parent reply other threads:[~2013-08-24 13:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-23 18:08 [PATCH 0/5] linux-yocto: consolidated pull request Bruce Ashfield
2013-08-23 18:08 ` [PATCH 1/5] kern-tools: usability, bug fixes and no guilt Bruce Ashfield
2013-08-23 18:08 ` [PATCH 2/5] guilt: update to latest git version Bruce Ashfield
2013-08-23 18:08 ` [PATCH 3/5] linux-libc-headers: update to v3.10 Bruce Ashfield
2013-08-23 18:08 ` [PATCH 4/5] gst-plugins-good: fix 3.10 libc-headers build failure Bruce Ashfield
2013-08-23 18:08 ` [PATCH 5/5] linux-yocto: introduce v3.10 Bruce Ashfield
2013-08-24 0:57 ` Jonathan Liu
2013-08-24 13:36 ` Bruce Ashfield [this message]
2013-08-23 21:30 ` [PATCH 0/5] linux-yocto: consolidated pull request Bruce Ashfield
2013-08-24 6:33 ` Saul Wold
2013-08-24 13:34 ` Bruce Ashfield
2013-08-24 13:45 ` Bruce Ashfield
2013-08-24 13:50 ` Saul Wold
2013-08-24 13:53 ` Bruce Ashfield
2013-08-24 14:47 ` Bruce Ashfield
2013-08-24 14:59 ` Bruce Ashfield
2013-08-24 16:05 ` Bruce Ashfield
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5218B6D9.4040805@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=net147@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.