All of lore.kernel.org
 help / color / mirror / Atom feed
From: Quentin Schulz <quentin.schulz@cherry.de>
To: yocto-patches@lists.yoctoproject.org
Subject: Re: [yocto-patches] [meta-rockchip][PATCH v4] fitimage rework
Date: Fri, 27 Jun 2025 12:34:48 +0200	[thread overview]
Message-ID: <dbb256bb-e95d-4858-ad52-7bdb9820814b@cherry.de> (raw)
In-Reply-To: <20250626031810.35828-1-twoerner@gmail.com>

Hi Trevor,

On 6/26/25 5:18 AM, Trevor Woerner via lists.yoctoproject.org wrote:

[...]

> diff --git a/conf/machine/include/rockchip-defaults.inc b/conf/machine/include/rockchip-defaults.inc
> index 85ec7b944d1d..fc8930635fbe 100644
> --- a/conf/machine/include/rockchip-defaults.inc
> +++ b/conf/machine/include/rockchip-defaults.inc
> @@ -1,9 +1,16 @@
>   # meta-rockchip default settings
>   MACHINEOVERRIDES =. "${@bb.utils.contains('ROCKCHIP_CLOSED_TPL', '1', 'closed-tpl:', '', d)}"
>   MACHINEOVERRIDES =. "rockchip:"
> +
>   # kernel
> +# RK_KERNEL_FITIMAGE needs to be set before the next "require ..."
> +RK_KERNEL_FITIMAGE ?= "True"
>   PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto"
>   KCONFIG_MODE ?= "alldefconfig"
> +KERNEL_IMAGETYPE ??= "zImage"

Any reason for having ??= instead of ?= here? I would assume that ?= 
would be enough? Can leave as is though.

> +MACHINE_ESSENTIAL_EXTRA_RDEPENDS_KERNEL += "kernel-devicetree"

Any reason for the += here? I believe = should be fine? Can leave as is 
though.

Looks ok to me otherwise!

FYI, I'm on PTO for the next two weeks and won't have the time to test 
this today, do what you will with this info :)

Cheers,
Quentin


  reply	other threads:[~2025-06-27 10:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-26  3:18 [meta-rockchip][PATCH v4] fitimage rework Trevor Woerner
2025-06-27 10:34 ` Quentin Schulz [this message]
2025-06-27 14:57 ` 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=dbb256bb-e95d-4858-ad52-7bdb9820814b@cherry.de \
    --to=quentin.schulz@cherry.de \
    --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.