From: "Jan Kiszka" <jan.kiszka@siemens.com>
To: cip-dev@lists.cip-project.org,
Quirin Gylstorff <quirin.gylstorff@siemens.com>
Subject: Re: [cip-dev][isar-cip-core][PATCH v2 0/4] Updates & Fixes
Date: Mon, 18 Jan 2021 18:17:23 +0100 [thread overview]
Message-ID: <749081eb-95b1-6d2d-facb-fb23eaa34a8f@siemens.com> (raw)
In-Reply-To: <20210118150625.20155-1-Quirin.Gylstorff@siemens.com>
[-- Attachment #1: Type: text/plain, Size: 1756 bytes --]
On 18.01.21 16:06, Quirin Gylstorff wrote:
> From: Quirin Gylstorff <quirin.gylstorff@siemens.com>
>
>
> - Update Kernel releases
> - Update ISAR to current HEAD of next
>
> - fix swupdate cross-compile
> - use libubootenv for swupdate & u-boot this works only with upstream u-boot-tools
> newer than 2019.10. The isar build is fixed with commit e77d030ed0ac5b122aa7b798131062946cb36699.
>
> Changes V2:
> - fix recipe name, add missing rt
>
> Quirin Gylstorff (4):
> swupdate: enable cross-compile by setting PKG_CONFIG_PATH
> swupdate: use libubootenv
> update linux kernels
> kas: update ISAR
>
> classes/swupdate-config.bbclass | 6 +++---
> kas-cip.yml | 2 +-
> recipes-core/swupdate/files/debian/rules.tmpl | 1 +
> recipes-core/swupdate/swupdate.bb | 2 +-
> ...35-cip31-rt13.bb => linux-cip-rt_4.19.160-cip39-rt17.bb} | 4 ++--
> ...231-cip47-rt30.bb => linux-cip-rt_4.4.244.cip51-rt32.bb} | 4 ++--
> ...ux-cip_4.19.140-cip33.bb => linux-cip_4.19.165-cip41.bb} | 4 ++--
> ...inux-cip_4.4.230-cip47.bb => linux-cip_4.4.249-cip53.bb} | 4 ++--
> 8 files changed, 14 insertions(+), 13 deletions(-)
> rename recipes-kernel/linux/{linux-cip-rt_4.19.135-cip31-rt13.bb => linux-cip-rt_4.19.160-cip39-rt17.bb} (54%)
> rename recipes-kernel/linux/{linux-cip-rt_4.4.231-cip47-rt30.bb => linux-cip-rt_4.4.244.cip51-rt32.bb} (54%)
> rename recipes-kernel/linux/{linux-cip_4.19.140-cip33.bb => linux-cip_4.19.165-cip41.bb} (53%)
> rename recipes-kernel/linux/{linux-cip_4.4.230-cip47.bb => linux-cip_4.4.249-cip53.bb} (53%)
>
Thanks, applied.
Jan
--
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux
[-- Attachment #2: Type: text/plain, Size: 420 bytes --]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#6107): https://lists.cip-project.org/g/cip-dev/message/6107
Mute This Topic: https://lists.cip-project.org/mt/79924716/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]
-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2021-01-18 17:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 15:06 [cip-dev][isar-cip-core][PATCH v2 0/4] Updates & Fixes Quirin Gylstorff
2021-01-18 15:06 ` [cip-dev][isar-cip-core][PATCH v2 1/4] swupdate: enable cross-compile by setting PKG_CONFIG_PATH Quirin Gylstorff
2021-01-18 15:06 ` [cip-dev][isar-cip-core][PATCH v2 2/4] swupdate: use libubootenv Quirin Gylstorff
2021-01-18 15:06 ` [cip-dev][isar-cip-core][PATCH v2 3/4] update linux kernels Quirin Gylstorff
2021-01-18 17:44 ` Jan Kiszka
2021-01-18 22:10 ` Chris Paterson
2021-01-18 15:06 ` [cip-dev][isar-cip-core][PATCH v2 4/4] kas: update ISAR Quirin Gylstorff
2021-01-18 17:17 ` Jan Kiszka [this message]
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=749081eb-95b1-6d2d-facb-fb23eaa34a8f@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=cip-dev@lists.cip-project.org \
--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;
as well as URLs for NNTP newsgroup(s).