On Fri, Oct 20, 2017 at 04:33:57PM -0500, Dennis Gilmore wrote:
El jue, 19-10-2017 a las 16:58 +0200, Maxime Ripard escribió:
On Thu, Oct 19, 2017 at 03:42:11PM +0100, Andre Przywara wrote:
Hi,
On 19/10/17 14:24, Maxime Ripard wrote:
On Thu, Oct 19, 2017 at 02:03:55PM +0100, Andre Przywara wrote:
Hi,
On 19/10/17 09:26, Maxime Ripard wrote:
Hi,
Most featureful boards, such as the Cubietruck, have been broken since the release 2017.09.
This is due to a size increase of the binary that will trip us across the size we've been using in the u-boot-sunxi-with-spl.bin file.
We would have two ways to work around it. The first one would be to just increase the offset of the environment. However, since it would break all the environments of our users and possibly the custom partition scheme that they would have created, it doesn't really seem like a smart move.
Is that really such a problem? How many people rely on having their custom environment preserved over an update? (That's an honest question)
All of them, I guess. In your U-boot upgrade script, do you do a 'env default -a; saveenv' all the time ?
I know I don't.
Well, I never use the saved environment and always expected some user or board specific environment to come from some file (boot.scr or something loaded via TFTP). But that's just my personal use, hence I was asking.
Well, even if you want to boot to tftp, you'll need to have some setup to do, even just to use a different server IP, and that will be in the environment.
I personally just use pxe boot
It's not really about what personally you use, but what any user can use.
dhcp pxe get pxe boot and pick the right option. nothing needed on the client side.
It has the assumption that the DHCP server is setup properly, which might or might not be the case, especially when it comes to the server option being there and valid.
Maxime