Date: Mon, 2 Feb 2015 20:16:49 -0700 From: Warner Losh <imp@bsdimp.com> To: Dan Raymond <draymond@foxvalley.net> Cc: freebsd-arm@freebsd.org Subject: Re: RPi 2 B+? Message-ID: <DF7D699A-8811-480B-AD46-4CE11D7A1AF8@bsdimp.com> In-Reply-To: <54D01B6D.9040309@foxvalley.net> References: <20150202111352.GA2060@in-addr.com> <54CF5CC8.8050601@selasky.org> <20150202112205.GA29086@in-addr.com> <CAJ-VmonVZB8=uwSSwpJTzdhDROu6WDrCMXYbzMgKu_o%2B5KFR2Q@mail.gmail.com> <54D01B6D.9040309@foxvalley.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Feb 2, 2015, at 5:50 PM, Dan Raymond <draymond@foxvalley.net> = wrote: >=20 > On 2/2/2015 9:08 AM, Adrian Chadd wrote: >> =46rom someone at the RPI foundation: >>=20 >> "All peripheral blocks detailed in the BCM2835 datasheet are >> applicable to BCM2836. The only thing that's changed in regards to >> these bits is the peripheral register set base address - which I >> believe is now placed at 0x3F000000." >>=20 >> still requires an updated uboot and some new glue for the new SoC = (DTS >> files, for example.) >>=20 >>=20 >>=20 >> -adrian >=20 > Will any changes be needed for FreeBSD to take advantage of SMP now = that the Raspberry Pi has 4 cores instead of 1? I imagine compiling for = ARMv7 instead of ARMv6 will incur performance improvements. Will that be = a simple transition? It will also be nice to have access to = pre-compiled ports. Most of the performance gain is marginal over the armv6hf port. = Compiling for armv7 would mean the packages wouldn=E2=80=99t work on the = original RPi, which is too high a cost for the marginal improvements. Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?DF7D699A-8811-480B-AD46-4CE11D7A1AF8>