This patch series aims to make automated testing of all supported targets easy.
Not all targets are actually tested for a variety of reasons, but this series
covers a significant portion of the target space and should make it easy to
add more targets as we figure out how do run their tests. All sup
Signed-off-by: Glenn Washburn
---
scripts/ci/build.sh | 67
scripts/ci/functions.sh | 33 ++
scripts/ci/make-images.sh | 86 ++
scripts/ci/process-tests.sh | 111 +
scripts/ci/test.sh |
Signed-off-by: Glenn Washburn
---
scripts/ci/functions.local.sh | 37 +
scripts/local-tester.sh | 39 +++
2 files changed, 76 insertions(+)
create mode 100644 scripts/ci/functions.local.sh
create mode 100755 scripts/local-tes
Gentle ping?
Without this patch, the new mkfs.btrfs NO_HOLES feature would break any
kernel/initramfs with hole in it.
And considering the modification is already small, I believe this patch
is definitely worthy as a bug fix.
Thanks,
Qu
On 2021/10/16 09:40, Qu Wenruo wrote:
[BUG]
Grub btr
Signed-off-by: Glenn Washburn
---
scripts/ci/functions.sh | 899 +++-
1 file changed, 898 insertions(+), 1 deletion(-)
diff --git a/scripts/ci/functions.sh b/scripts/ci/functions.sh
index 2f4cecaa1..f94f90dc1 100644
--- a/scripts/ci/functions.sh
+++ b/scripts/
On Thu, Oct 28, 2021 at 03:36:10PM +0800, The development of GNU GRUB wrote:
> Gentle ping?
>
> Without this patch, the new mkfs.btrfs NO_HOLES feature would break any
> kernel/initramfs with hole in it.
>
> And considering the modification is already small, I believe this patch is
> definitely w
[BUG]
Grub btrfs implementation can't handle two very basic btrfs file
layouts:
1. Mixed inline/regualr extents
# mkfs.btrfs -f test.img
# mount test.img /mnt/btrfs
# xfs_io -f -c "pwrite 0 1k" -c "sync" -c "falloc 0 4k" \
-c "pwrite 4k 4k" /mnt/btrfs/file
# umount /mnt/
On 2021/10/28 17:27, Michael Chang wrote:
On Thu, Oct 28, 2021 at 03:36:10PM +0800, The development of GNU GRUB wrote:
Gentle ping?
Without this patch, the new mkfs.btrfs NO_HOLES feature would break any
kernel/initramfs with hole in it.
And considering the modification is already small, I b
Originally added in 9fbdec2f6b4fa8b549daa4d49134d1fe89d95ef9 and
subsequently modified in 552c9fd08122a3036c724ce96dfe68aa2f75705f,
fix-base64.patch handled two problems we have using gnulib, which are
exerciesd by the base64 module but not directly caused by it.
First, grub2 defines its own bool
From: Ard Biesheuvel
Recent Linux kernels will invoke the LoadFile2 protocol installed on
a well-known vendor media path to load the initrd if it is exposed by
the firmware. Using this method is preferred for two reasons:
- the Linux kernel is in charge of allocating the memory, and so it can
i
Hello,
This is the third version of the patch series. In v3 the series was rebased
on top of the master branch.
This series contains patches to add support for LoadFile2 protocol to load
initrd on EFI systems. Also it contains patches to load Linux kernel with EFI
stub on riscv platforms and unit
From: Atish Patra
ARM64 linux loader code is written in such a way that it can be reused
across different architectures without much change. Move it to common
code so that RISC-V doesn't have to define a separate loader.
Signed-off-by: Atish Patra
---
grub-core/Makefile.core.def |
In the case of an error grub_initrd_load() uses argv[] to print the
filename that caused the error. It is also possible to obtain the
filename from the file handles and there is no need to duplicate that
information in argv[], so let's drop it.
Signed-off-by: Nikita Ermakov
---
grub-core/loader/
From: Ard Biesheuvel
Now that we implemented supported for the LoadFile2 protocol for initrd
loading, there is no longer a need to pass the initrd parameters via
the device tree. This means there is no longer a reason to update the
device tree in the first place, and so we can ignore it entirely.
From: Ard Biesheuvel
Incorporate the EFI_LOAD_FILE2_PROTOCOL GUID and C types from the
UEFI spec.
Signed-off-by: Ard Biesheuvel
Reviewed-by: Heinrich Schuchardt
Signed-off-by: Nikita Ermakov
---
grub-core/commands/efi/lsefi.c | 1 +
include/grub/efi/api.h | 15 +++
2 fil
From: Atish Patra
RISC-V doesn't have to do anything very different from other architectures
to loader EFI stub linux kernel. As a result, just use the common linux
loader instead of defining a RISC-V specific linux loader.
Signed-off-by: Atish Patra
---
grub-core/Makefile.core.def| 4 +--
From: Atish Patra
Update the RISC-V Linux kernel image headers as per the current header.
Reference:
/Documentation/riscv/boot-image-header.rst
Signed-off-by: Atish Patra
---
include/grub/riscv32/linux.h | 15 ---
include/grub/riscv64/linux.h | 15 ---
2 files changed,
On Tue, Oct 26, 2021 at 03:02:34PM +, Darren Kenny wrote:
> Coverity has flagged a number of small issues that should be fixed to help in
> cleaning up the code - these here are primarily memory leaks or uninitialized
> variables.
>
> In theory leaked memory is significant, but for short-lived
On Tue, Sep 21, 2021 at 03:07:25PM -0700, Julius Werner wrote:
> > Since it doesn't seem possible to have each boot component using the same
> > log
> > format, we added a log_format and log_phys_addr fields to give flexibility
> > in
> > how logs are stored. An example of a different log format
On 10/28/21 22:31, Nikita Ermakov wrote:
Hello,
This is the third version of the patch series. In v3 the series was rebased
on top of the master branch.
This series contains patches to add support for LoadFile2 protocol to load
initrd on EFI systems. Also it contains patches to load Linux kerne
20 matches
Mail list logo
