John Thomson ef69ab7a35 kernel: cut broken SPI_NOR 4K eraseblock LIMIT patch ... Since 4e0c54bc5b ("kernel: add support for kernel 5.4"), the spi-nor limit 4k erasesize to spi-nor chips below a configured size patch has not functioned as intended. For uniform erasesize SPI-NOR devices, both nor->erase_opcode & mtd->erasesize are used in erase operations. These are set before, and not modified by, this CONFIG_MTD_SPI_NOR_USE_4K_SECTORS_LIMIT patch. Thus, an SPI-NOR device with CONFIG_MTD_SPI_NOR_USE_4K_SECTORS will always use 4k erasesize (where the device supports it). If this patch was fixed to function as intended, there would be cases where devices change from a 4K to a 64K erasesize. Signed-off-by: John Thomson <git@johnthomson.fastmail.com.au>		2022-06-29 12:34:49 +02:00
..
imagebuilder	imagebuilder: export SOURCE_DATE_EPOCH to environment	2022-04-10 00:56:38 +01:00
linux	kernel: cut broken SPI_NOR 4K eraseblock LIMIT patch	2022-06-29 12:34:49 +02:00
llvm-bpf	llvm-bpf: fix rebuild check for generating tarball	2021-11-26 11:37:19 +01:00
sdk	build: scripts/config - update to kconfig-v5.14	2022-02-19 13:10:01 +01:00
toolchain	toolchain: switch packaged toolchain to tar.xz	2021-10-21 08:25:38 -10:00
Config.in	base-files: add eMMC sysupgrade support	2021-12-02 20:42:58 +00:00
Makefile	tools/llvm-bpf: move tarball packing to target/llvm-bpf	2021-11-22 12:00:40 +01:00