On Mon, 4 Jan 2021, at 12:28, John Thomson wrote:
> --- a/drivers/mtd/mtdpart.c
> +++ b/drivers/mtd/mtdpart.c
> @@ -38,10 +38,11 @@ static struct mtd_info *allocate_partition(struct
> mtd_info *parent,
> struct mtd_info *master = mtd_get_master(parent);
> int wr_a
access to 4K erase without
requiring CONFIG_MTD_SPI_NOR_USE_4K_SECTORS
Introduce mtd struct erasesize_minor,
the smallest erasesize supported by the device.
Do not prevent writing to mtd partitions where a partition boundary sits
on a minor erasesize boundary.
Signed-off-by: John Thomson
---
Have
work boot tested this change on ath79 hardware:
- kernel vmlinuz.bin
then appended DTB, and packed into a uImage (out of kernel tree)
- kernel vmlinuz
then updated ELF DTB appended_dtb section, and ELF booted
Cheers,
--
John Thomson
I think it would be safer to make these changes by adding a different
boot/compressed target: vmlinuz.elf?
So that this would not break kernel build cases where both a normal
RAW_APPENDED_DTB zImage is wanted, and additionally an ELF boot vmlinuz.elf.
--
John Thomson
ELF:
objcopy --update-section .appended_dtb=.dtb vmlinuz
Signed-off-by: John Thomson
---
arch/mips/Kconfig | 21 +
arch/mips/boot/compressed/decompress.c | 4
arch/mips/boot/compressed/vmlinuz.lds.S | 9 +
3 files changed, 34 insertions
Preprocess vmlinuz (self-decompressing kernel ELF) linker script
to avoid using ld -Ttext $(address)
https://lkml.kernel.org/lkml/20200413153453.zi4jvu3c4ul23...@google.com/
Signed-off-by: John Thomson
---
arch/mips/boot/compressed/.gitignore | 1 +
arch/mips/boot/compressed
6 matches
Mail list logo