From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([209.51.188.92]:58737) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hG8kp-0003Y9-Ai for guix-patches@gnu.org; Mon, 15 Apr 2019 17:03:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hG8ko-0004gT-Ak for guix-patches@gnu.org; Mon, 15 Apr 2019 17:03:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:50333) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hG8ko-0004gI-4k for guix-patches@gnu.org; Mon, 15 Apr 2019 17:03:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hG8ko-0004XT-0v for guix-patches@gnu.org; Mon, 15 Apr 2019 17:03:02 -0400 Subject: [bug#35217] gnu: u-boot: Update to 2019.04. Resent-Message-ID: Date: Mon, 15 Apr 2019 23:02:14 +0200 From: Danny Milosavljevic Message-ID: <20190415230214.31877ad1@scratchpost.org> In-Reply-To: <87v9zl33hh.fsf@ponder> References: <87h8b6ia13.fsf@ponder> <87zhox33vu.fsf@ponder> <87v9zl33hh.fsf@ponder> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/Q5wq0.id5sxQ5.RN1Wo++zV"; protocol="application/pgp-signature" List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Vagrant Cascadian Cc: 35217@debbugs.gnu.org --Sig_/Q5wq0.id5sxQ5.RN1Wo++zV Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hi Vagrant, On Wed, 10 Apr 2019 15:22:18 -0700 Vagrant Cascadian wrote: > > On 2019-04-10, Vagrant Cascadian wrote: > > * gnu/packages/bootloaders (u-boot): Update to 2019.04. =20 > ... > > (u-boot-am335x-evm): New variable. > > (u-boot-am335x-boneblack): Deprecate variable. =20 >=20 > The am335x-boneblack configuration was dropped from upstream. >=20 > The am335x-evm image is considerably larger than the am335x-boneblack > images, which leads to issues when installing at a device offset, as it > will overwrite the first partition unless the first partition starts > significantly later than most tools (parted, cfdisk) default of sector > 2048 (beagleboard.org images start the first partition at sector 8192). >=20 > The embedded-os-installation code should probably check to make sure > they aren't trampling the first partition if installing to the raw > device offset. That would make the parted bindings a hard dependency, probably even build-side. But I think that would still be better than the alternative: destroying user filesystems. > Alternately, it's possible to copy the u-boot.img onto the first FAT > partition of the microSD/eMMC, which will be loaded instead of the > offset. But that takes some rethinking of how to install the bootloader > (which would be good to not diverge from upstream for other platforms, > such as u-boot-novena). Yeah, I think sooner or later it's going to come to this. Might as well bite the bullet now. > In light of all that, I'm not sure what a proper way forward is... Yeah, sounds like a bad situation with no nice solution that allows updating of existing installations. In that case, keeping existing installations on the old version would be preferrable to breaking them. --Sig_/Q5wq0.id5sxQ5.RN1Wo++zV Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEds7GsXJ0tGXALbPZ5xo1VCwwuqUFAly08VYACgkQ5xo1VCww uqWS6Af9GwqyupWEmemtQkHnlNwAcFPktXjrC0qUltDn8w5EJ0v+F8b2wBC7zJ7r V4On0loBt2UHjOAOdqQQbfLQTQYhP6Ld8hPOVFxh9rOhFdsCU8Y5N54PLVMyW58d x/2DOgqU44DQizsz3fHu8yNK1jFnzhgfN3sBBWxuweumyAIO+Yw/JOXNYEKFMTCP 3e/OZ07Sk3iSOmWXo7BIcOwccYaO0b1tY7r2NzLrB83Meiu4/ReY0ZHKx2wkwRUH 6Jfy3YVtTR9xBJ4JRh4yZl5HDE1WAqMCYmvPXYRHk5lwTqvZKwdugb+tCA+KzWum KTtow5jPfnrhur5Msp1jmyoR+2zDqQ== =56sX -----END PGP SIGNATURE----- --Sig_/Q5wq0.id5sxQ5.RN1Wo++zV--