Date: Sat, 12 Jan 2019 23:10:03 -0800 From: Mark Millard <marklmi@yahoo.com> To: Gleb Popov <arrowd@freebsd.org> Cc: uboot@freebsd.org Subject: Re: FreeBSD Port: sysutils/u-boot-orangepi-pc Message-ID: <A830CCCA-7523-4C21-9B33-8D8AFCEEA605@yahoo.com> In-Reply-To: <CANCZdfpqxNuA-bGMb7xaTUayoT5%2Bbx6Hb-iW4j5j9efHQrDSyQ@mail.gmail.com> References: <CALH631=8WFSR8gysUBvVmB4_b%2Bcvs3YGVEbqcjMh=8dS2cfdDQ@mail.gmail.com> <20190112133043.a6892af1285b957eb3a8b61b@bidouilliste.com> <CANCZdfpqxNuA-bGMb7xaTUayoT5%2Bbx6Hb-iW4j5j9efHQrDSyQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2019-Jan-12, at 09:30, Warner Losh <imp at bsdimp.com> wrote: > On Sat, Jan 12, 2019 at 5:31 AM Emmanuel Vadot <manu@bidouilliste.com> > wrote: >=20 >>=20 >> Hi, >>=20 >> On Sat, 12 Jan 2019 16:07:15 +0400 >> Gleb Popov <arrowd@freebsd.org> wrote: >>=20 >>> Hello. >>>=20 >>> I installed u-boot-orangepi-pc port, but there is no boot.img file >> anymore. >>> Consequently, crochet can't build an image for this board. Other = boards >>> (like u-boot-zedboard) do have this file in plist. >>> Am I missing something? >>>=20 >>> Thanks in advance. >>> _______________________________________________ >>> 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" >>=20 >> There never was a boot.img for orangepi-pc. >> The u-boot installation instruction as describe in pkg-descr >>=20 >> = https://svnweb.freebsd.org/ports/head/sysutils/u-boot-orangepi-pc/pkg-desc= r?revision=3D472710&view=3Dmarkup >=20 >=20 > All the allwinner boards have always used something similar to that... There are some AllWinner-based boards with prebuilt snapshots . . . https://wiki.freebsd.org/FreeBSD/arm/Allwinner lists (summary): Allwinner A10: Cubieboard=20 Allwinner A20: Banana Pi=20 Allwinner A64: Pine64=20 It does not list Pine64-LTS's Allwinner R18 and does not mention the PineBook, which also is A64 based. (There may be more unlisted that I've not familiar with.) For head : = https://lists.freebsd.org/pipermail/freebsd-snapshots/2019-January/000485.= html lists: o 13.0-CURRENT armv7 BANANAPI o 13.0-CURRENT armv7 CUBIEBOARD o 13.0-CURRENT aarch64 PINE64 o 13.0-CURRENT aarch64 PINE64-LTS o 13.0-CURRENT aarch64 PINEBOOK But I notice that = https://lists.freebsd.org/pipermail/freebsd-snapshots/2019-January/000488.= html does not list PINE64 but does still list PINE64-LTS and PINEBOOK. By contrast for stable/12 : = https://lists.freebsd.org/pipermail/freebsd-snapshots/2019-January/000489.= html does list PINE64 --but not the PINEBOOK: o 12.0-STABLE armv7 BANANAPI o 12.0-STABLE armv7 CUBIEBOARD o 12.0-STABLE aarch64 RPI3 o 12.0-STABLE aarch64 PINE64 o 12.0-STABLE aarch64 PINE64-LTS stable/11 : = https://lists.freebsd.org/pipermail/freebsd-snapshots/2019-January/000490.= html lists: o 11.2-STABLE armv6 BANANAPI o 11.2-STABLE armv6 CUBIEBOARD Of course, building the snapshots uses materials like Emmanuel suggested = for the example that does not have a pre-built snapshot in order to have uboot = in place. I periodically compare and contrast how I build vs. what the release = build scripts do for an appropriately similar example. And I monitor = sysutils/u-boot-*/ for updates. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A830CCCA-7523-4C21-9B33-8D8AFCEEA605>