From: Trevor Woerner <twoerner@gmail.com>
To: Quentin Schulz <quentin.schulz@theobroma-systems.com>
Cc: yocto@lists.yoctoproject.org
Subject: Re: [yocto] [meta-rockchip][PATCH] rock5b: add
Date: Fri, 22 Sep 2023 12:31:04 -0400 [thread overview]
Message-ID: <20230922163104.GA6673@localhost> (raw)
In-Reply-To: <20230922150605.GA40347@localhost>
On Fri 2023-09-22 @ 11:06:05 AM, Trevor Woerner wrote:
> On Fri 2023-09-22 @ 04:22:11 PM, Quentin Schulz wrote:
> > So we should have something like:
> > """
> > aarch64:rk3588s:rk3588:rock5b
> > aarch64:rk3588s:orangepi5
> > """
> > for example.
>
> I spent quite a while checking MACHINEOVERRIDES and SOC_FAMILY with many
> variations until I was able to get exactly what you've just said we should be
> getting.
>
> MACHINE="rock5b"
> $ meta-rockchip> bitbake core-image-base -e | grep "^MACHINEOVERRIDES="
> MACHINEOVERRIDES="rk3588:aarch64:armv8-2a:cortexa76-cortexa55:rk3588:rk3588s:rock5b"
> $ meta-rockchip> bitbake core-image-base -e | grep "^SOC_FAMILY="
> SOC_FAMILY="rk3588"
>
> MACHINE="orangepi5"
> $ meta-rockchip> bitbake core-image-base -e | grep "^MACHINEOVERRIDES="
> MACHINEOVERRIDES="rk3588s:aarch64:armv8-2a:cortexa76-cortexa55:rk3588s:orangepi5"
> $ meta-rockchip> bitbake core-image-base -e | grep "^SOC_FAMILY="
> SOC_FAMILY="rk3588s"
Ah, ordering not just content.
Okay, I'll spin a v2.
prev parent reply other threads:[~2023-09-22 16:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 2:51 [meta-rockchip][PATCH] rock5b: add Trevor Woerner
2023-09-22 14:22 ` [yocto] " Quentin Schulz
2023-09-22 15:06 ` Trevor Woerner
2023-09-22 15:15 ` Quentin Schulz
2023-09-22 16:31 ` Trevor Woerner [this message]
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=20230922163104.GA6673@localhost \
--to=twoerner@gmail.com \
--cc=quentin.schulz@theobroma-systems.com \
--cc=yocto@lists.yoctoproject.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.