public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: "Fatih Alperen Erdogan" <alperen.erdogan@siemens.com>
To: cip-dev@lists.cip-project.org
Subject: Re: [isar-cip-core][PATCH 0/2] swupdate-config-wfx: make device identity configurable
Date: Mon, 20 Apr 2026 07:56:32 -0700	[thread overview]
Message-ID: <962369.1776696992684909700@lists.cip-project.org> (raw)
In-Reply-To: <782e663a-1503-41ca-940e-6f99da8c1a47@siemens.com>

On Mon, Apr 20, 2026 at 02:11 AM, Jan Kiszka wrote:

>
> On 20.04.26 10:00, Alperen Erdogan wrote:
> > Add WFX_DEVICE_ID variable to allow configuring the wfx suricatta
> > device identity at build time. Defaults to $(cat /etc/machine-id).
> > 
> > Alperen Erdogan (2):
> >   swupdate-config-wfx: make device identity configurable
> >   doc: update wfx documentation for configurable device identity
> > 
> >  doc/README.swupdate.md                                        | 4 ++--
> >  .../swupdate-config-wfx/files/suricatta_wfx.conf.tmpl         | 2 +-
> >  ...{swupdate-config-wfx_0.1.bb => swupdate-config-wfx_0.2.bb} | 4 +++-
> >  3 files changed, 6 insertions(+), 4 deletions(-)
> >  rename recipes-core/swupdate-config-wfx/{swupdate-config-wfx_0.1.bb =>
> swupdate-config-wfx_0.2.bb} (86%)
> > 
> > --
> > 2.43.0
> > 
> 
> Looks good to me so far - but would you mind explaining your use case as
> well? Do you replace the extraction logic because your target provides
> an production device ID differently, or do you pin it to fixed known
> value in a development image?
> 
> Jan
> 
> -- 
> Siemens AG, Foundational Technologies
> Linux Expert Center
>

for this use case, target uses a unique device ID provided by the internal system, so it’s read from a different file path.

Thanks, 

Alperen


  reply	other threads:[~2026-04-20 14:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-20  8:00 [isar-cip-core][PATCH 0/2] swupdate-config-wfx: make device identity configurable Alperen Erdogan
2026-04-20  8:00 ` [isar-cip-core][PATCH 1/2] " Alperen Erdogan
2026-04-20  8:00 ` [isar-cip-core][PATCH 2/2] doc: update wfx documentation for configurable device identity Alperen Erdogan
2026-04-20  9:11 ` [isar-cip-core][PATCH 0/2] swupdate-config-wfx: make device identity configurable Jan Kiszka
2026-04-20 14:56   ` Fatih Alperen Erdogan [this message]
2026-04-21 13:33     ` Jan Kiszka

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=962369.1776696992684909700@lists.cip-project.org \
    --to=alperen.erdogan@siemens.com \
    --cc=cip-dev@lists.cip-project.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