public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Henning Schild <henning.schild@siemens.com>
Cc: isar-users@googlegroups.com,
	Quirin Gylstorff <quirin.gylstorff@siemens.com>
Subject: Re: [PATCH] wic: move out all files ending on "direct*"
Date: Thu, 8 Apr 2021 10:49:11 +0200	[thread overview]
Message-ID: <2620070b-5078-7de2-16ca-f026eb6dc373@siemens.com> (raw)
In-Reply-To: <20210408104421.64504371@md1za8fc.ad001.siemens.net>

On 08.04.21 10:44, Henning Schild wrote:
> Am Thu, 8 Apr 2021 10:32:32 +0200
> schrieb Jan Kiszka <jan.kiszka@siemens.com>:
> 
>> On 08.04.21 10:05, [ext] Henning Schild wrote:
>>> wic can compress images, in which case they would have a suffix
>>> plus our new version of wic keeps individual partitions that might
>>> be valuable to some, they also have a suffix we used to not move out
>>>   
>>
>> I vaguely recall some partition extraction classes for SWUpdate
>> scenarios - room for improvements, Quirin? Or are we using that
>> feature already?
> 
> I know, with swupdate we often wanted those single partitions but did
> not have them because wic did not keep them. Now wic seems to keep
> them, which might make later extraction not needed anymore.
> 
> I have compression as a separate task in some layers, when i wanted to
> finally upstream it i found that wic supports it already.
> i.e. bz2 compression is really good to shrink artifacts in CI, and
> https://www.balena.io/etcher/ can uncompress that. Which means Mac and
> Windows users can flash with a mouse what comes out of CI.

That's even greater to hear: I was recently asked for such a flashing
tool internally ("Does Isar have something like
https://www.raspberrypi.org/blog/raspberry-pi-imager-imaging-utility/?")
and also pointed to Etcher as one option. The smoother things work with
it, the better. Maybe worth to add a section to the user manual?

Jan

-- 
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux

  reply	other threads:[~2021-04-08  8:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-08  8:05 Henning Schild
2021-04-08  8:32 ` Jan Kiszka
2021-04-08  8:44   ` Henning Schild
2021-04-08  8:49     ` Jan Kiszka [this message]
2021-04-16 14:21 ` Anton Mikanovich

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=2620070b-5078-7de2-16ca-f026eb6dc373@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=quirin.gylstorff@siemens.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox