Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 11 Dec 2017 21:26:40 +0100
From:      Emmanuel Vadot <manu@bidouilliste.com>
To:        Warner Losh <imp@bsdimp.com>
Cc:        freebsd-uboot@freebsd.org
Subject:   Re: UBOOT version bump
Message-ID:  <20171211212640.6ef0a56321f9ca43000a2790@bidouilliste.com>
In-Reply-To: <CANCZdfrtSwAhPd_a45vh1UChh96fK20yQC92bLSRP3gH=C0prw@mail.gmail.com>
References:  <CANCZdfrtSwAhPd_a45vh1UChh96fK20yQC92bLSRP3gH=C0prw@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help

 Hi Warner,

On Mon, 4 Dec 2017 11:17:20 -0700
Warner Losh <imp@bsdimp.com> wrote:

> So, what's the issue with bumping to the 2017.11?
> 
> Warner
> _______________________________________________
> freebsd-uboot@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-uboot
> To unsubscribe, send any mail to "freebsd-uboot-unsubscribe@freebsd.org"

 Long story short, the efi part in u-boot 2017.11 was greatly improved
but the devpath feature (and others) have a few bugs that make
loader.efi and boot1.efi not working.

 As of just now I have u-boot master (2018.01-rc1) working with just
two patch :

 - https://patchwork.ozlabs.org/patch/846927/ (I don't think that it
will make it to 2018.01)
 -
https://people.freebsd.org/~manu/uboot/0001-efi_loader-Setup-logical_partition-media-information.patch
(that was just sent on review to u-boot list).

 I think that I will skip 2017.11 since we're a month behind, only a
month until 2018.01 and I haven't tested all the boards I have with
current u-boot master.

 Cheers,

-- 
Emmanuel Vadot <manu@bidouilliste.com>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20171211212640.6ef0a56321f9ca43000a2790>