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
..
base-files	treewide: remove execute bit and shebang from board.d files	2021-03-06 11:30:06 +01:00
config-5.10	kernel: cut broken SPI_NOR 4K eraseblock LIMIT patch	2022-06-29 12:34:49 +02:00
target.mk	treewide: use wpad-basic-wolfssl as default	2020-08-20 14:19:39 +02:00