Re: [ptxdist] [PATCH] barebox: Remove all images from multi-image installs.

On Sat, Feb 26, 2022 at 06:28:57PM +0100, Christian Melki wrote: > The multi-image install is a bit peculiar. > It installs several target images and decides to softlink > the last image to barebox-image, which is then used for image installs etc. > The barebox-image only by chance pointing at the

[ptxdist] [PATCH] image-root-cpio: Add compressor options to the env.

* xz needs crc32 instead of crc64 for the kernel cpio. * Set zstd compression level to the same as for the kernel (19). * Use multithreading for zstd (deterministic, afaiu). Actively decided against -T0 for xz, as compression is not deterministic when number of threads varies. Signed-off-by:

[ptxdist] [PATCH] qemu: Add possibility to drop edk2 firmware.

EDK2 firmware files are large and very sparse ROM images. The set currently borders 200M. AFAIK, QEMU can't load compressed raw firmware files. So add the possibility to drop EDK2 in case it's unused. Signed-off-by: Christian Melki --- rules/qemu.in | 8 rules/qemu.make | 4 2

Re: [ptxdist] Patch series for package per project?

Hei hei, it's me again, I want to add some more thoughts on this. O:-) On Thu, Mar 03, 2022 at 09:11:39PM +0100, Alexander Dahl wrote: > Hello Christian, > > On Thu, Mar 03, 2022 at 08:37:45PM +0100, Christian Melki wrote: > > On 3/3/22 18:07, Felix Mellmann wrote: > > > On 03.03.22 15:22,

Re: [ptxdist] Patch series for package per project?

Hello Christian, On Thu, Mar 03, 2022 at 08:37:45PM +0100, Christian Melki wrote: > On 3/3/22 18:07, Felix Mellmann wrote: > > On 03.03.22 15:22, Christian Melki wrote: > >> Just one barebox version, but for different archs, with different > >> patchsets. I'd like the patches to live in the same

Re: [ptxdist] Patch series for package per project?

On 3/3/22 18:07, Felix Mellmann wrote: > On 03.03.22 15:22, Christian Melki wrote: >> >> >> On 3/3/22 2:40 PM, Michael Olbrich wrote: >>> Hi, >>> >>> On Thu, Mar 03, 2022 at 10:17:07AM +0100, Christian Melki wrote: I want to use the same bootloader (barebox) for various projects. But

Re: [ptxdist] Patch series for package per project?

On 3/3/22 2:40 PM, Michael Olbrich wrote: Hi, On Thu, Mar 03, 2022 at 10:17:07AM +0100, Christian Melki wrote: I want to use the same bootloader (barebox) for various projects. But patches are slightly different. series. doesn't seem to work. Have I missed something? I just assumed that per

[ptxdist] [PATCH 6/6] vulkan-validationlayers: version bump 1.3.204.0 -> 1.3.204.1

Signed-off-by: Philipp Zabel --- rules/vulkan-validationlayers.make | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/rules/vulkan-validationlayers.make b/rules/vulkan-validationlayers.make index d727c7304cc2..f92f6a1eef4e 100644 --- a/rules/vulkan-validationlayers.make

[ptxdist] [PATCH 3/6] spirv-tools: version bump 1.3.204.0 -> 1.3.204.1

Signed-off-by: Philipp Zabel --- rules/spirv-tools.make | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/rules/spirv-tools.make b/rules/spirv-tools.make index 770df808107c..93fc1f18723b 100644 --- a/rules/spirv-tools.make +++ b/rules/spirv-tools.make @@ -14,8 +14,8 @@

[ptxdist] [PATCH 4/6] vulkan-loader: version bump 1.3.204.0 -> 1.3.204.1

Signed-off-by: Philipp Zabel --- rules/vulkan-loader.make | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/rules/vulkan-loader.make b/rules/vulkan-loader.make index b621a4c31cac..0d88b78c98c0 100644 --- a/rules/vulkan-loader.make +++ b/rules/vulkan-loader.make @@ -14,8

[ptxdist] [PATCH 5/6] vulkan-tools: version bump 1.3.204.0 -> 1.3.204.1

Signed-off-by: Philipp Zabel --- rules/vulkan-tools.make | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/rules/vulkan-tools.make b/rules/vulkan-tools.make index c794e20a6ebe..7e297d83938c 100644 --- a/rules/vulkan-tools.make +++ b/rules/vulkan-tools.make @@ -14,8 +14,8 @@

[ptxdist] [PATCH 2/6] spirv-headers: version bump 1.3.204.0 -> 1.3.204.1

Signed-off-by: Philipp Zabel --- rules/spirv-headers.make | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/rules/spirv-headers.make b/rules/spirv-headers.make index 6fba1b6058c1..dc425b753a8a 100644 --- a/rules/spirv-headers.make +++ b/rules/spirv-headers.make @@ -14,8

[ptxdist] [PATCH 1/6] glslang: version bump 1.3.204.0 -> 1.3.204.1

Signed-off-by: Philipp Zabel --- rules/glslang.make | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/rules/glslang.make b/rules/glslang.make index 5a65ef5ae093..b31424b6b70c 100644 --- a/rules/glslang.make +++ b/rules/glslang.make @@ -14,8 +14,8 @@

Re: [ptxdist] Patch series for package per project?

Hi, On Thu, Mar 03, 2022 at 10:17:07AM +0100, Christian Melki wrote: > I want to use the same bootloader (barebox) for various projects. > But patches are slightly different. series. doesn't seem to work. > Have I missed something? I just assumed that per project patch series for > packages would

[ptxdist] Patch series for package per project?

Hi. I want to use the same bootloader (barebox) for various projects. But patches are slightly different. series. doesn't seem to work. Have I missed something? I just assumed that per project patch series for packages would be possible. I can see that kernel can steer the use of series file

Re: [ptxdist] [PATCH] lighttpd: version bump 1.4.63 -> 1.4.64

Hello Roland, On Tue, Mar 01, 2022 at 11:33:35AM +0100, Roland Hieber wrote: > On Thu, Jan 27, 2022 at 02:31:59PM +0100, Alexander Dahl wrote: > > Main change is "remove long-deprecated modules", but some bugfixes went > > in that release as well. > > > > Note: The ptxdist package still uses the