cip-dev.lists.cip-project.org archive mirror
 help / color / mirror / Atom feed
From: "Quirin Gylstorff" <quirin.gylstorff@siemens.com>
To: Jan Kiszka <jan.kiszka@siemens.com>, cip-dev@lists.cip-project.org
Subject: Re: [cip-dev][isar-cip-core][PATCH 2/4] swupdate: use libubootenv
Date: Mon, 18 Jan 2021 15:34:20 +0100	[thread overview]
Message-ID: <ce3bd722-2acd-5d42-ec7d-b14e5df0c0c6@siemens.com> (raw)
In-Reply-To: <89feea39-1151-192c-976a-55a4f68ab51c@siemens.com>

[-- Attachment #1: Type: text/plain, Size: 1596 bytes --]



On 1/18/21 3:10 PM, [ext] Quirin Gylstorff wrote:
> 
> 
> On 1/18/21 12:23 PM, Jan Kiszka wrote:
>> On 18.01.21 11:35, Q. Gylstorff wrote:
>>> From: Quirin Gylstorff <quirin.gylstorff@siemens.com>
>>>
>>> libubootenv provides hardware independent access to u-boot environments.
>>> This change conflicts with u-boot tools < 10.2019.
>>>
>>> Signed-off-by: Quirin Gylstorff <quirin.gylstorff@siemens.com>
>>> ---
>>>   classes/swupdate-config.bbclass | 4 ++--
>>>   1 file changed, 2 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/classes/swupdate-config.bbclass 
>>> b/classes/swupdate-config.bbclass
>>> index 208d240..dd0317f 100644
>>> --- a/classes/swupdate-config.bbclass
>>> +++ b/classes/swupdate-config.bbclass
>>> @@ -46,8 +46,8 @@ KFEATURE_ubi[KCONFIG_SNIPPETS] = 
>>> "file://swupdate_defconfig_ubi.snippet"
>>>   KFEATURE_DEPS[ubi] = "mtd"
>>>   KFEATURE_u-boot = ""
>>> -KFEATURE_u-boot[BUILD_DEB_DEPENDS] = "u-boot-${MACHINE}-dev"
>>> -KFEATURE_u-boot[DEBIAN_DEPENDS] = "u-boot-tools"
>>> +KFEATURE_u-boot[BUILD_DEB_DEPENDS] = "libubootenv-dev"
>>> +KFEATURE_u-boot[DEBIAN_DEPENDS] = "libubootenv-tool, u-boot-tools"
>>>   KFEATURE_u-boot[DEPENDS] = "${U_BOOT}"
>>>   KFEATURE_u-boot[KCONFIG_SNIPPETS] = 
>>> "file://swupdate_defconfig_u-boot.snippet"
>>>
>>
>> The isar version we have at this point already supports that?
> 
> Yes, since one next e77d030ed0ac5b122aa7b798131062946cb36699.
Isar supports libubootenv since e77d030ed0ac5b122aa7b798131062946cb36699
cip-core since 683866e2b0c5113b849ef82cf206b3bb5c6e3e30

Quirin

[-- Attachment #2: Type: text/plain, Size: 420 bytes --]


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#6100): https://lists.cip-project.org/g/cip-dev/message/6100
Mute This Topic: https://lists.cip-project.org/mt/79920019/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-


  reply	other threads:[~2021-01-18 14:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-18 10:35 [cip-dev][isar-cip-core][PATCH 0/4] Updates & Fixes Quirin Gylstorff
2021-01-18 10:35 ` [cip-dev][isar-cip-core][PATCH 1/4] swupdate: enable cross-compile by setting PKG_CONFIG_PATH Quirin Gylstorff
2021-01-18 10:35 ` [cip-dev][isar-cip-core][PATCH 2/4] swupdate: use libubootenv Quirin Gylstorff
2021-01-18 11:23   ` Jan Kiszka
2021-01-18 14:10     ` Quirin Gylstorff
2021-01-18 14:34       ` Quirin Gylstorff [this message]
2021-01-18 10:35 ` [cip-dev][isar-cip-core][PATCH 3/4] update linux kernels Quirin Gylstorff
2021-01-18 11:24   ` Jan Kiszka
2021-01-18 10:35 ` [cip-dev][isar-cip-core][PATCH 4/4] kas: update ISAR Quirin Gylstorff

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=ce3bd722-2acd-5d42-ec7d-b14e5df0c0c6@siemens.com \
    --to=quirin.gylstorff@siemens.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=jan.kiszka@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;
as well as URLs for NNTP newsgroup(s).