All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ryan Eatmon <reatmon@ti.com>
To: Moteen Shah <m-shah@ti.com>, <meta-arago@lists.yoctoproject.org>
Cc: <u-kumar1@ti.com>, <s-vadapalli@ti.com>, <a-limaye@ti.com>,
	<gehariprasath@ti.com>, <denys@konsulko.com>
Subject: Re: [PATCH] recipes-core/images: Build ti-core-initramfs alongside tisdk images
Date: Thu, 3 Sep 2026 10:14:29 -0500	[thread overview]
Message-ID: <c12cea0a-a68a-4085-9cf2-6fa0ef967649@ti.com> (raw)
In-Reply-To: <10794eab-552c-440b-b430-5dd644798df8@ti.com>



On 9/3/2026 4:50 AM, Moteen Shah wrote:
> Hey Ryan,
> 
> On 02/09/26 19:35, Ryan Eatmon wrote:
>>
>>
>> On 9/2/2026 8:28 AM, Moteen Shah wrote:
>>> Neither image sets TI_CORE_INITRAMFS_KERNEL_MODULES or
>>> TI_CORE_INITRAMFS_EXTRA_INSTALL for j722s, so the machine-wide
>>> TI_CORE_INITRAMFS_ENABLED gate in meta-ti-bsp stays off by default for
>>> this machine. Force ti-core-initramfs to build via an explicit
>>> do_build dependency in arago-image.inc, the common include every
>>> tisdk-*-image recipe require.
>>
>> Why do we need to force an initramfs on every platform/image? What is 
>> the point?  The point of the initramfs was that *some* boards need 
>> some kernel modules to boot so we only require it for those platforms.
>>
> 
> Is something like this okay?

To be fair, I'm not 100% certain about backporting any of this.  We did 
the initramfs in response to the newer kernels (ie upstream) building 
something as modules and not built in.  And we moved to that model in 
6.18 (master/wrynose).

If there is something in scarthgap for 6.12 that requires this then we 
should just update our 6.12 kernel to build the correct thing and not 
need the initramfs.  We haven't tested any of this code under scarthgap 
and I'm not comfortable just shoving this in.  We need to try and keep 
scarthgap somewhat stable and not do things like this.

We should be able to have a config fragment that only applies for j722s 
when building the kernel to configure it exactly how we want for just 
j722s.  No need to shoehorn in the initramfs for this.


> --- a/meta-arago-distro/recipes-core/images/arago-image.inc
> +++ b/meta-arago-distro/recipes-core/images/arago-image.inc
> @@ -30,3 +30,11 @@ BAD_RECOMMENDATIONS += " \
>   BAD_RECOMMENDATIONS += "${@oe.utils.conditional("INIT_MANAGER", 
> "sysvinit", "", "busybox-syslog", d)}"
> 
>   inherit core-image remove-net-rules
> +
> +ARAGO_TI_CORE_INITRAMFS_STEP ?= ""
> +ARAGO_TI_CORE_INITRAMFS_STEP:j722s = "ti-core-initramfs:do_image_complete"
> +
> +do_build[depends] += "${ARAGO_TI_CORE_INITRAMFS_STEP}"
> 
> 
> With the above change I need to do some meta-ti fix as well.
> 
> Regards,
> Moteen
> 
> 
>>
>>> Signed-off-by: Moteen Shah <m-shah@ti.com>
>>> ---
>>> This patch has a dependency on the following series:
>>> https://lists.yoctoproject.org/g/meta-ti/message/20235
>>>
>>>   meta-arago-distro/recipes-core/images/arago-image.inc | 4 ++++
>>>   1 file changed, 4 insertions(+)
>>>
>>> diff --git a/meta-arago-distro/recipes-core/images/arago-image.inc 
>>> b/meta-arago-distro/recipes-core/images/arago-image.inc
>>> index 37b20850..398e299f 100644
>>> --- a/meta-arago-distro/recipes-core/images/arago-image.inc
>>> +++ b/meta-arago-distro/recipes-core/images/arago-image.inc
>>> @@ -30,3 +30,7 @@ BAD_RECOMMENDATIONS += " \
>>>   BAD_RECOMMENDATIONS += "${@oe.utils.conditional("INIT_MANAGER", 
>>> "sysvinit", "", "busybox-syslog", d)}"
>>>     inherit core-image remove-net-rules
>>> +
>>> +# Force ti-core-initramfs to build alongside every image based on 
>>> this common include.
>>> +
>>> +do_build[depends] += "ti-core-initramfs:do_image_complete"
>>

-- 
Ryan Eatmon                reatmon@ti.com
-----------------------------------------
Texas Instruments, Inc.  -  LCPD  -  MGTS


  reply	other threads:[~2026-09-03 15:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-02 13:28 [PATCH] recipes-core/images: Build ti-core-initramfs alongside tisdk images Moteen Shah
2026-09-02 13:32 ` PRC Automation
2026-09-02 13:41   ` Moteen Shah
2026-09-02 14:05 ` Ryan Eatmon
2026-09-03  9:50   ` Moteen Shah
2026-09-03 15:14     ` Ryan Eatmon [this message]
2026-09-03  8:59 ` [meta-arago] " Yogesh Hegde
2026-09-03  9:45   ` Moteen Shah

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=c12cea0a-a68a-4085-9cf2-6fa0ef967649@ti.com \
    --to=reatmon@ti.com \
    --cc=a-limaye@ti.com \
    --cc=denys@konsulko.com \
    --cc=gehariprasath@ti.com \
    --cc=m-shah@ti.com \
    --cc=meta-arago@lists.yoctoproject.org \
    --cc=s-vadapalli@ti.com \
    --cc=u-kumar1@ti.com \
    /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.