[OE-core] [PATCH 4/4] recipes-kernel/linux: Add RISC-V support

[Bruce Ashfield]

On Thu, Jan 3, 2019 at 7:15 PM Alistair Francis <alistair23 at gmail.com> wrote:
>
> On Thu, Jun 14, 2018 at 3:12 PM Bruce Ashfield <bruce.ashfield at gmail.com> wrote:
> >
> >
> >
> > On Thu, Jun 14, 2018 at 3:45 PM, Alistair Francis <alistair.francis at wdc.com> wrote:
> >>
> >> Signed-off-by: Alistair Francis <alistair.francis at wdc.com>
> >> ---
> >>  meta/recipes-kernel/linux/linux-yocto.inc     | 4 ++++
> >>  meta/recipes-kernel/linux/linux-yocto_4.15.bb | 5 ++++-
> >>  2 files changed, 8 insertions(+), 1 deletion(-)
> >>
> >> diff --git a/meta/recipes-kernel/linux/linux-yocto.inc b/meta/recipes-kernel/linux/linux-yocto.inc
> >> index 95ec2a2b41..70a13cdd1e 100644
> >> --- a/meta/recipes-kernel/linux/linux-yocto.inc
> >> +++ b/meta/recipes-kernel/linux/linux-yocto.inc
> >> @@ -26,6 +26,10 @@ DEPENDS_append_nios2 = " libgcc"
> >>  KERNEL_CC_append_nios2 = " ${TOOLCHAIN_OPTIONS}"
> >>  KERNEL_LD_append_nios2 = " ${TOOLCHAIN_OPTIONS}"
> >>
> >> +DEPENDS_append_riscv64 = " libgcc"
> >> +KERNEL_CC_append_riscv64 = " ${TOOLCHAIN_OPTIONS} ${SECURITY_NOPIE_CFLAGS}"
> >> +KERNEL_LD_append_riscv64 = " -no-pie"
> >> +
> >>  KERNEL_FEATURES_append_qemuall=" features/debug/printk.scc"
> >>
> >>  # A KMACHINE is the mapping of a yocto $MACHINE to what is built
> >> diff --git a/meta/recipes-kernel/linux/linux-yocto_4.15.bb b/meta/recipes-kernel/linux/linux-yocto_4.15.bb
> >> index 693670c613..4ea368a011 100644
> >> --- a/meta/recipes-kernel/linux/linux-yocto_4.15.bb
> >> +++ b/meta/recipes-kernel/linux/linux-yocto_4.15.bb
> >> @@ -36,7 +36,10 @@ KCONF_BSP_AUDIT_LEVEL = "2"
> >>
> >>  KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb"
> >>
> >> -COMPATIBLE_MACHINE = "qemuarm|qemuarm64|qemux86|qemuppc|qemumips|qemumips64|qemux86-64"
> >> +KBUILD_DEFCONFIG_qemuriscv64 = "defconfig"
> >> +KCONFIG_MODE_qemuriscv64 = "--alldefconfig"
> >
> >
> > This doesn't belong in linux-yocto.
> >
> > We use defined BSP and configuration fraagments, not in-tree defconfigs
> >
> > I'm happy to add a BSP definition to the kernel-cache, but this isn't the way to add configuration support for the linux-yocto trees
>
> Hey Bruce,
>
> I'm looking at this again as the 4.19 kernel now has full working
> RISC-V support.
>
> How can I add a BSP definition to the kernel-cache?
>

See the examples that are already in the kernel-cache, follow one of
them and send a patch to the linux-yocto mailing list.

What ends up in the BSP definition are only the options related to h/w
on the board. General / software options are defined by the
common/included fragments in the configuration repo.

> Also, what is the reason for not using the in-tree defconfigs?

Because we maintain our own reference configurations, and they are
largely consistent across machines and architectures. That is not the
case for in tree defconfigs. People are free to use them for their own
purposes, but that's not what we do for the reference BSPs.

Cheers,

Bruce

>
> Alistair
>
> >
> > Cheers,
> >
> > Bruce
> >
> >>
> >> +
> >> +COMPATIBLE_MACHINE = "qemuarm|qemuarm64|qemux86|qemuppc|qemumips|qemumips64|qemux86-64|qemurisc532|qemuriscv64"
> >>
> >>  # Functionality flags
> >>  KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc"
> >> --
> >> 2.17.1
> >>
> >> --
> >> _______________________________________________
> >> Openembedded-core mailing list
> >> Openembedded-core at lists.openembedded.org
> >> http://lists.openembedded.org/mailman/listinfo/openembedded-core
> >
> >
> >
> >
> > --
> > "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"
> > --
> > _______________________________________________
> > Openembedded-core mailing list
> > Openembedded-core at lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-core



-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II