On 2016-07-24 09:20, Bjarne Saltbæk wrote:
Hi Gordan.
It just "tickles my OCD" that i have to set uboot boot and root args
different for every arm device.
I am not sure there is really a way around it. But if you want to
standardize on FAT16 /boot, I guess that's livable with.
Could we not agree on a 256 mb boot partition 1 and OS size specific
root partition 2 for a Redsleeve SD card?
I'd probably go as far as 512MB for the /boot partition. Depending
on what you want in your initrd it is not at all unusual for it to
bloat to over 20MB. Then there's the kernels and some supporting
files. If you like to keep more than 2-3 kernels around for testing,
256MB can become tight. Also note that UEFI _requires_ a FAT32
partition of a certain number of sectors, which with 4KB sectors
amounts to about 260MB, but that gets mounted under /boot/efi, rather
than /boot, so not strictly speaking a part of this discussion. I
am merely mentioning it to point out that as UEFI becomes more
commonly used on ARM, things will change anyway.
I am open for a discussion about file systems. Thats a minor
kernel/uboot compilation issue to me.
I'm in favour of building both FAT and ext* into u-boot (I believe
this is the default anyway). As far as I understand, this thread
is about having to use fatload vs. extload to get the kernel and
initramfs loaded into memory from u-boot.
And then there's the devices that use something other than
u-boot. Granted, those are getting increasingly ending up in
landfills, and the newest ones are supporting UEFI.
Gordan
_______________________________________________
users mailing list
[email protected]
https://lists.redsleeve.org/mailman/listinfo/users
