From: "Su, Bao Cheng" <baocheng.su@siemens.com>
To: "Schultschik, Sven" <sven.schultschik@siemens.com>,
"cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>
Cc: "Kiszka, Jan" <jan.kiszka@siemens.com>
Subject: Re: AW: [isar-cip-core][PATCH 1/8] add recipe for edk2
Date: Thu, 27 Oct 2022 01:39:42 +0000 [thread overview]
Message-ID: <2b44a657cd32ba83a1427ed32090ac71da3fad5e.camel@siemens.com> (raw)
In-Reply-To: <PAXPR10MB50374CAB4D5D604A25B7003190309@PAXPR10MB5037.EURPRD10.PROD.OUTLOOK.COM>
On Wed, 2022-10-26 at 14:44 +0000, Schultschik, Sven (DI PA DCP R&D 2)
wrote:
>
> > -----Ursprüngliche Nachricht-----
> > Von: Su, Bao Cheng (DI FA CTR IPC CN PRC4) <baocheng.su@siemens.com>
> > Gesendet: Dienstag, 25. Oktober 2022 10:23
> > An: Schultschik, Sven (DI PA DCP R&D 2) <sven.schultschik@siemens.com>;
> cip-
> > dev@lists.cip-project.org
> > Cc: Kiszka, Jan (T CED) <jan.kiszka@siemens.com>
> > Betreff: Re: [isar-cip-core][PATCH 1/8] add recipe for edk2
> >
> > On Mon, 2022-10-24 at 14:27 +0200, sven.schultschik@siemens.com wrote:
> > > From: Sven Schultschik <sven.schultschik@siemens.com>
> > >
> > > +SRC_URI =
> >
> "gitsm://github.com/tianocore/edk2.git;branch=master;protocol=https;destsuff
> > ix=git/edk2;name=edk2 \
> > > + git://github.com/tianocore/edk2-
> > platforms.git;protocol=https;destsuffix=git/edk2-platforms;name=edk2-
> > platforms \
> > > + file://rules.tmpl \
> > > + "
> > > +SRCREV_edk2 = "edk2-stable${PV}"
> > > +SRCREV_edk2-platforms = "3b896d1a325686de3942723c42f286090453e37a"
> > > +
> >
> > git clone shows almost 3GiB need be cloned:
> >
> > Receiving objects: 100% (449873/449873), 345.43 MiB | 645.00 KiB/s
> Receiving
> > objects: 100% (621839/621839), 387.81 MiB | 2.70 MiB/s Receiving objects:
> > 100% (294131/294131), 379.77 MiB | 2.84 MiB/s Receiving objects: 100%
> > (193740/193740), 1.40 GiB | 2.61 MiB/s Receiving objects: 100%
> > (257204/257204), 75.65 MiB | 2.82 MiB/s Receiving objects: 100%
> (2931/2931),
> > 827.33 KiB | 661.00 KiB/s Receiving objects: 100% (3254/3254), 945.31 KiB
> >
> > 974.00 KiB/s Receiving objects: 100% (14888/14888), 6.26 MiB | 2.19 MiB/s
> > Receiving objects: 100% (9737/9737), 47.26 MiB | 2.69 MiB/s Receiving
> objects:
> > 100% (8383/8383), 2.24 MiB | 1.57 MiB/s, Receiving objects: 100%
> > (300301/300301), 271.63 MiB | 1.72 MiB/s
> >
> > This is too huge, use tarballs instead?
> >
> I checked and in my opinion it is not an option.
> EDK2 has a released tar.gz, but it is missing the submodules.
> The first submodule I tried to add as tar file as well was google/brotli
> https://github.com/google/brotli/tree/f4153a09f87cbb9c826d8fc12c74642bb2d879
> ea
> The last release they had was in Aug 27 2020 and the commit used in edk2
> Is from Januar 10, 2022.
> So google/brotli would be added as git again, trying to get all at the right
> spot.
> I don't think that you would safe speed and space and you would add
> Complexity.
I think you can use below link to get a commit:
https://github.com/google/brotli/archive/f4153a09f87cbb9c826d8fc12c74642bb2d879.tar.gz
which results in:
-rw-r--r-- 1 *** *** 501K Oct 27 09:32
f4153a09f87cbb9c826d8fc12c74642bb2d879.tar.gz
And the git clone size is 49MB for this repo.
- Baocheng Su
next prev parent reply other threads:[~2022-10-27 1:39 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 12:27 [isar-cip-core][PATCH 0/8] Secureboot on QEMU with EDK2, OP-TEE and RPBM sven.schultschik
2022-10-24 12:27 ` [isar-cip-core][PATCH 1/8] add recipe for edk2 sven.schultschik
2022-10-25 8:23 ` Su, Bao Cheng
2022-10-26 14:44 ` AW: " Schultschik, Sven
2022-10-27 1:39 ` Su, Bao Cheng [this message]
2022-10-27 16:14 ` AW: " Schultschik, Sven
2022-10-27 17:08 ` Jan Kiszka
2022-10-25 8:40 ` Su, Bao Cheng
2022-10-24 12:27 ` [isar-cip-core][PATCH 2/8] add recipe for optee qemu arm64 sven.schultschik
2022-10-24 12:27 ` [isar-cip-core][PATCH 3/8] Include optee into u-boot sven.schultschik
2022-10-26 7:36 ` Su, Bao Cheng
2022-10-26 8:52 ` Jan Kiszka
2022-10-26 15:27 ` AW: " Schultschik, Sven
2022-10-26 16:00 ` Jan Kiszka
2022-11-07 16:57 ` AW: " Schultschik, Sven
2022-11-07 17:50 ` Jan Kiszka
2022-11-10 11:01 ` AW: " Schultschik, Sven
2022-11-10 13:38 ` Jan Kiszka
2022-10-24 12:27 ` [isar-cip-core][PATCH 4/8] add u-boot patch for qemu to support RPMB sven.schultschik
2022-10-24 12:27 ` [isar-cip-core][PATCH 5/8] add recipe for trusted firmware a qemu arm64 sven.schultschik
2022-10-28 5:50 ` Jan Kiszka
2022-10-28 15:46 ` AW: " Schultschik, Sven
2022-10-28 19:10 ` Jan Kiszka
2022-10-24 12:27 ` [isar-cip-core][PATCH 6/8] add kas files for building qemu secure boot images sven.schultschik
2022-10-27 17:17 ` Jan Kiszka
2022-11-07 10:43 ` AW: " Schultschik, Sven
2022-11-07 12:59 ` Jan Kiszka
2022-10-24 12:27 ` [isar-cip-core][PATCH 7/8] enhance start-qemu.sh for arm64 secure boot sven.schultschik
2022-10-24 12:27 ` [isar-cip-core][PATCH 8/8] no merge - manually instructions test " sven.schultschik
2022-10-25 8:36 ` Su, Bao Cheng
2022-10-25 15:23 ` AW: " Schultschik, Sven
2022-10-25 8:09 ` [isar-cip-core][PATCH 0/8] Secureboot on QEMU with EDK2, OP-TEE and RPBM Su, Bao Cheng
2022-10-25 8:16 ` 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=2b44a657cd32ba83a1427ed32090ac71da3fad5e.camel@siemens.com \
--to=baocheng.su@siemens.com \
--cc=cip-dev@lists.cip-project.org \
--cc=jan.kiszka@siemens.com \
--cc=sven.schultschik@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