From: Henning Schild <henning.schild@siemens.com>
To: "Moessbauer, Felix (T RDA IOT SES-DE)" <felix.moessbauer@siemens.com>
Cc: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"Kiszka, Jan (T RDA IOT)" <jan.kiszka@siemens.com>,
"Schmidt,
Adriaan (T RDA IOT SES-DE)" <adriaan.schmidt@siemens.com>
Subject: Re: Lightning talk about ISAR
Date: Thu, 9 Dec 2021 23:02:01 +0100 [thread overview]
Message-ID: <20211209230201.6dde4808@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <AM9PR10MB4869D829C16854173F494A8589629@AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM>
Hi all,
the talk went well and i think we can conclude that Isar adoption is
right on track! We have many stakeholders building their firmwares with
Isar and being pretty happy with it!
The talk did focus on performance improvements like sstate and ccache
and did also mention some other changes.
We did have a poll at the end to see where users see room for
improvement. I hope Felix will share the results ... but the number one
topic was "documentation" if i recall correctly.
Short conclusion is ... "Isar is great and works", performance was a
big deal but we are on the right track ... hopefully. But new users and
early adopters rightfully dislike the docs. Surpringly the API
changelog seems fine ... even if we have to break things every once i a
while!
I would take this as a very good indication, but we should not stop
improving. While Isar works well all devs know that its core has many
problems that deserve proper fixes!
regards,
Henning
Am Thu, 25 Nov 2021 11:42:00 +0100
schrieb "Moessbauer, Felix (T RDA IOT SES-DE)"
<felix.moessbauer@siemens.com>:
> Dear subscribers,
>
>
>
> we plan to give a lightning talk about recent changes in ISAR at the
> “Linux Community Event” conference (Siemens internal).
>
> The talk should give an overview about major changes and features,
> added to ISAR since the last year.
>
>
>
> Below you will find a list of topics we plan to present.
>
> Are there any further topics which we should cover?
>
>
>
> - distro support
>
> - added debian bullseye
>
> - added ubuntu (focal)
>
> - target support
>
> - added sample RISC-V target
>
> - image formats
>
> - added OVA (VMWare) image type
>
> - added CPIO image type (initramfs like filesystem)
>
> - generate OCI (container) filesystem
>
> - Performance optimizations
>
> - SState
>
> - CCache (Upcoming)
>
>
>
> Minor changes:
>
> - Install prebuild DPKD packages from third party sources
>
> - Support for apt sources in "Absolute Component Format"
>
> - Package building
>
> - DEBIAN_BUILD_DEPENDS as BB parameter
>
> - DEBIAN_CONFLICTS as BB parameter
>
> - git as default patchtool
>
> - Warn if FS has Y2038 issue
>
> - Changes to ISAR_RELEASE_CMD (upcoming)
>
> Best regards,
> Felix
>
next prev parent reply other threads:[~2021-12-09 22:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-25 10:42 Moessbauer, Felix
2021-11-25 16:26 ` Jan Kiszka
2021-11-25 20:17 ` Henning Schild
2021-11-26 20:20 ` Henning Schild
2021-12-09 22:02 ` Henning Schild [this message]
2021-12-10 10:56 ` Baurzhan Ismagulov
2021-12-10 11:06 ` Moessbauer, Felix
2021-12-10 11:23 ` Jan Kiszka
2021-12-10 11:36 ` Baurzhan Ismagulov
2021-12-13 21:17 ` Henning Schild
2021-12-15 8:49 ` Baurzhan Ismagulov
2021-12-14 13:15 ` Schmidt, Adriaan
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=20211209230201.6dde4808@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=adriaan.schmidt@siemens.com \
--cc=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.com \
--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