Date: Wed, 19 Oct 2016 11:33:47 -0700 (PDT) From: "Rodney W. Grimes" <freebsd-rwg@pdx.rh.CN85.dnsmgr.net> To: Diane Bruce <db@db.net> Cc: Warner Losh <imp@bsdimp.com>, "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org>, Ross Alexander <rwa@athabascau.ca> Subject: Re: Raspberry Pi 3 support Message-ID: <201610191833.u9JIXlb1037363@pdx.rh.CN85.dnsmgr.net> In-Reply-To: <20161019112224.GA10536@night.db.net>
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 ;) It would be very nice to support both 32 bit and 64 bit worlds on the RPI3. I am not sure if this can be done in one version of uboot, or if it would require two, as IIRC it is the binary blob running in the GPU that sets the CPU up for 32 or 64 bit. -- Rod Grimes rgrimes@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201610191833.u9JIXlb1037363>