Date: Wed, 19 Oct 2016 07:22:25 -0400 From: Diane Bruce <db@db.net> To: Warner Losh <imp@bsdimp.com> Cc: Shawn Webb <shawn.webb@hardenedbsd.org>, "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org>, Ross Alexander <rwa@athabascau.ca> Subject: Re: Raspberry Pi 3 support Message-ID: <20161019112224.GA10536@night.db.net> In-Reply-To: <CANCZdfoO7e3ZkzGZVUjF9tMqm0t7=RYY2-_JxRV_%2BTs6OOZQFg@mail.gmail.com> References: <mailman.62.1476446401.6092.freebsd-arm@freebsd.org> <alpine.BSF.2.20.1610170004010.2176@autopsy.pc.athabascau.ca> <20161017140631.GA77580@mutt-hardenedbsd> <20161018194958.GC22296@mutt-hardenedbsd> <2BC88734-CF40-4702-9483-ADEBA23C11F2@bluezbox.com> <20161019002146.GA57025@mutt-hardenedbsd> <CANCZdfoO7e3ZkzGZVUjF9tMqm0t7=RYY2-_JxRV_%2BTs6OOZQFg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Oct 19, 2016 at 01:46:20AM -0600, Warner Losh wrote: ... > I've updated the nanobsd build. > > Is the u-boot-rpi3 port different from the other u-boot ports in > requiring someone to snag firmware in addition to u-boot? Will that be > fixed? Or should I go ahead and fix it when I get to rpi3 in my uboot > cleanup? I looked at how the rpi2 u boot port did it. crochet (or whoever) is responsible for building a dtb from a source dts we have. So for now the rpi3 port does not provide the dtb files but will provide the broadcom binary (as the RPI2 port does). Really this is one place where the RPi2 and RPi3 ports could share easily as the firmware should be the same. We need to chat about this further ;) Diane > > Warner > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > -- - db@FreeBSD.org db@db.net http://www.db.net/~db
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20161019112224.GA10536>