From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
To: Trevor Woerner <twoerner@gmail.com>
Cc: michael.opdenacker@rootcommit.com, yocto-patches@lists.yoctoproject.org
Subject: Re: [yocto-patches] [meta-rockchip] [PATCH] tinker-board-3: add
Date: Fri, 19 Dec 2025 06:34:15 +0000 (UTC) [thread overview]
Message-ID: <2faed21a-9745-4f67-a2de-efe1f56c4141@rootcommit.com> (raw)
In-Reply-To: <20251219025010.GB5613@localhost>
Hi Trevor
On 12/19/25 03:50, Trevor Woerner wrote:
> On Thu 2025-12-18 @ 06:10:07 AM, Michael Opdenacker via lists.yoctoproject.org wrote:
>> Greetings,
>>
>> On 12/18/25 07:03, Michael Opdenacker via lists.yoctoproject.org wrote:
>>> From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
>>>
>>> Add basic support for the Asus Tinker Board 3 [1] and 3S [2] SBCs,
>>> with the Rockchip rk3566 SoC.
>>>
>>> Support for such boards was introduced in the 6.19-rc1 version
>>> of the Linux kernel:
>>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9f80b3952318d7ef18573a5010f06118602f992e
>>>
>>> Therefore, the https://github.com/betafive/meta-linux-mainline/
>>> layer is currently a prerequisite to build images for such machines.
>> Is it fine to require an additional dependency to the "meta-linux-mainline"
>> layer here, as Linux 6.19-rc1 isn't supported by linux-yocto-dev?
>>
>> I could add a machine dependent string to LAYERDEPENDS_rockchip, but I don't
>> want to pollute conf/layer.conf.
>>
>> And it seems BBFILES_DYNAMIC is for recipes only, not configuration files.
>> Thanks in advance
>> Michael.
> As much as I like Paul's meta-linux-mainline (and use it myself from
> time to time) I would prefer of meta-rockchip didn't have a dependency
> on it.
No problem at all. I fully understand you want to keep meta-rockchip
clean, and it looks very clean compared to other layers).
This being said, having a board in a community layer like ours is a way
to share code and foster collaboration, all the more as OE/Yocto can
help people focus on userspace aspects while keeping the early boot
details transparent. It's a bit frustrating to have to wait for 2 more
months, but its not blocking either.
Thanks for your review!
Cheers
Michael.
--
Michael Opdenacker
Root Commit
Yocto Project and OpenEmbedded Training course - Learn by doing:
https://rootcommit.com/training/yocto/
next prev parent reply other threads:[~2025-12-19 6:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <18823A0A6BE7E236.1506149@lists.yoctoproject.org>
2025-12-18 6:10 ` [yocto-patches] [meta-rockchip] [PATCH] tinker-board-3: add Michael Opdenacker
2025-12-19 2:50 ` Trevor Woerner
2025-12-19 6:34 ` Michael Opdenacker [this message]
2025-12-18 6:03 michael.opdenacker
2025-12-18 10:46 ` [yocto-patches] " Quentin Schulz
2025-12-19 2:47 ` Trevor Woerner
2025-12-19 15:17 ` Michael Opdenacker
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=2faed21a-9745-4f67-a2de-efe1f56c4141@rootcommit.com \
--to=michael.opdenacker@rootcommit.com \
--cc=twoerner@gmail.com \
--cc=yocto-patches@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.