Yocto Project Discussions
 help / color / mirror / Atom feed
From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: "Böckelmann, Thore" <thore.boeckelmann@inoex.de>
Cc: "yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Subject: Re: AW: [EXT] Re: [yocto] ext4 issues with scarthgap .wic image
Date: Wed, 20 Nov 2024 14:50:19 +0200	[thread overview]
Message-ID: <Zz3bC-M33vN1HVXj@nuoska> (raw)
In-Reply-To: <FR3PPF317299CA97E0A8E987CB5588C3C358F212@FR3PPF317299CA9.DEUP281.PROD.OUTLOOK.COM>

Hi,

On Wed, Nov 20, 2024 at 12:42:51PM +0000, B�ckelmann, Thore wrote:
> Hi Mikko!
> 
> Of course it is always better to move forward instead of backwards. But my point is that the documented EXTRA_IMAGECMD variable is somehow ignored and not passed to mkfs.ext4 as it should be. If it isn't to disable a feature the same issue will arise when I try to pass any other option to mkfs.ext4. This is what the IMAGE_CMD and EXTRA_IMAGECMD variables were invented for.

This could be a bug, or change in image_types.bbclass behaviour.
Would be nice if you could debug this a bit further, for example
"bitbake -e image" output.

At least IMAGE_CMD:ext4 in current poky master image_types.bbclass
still has

IMAGE_CMD:ext4 = "oe_mkext234fs ext4 ${EXTRA_IMAGECMD}"

which would imply that adding command line arguments with
EXTRA_IMAGECMD should work.

Cheers,

-Mikko


  reply	other threads:[~2024-11-20 12:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ed7dbfe9-1861-4e5b-9954-03bf8404920a.970c85df-582b-4473-a7de-31be6a2b58c9.8a47a721-58ad-47e5-be44-609511a60ac9@emailsignatures365.codetwo.com>
     [not found] ` <ed7dbfe9-1861-4e5b-9954-03bf8404920a.5f629621-7c71-47da-aee6-727c8a7b4e6a.21f4d927-51fb-4187-a3f2-1b08161ff7e2@emailsignatures365.codetwo.com>
2024-11-20 11:37   ` ext4 issues with scarthgap .wic image Böckelmann, Thore
2024-11-20 12:04     ` [yocto] " Mikko Rapeli
2024-11-20 12:42       ` AW: [EXT] " Böckelmann, Thore
2024-11-20 12:50         ` Mikko Rapeli [this message]
2024-11-21  9:18           ` AW: [EXT] " Böckelmann, Thore
2024-11-21  9:24             ` Mikko Rapeli
2024-11-21 14:02               ` Jan-Simon Moeller

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=Zz3bC-M33vN1HVXj@nuoska \
    --to=mikko.rapeli@linaro.org \
    --cc=thore.boeckelmann@inoex.de \
    --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