On 9/10/23 04:55, Paul Wise wrote:
I think any modern (at least more than 10 years of lifespan) bootloader (u-boot, redboot, barebox, etc.,...) can read from any supported filesystem (at least ext2, ext3 and ext4 and maybe nand-related filesystems like yaffs, yaffs2, ubifs), so having the {z|u}Image kernel stored on those filesystems should be not an issue...On Sat, 2023-09-09 at 11:42 +0200, Bastian Blank wrote:The first one is the one with included size limitations, because those load the kernel from a pre-defined flash partition, whose size can't be easily changed by the user. This one is now overflowing for the second to last documented one in the kernel package config.Seems like this would be solvable by writing a bootloader to the flash partition that would be able to load Linux from a normal filesystem?
The biggest problem will be the update procedures for those hardware. All scripts must be changed to reflect the new partition scheme. This is *not* an easy fix.
Just my $0.02 Regards Gianluca -- Eurek s.r.l. | Electronic Engineering | http://www.eurek.it via Celletta 8/B, 40026 Imola, Italy | Phone: +39-(0)542-609120 p.iva 00690621206 - c.f. 04020030377 | Fax: +39-(0)542-609212