mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Denis Osterland-Heim <denis.osterland@diehl.com>
To: "robin@protonic.nl" <robin@protonic.nl>
Cc: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] PTXCONF_RAUC_COMPATIBLE location
Date: Mon, 23 Aug 2021 04:27:00 +0000	[thread overview]
Message-ID: <156e235c1e578d1ad465d1ee74b15da5b8845b73.camel@diehl.com> (raw)
In-Reply-To: <3724efa0030479a35230e2f1dd62264b@protonic.nl>

Hi Robin,

You may simply add the platform name to the compatibility string.

PTXCONF_RAUC_COMPATIBLE="${PTXCONF_PROJECT_VENDOR} ${PTXCONF_PROJECT} ${PTXCONF_PLATFORM}"

Regards Denis

Am Mittwoch, den 18.08.2021, 16:16 +0200 schrieb Robin van der Gracht:
> Hi Bastian,
>
> On 2021-08-18 15:52, Bastian Krause wrote:
> > Hi Robin,
> >
> > On 8/18/21 3:17 PM, Robin van der Gracht wrote:
> > > We're building an OS for multiple platforms. The platforms aren't
> > > compatible.
> >
> > Is the system.conf supposed to be identical on both platforms - apart
> > from the compatible?
>
> If you mean the ptxconfig file (generated by `ptxdist menuconfig`) then yes.
>
> We've refreshed the hardware of an existing product but want the OS to stay
> the same.
>
> Best regards,
> Robin van der Gracht
>
Diehl Connectivity Solutions GmbH
Geschäftsführung: Horst Leonberger
Sitz der Gesellschaft: Nürnberg - Registergericht: Amtsgericht
Nürnberg: HRB 32315

________________________________

Der Inhalt der vorstehenden E-Mail ist nicht rechtlich bindend. Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen.
Informieren Sie uns bitte, wenn Sie diese E-Mail faelschlicherweise erhalten haben. Bitte loeschen Sie in diesem Fall die Nachricht.
Jede unerlaubte Form der Reproduktion, Bekanntgabe, Aenderung, Verteilung und/oder Publikation dieser E-Mail ist strengstens untersagt.

- Informationen zum Datenschutz, insbesondere zu Ihren Rechten, erhalten Sie unter:

https://www.diehl.com/group/de/transparenz-und-informationspflichten/

The contents of the above mentioned e-mail is not legally binding. This e-mail contains confidential and/or legally protected information. Please inform us if you have received this e-mail by
mistake and delete it in such a case. Each unauthorized reproduction, disclosure, alteration, distribution and/or publication of this e-mail is strictly prohibited.

- For general information on data protection and your respective rights please visit:

https://www.diehl.com/group/en/transparency-and-information-obligations/


_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de

  reply	other threads:[~2021-08-23  4:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-18 13:17 Robin van der Gracht
2021-08-18 13:52 ` Bastian Krause
2021-08-18 14:16   ` Robin van der Gracht
2021-08-23  4:27     ` Denis Osterland-Heim [this message]
2021-08-23  6:54       ` Robin van der Gracht
2021-08-23  7:41         ` Denis Osterland-Heim
2021-08-23  9:13           ` Roland Hieber
2021-08-24  6:44             ` Denis Osterland-Heim
2021-08-24  7:39               ` Robin van der Gracht
2021-08-24 13:03               ` rhi
2021-09-03 14:36                 ` Michael Olbrich

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=156e235c1e578d1ad465d1ee74b15da5b8845b73.camel@diehl.com \
    --to=denis.osterland@diehl.com \
    --cc=ptxdist@pengutronix.de \
    --cc=robin@protonic.nl \
    /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