From: Trevor Woerner <twoerner@gmail.com>
To: yocto@lists.yoctoproject.org
Subject: [meta-rockchip][PATCH v2 0/1] rock-pi-s: add
Date: Tue, 31 Oct 2023 08:58:04 -0400 [thread overview]
Message-ID: <20231031125805.37314-1-twoerner@gmail.com> (raw)
Add a new MACHINE: rock-pi-s
changes since v1:
- while the actual patch to add the rock-pi-s was not merged, all of the
cleanup patches that were submitted in advance of the "add" patch (and
were part of the original series) were applied, therefore those patches
are dropped from this version
- upstream master now contains a version of u-boot that supports the
rock-pi-s, therefore using rk3308-specific overrides in the u-boot
bbappend is no longer necessary
- add a separate rk3308-rkbin recipe instead of loading the rockchip-rkbin
recipe with rk3308-specific overrides
- allow the user to choose whether they want the rkbin and u-boot debug
messages to show up on the console (i.e. use an older version of rkbin)
or have gibberish until the linux kernel starts (use the latest version
of rkbin) by setting (or not) a variable; default is to use an older
version
Trevor Woerner (1):
rock-pi-s: add
README | 22 +++++++++++
conf/machine/include/rk3308.inc | 18 +++++++++
conf/machine/rock-pi-s.conf | 11 ++++++
recipes-bsp/rkbin/rk3308-rkbin_git.bb | 41 +++++++++++++++++++++
recipes-bsp/rkbin/rockchip-rkbin_git.bb | 10 +++++
recipes-bsp/u-boot/u-boot%.bbappend | 8 ++++
recipes-kernel/linux/linux-yocto_%.bbappend | 1 +
7 files changed, 111 insertions(+)
create mode 100644 conf/machine/include/rk3308.inc
create mode 100644 conf/machine/rock-pi-s.conf
create mode 100644 recipes-bsp/rkbin/rk3308-rkbin_git.bb
--
2.41.0.327.gaa9166bcc0ba
next reply other threads:[~2023-10-31 12:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 12:58 Trevor Woerner [this message]
2023-10-31 12:58 ` [meta-rockchip][PATCH v2 1/1] rock-pi-s: add Trevor Woerner
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=20231031125805.37314-1-twoerner@gmail.com \
--to=twoerner@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox