Date: Sat, 22 Oct 2016 22:42:47 +0200 From: Bernd Walter <ticso@cicely7.cicely.de> To: Mark Millard <markmi@dsl-only.net> Cc: ticso@cicely.de, freebsd-arm@freebsd.org Subject: Re: [SPAM] Issue booting RPI2 B (v1.2) [V1.2 is BVM2837 and quad-core Cortex-A53 based] Message-ID: <20161022204247.GC96251@cicely7.cicely.de> In-Reply-To: <9BF0FDD6-932B-4656-B7B2-C23AD540A933@dsl-only.net> References: <ca0b4873-bea3-69e0-82b4-199e06bb4dee@ixsystems.com> <053B3B99-E4D9-4714-ACCF-AA846E1855CE@dsl-only.net> <1C2BA80D-FAB7-49D2-8D02-5CE1431953CF@dsl-only.net> <38a4152b-e27e-baa3-33a6-cd7318026569@ixsystems.com> <20161022200449.GB96251@cicely7.cicely.de> <9BF0FDD6-932B-4656-B7B2-C23AD540A933@dsl-only.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Oct 22, 2016 at 01:22:08PM -0700, Mark Millard wrote: > On 2016-Oct-22, at 1:04 PM, Bernd Walter <ticso at cicely7.cicely.de> wrote: > > > WTF - why can't they use a different name for something completely > > different. > > This isn't just a PCB version change, especially not a change in a > > minor number. > > In other words I need to keep my thumb on the Pi 2s I recently got, > > since those are the old ones. > > Got mine just 2 months ago directly from RS, maybe they still have a > > stock on the previos Pi 2. > > The modern versions of the official operating system supports both V1.1 and V1.2 of the board, allowing existing programs to continue to work on newer boards. (At least that is my understanding.) > > It is a different SOC but with the new one configured for use for extreme compatibility with the old one from what I can tell. (User space code, anyway, including using official interfaces to things on the board.) They do not claim to support 64 bit at all: just Cortex-A7 compatibility. > > For their primary target customers it is not "completely different". > > That other operating systems might choose to go in a different direction is not a consideration for them: what they support is very compatible even though the hardware does not require such configuration. It is not just other OS. There are tons of customized Pi Images out there for different kind of application type of things, which can't boot until updated by the vendor first. Usually this wouldn't be a big deal, since you boot them and start an update. Many kind of common use cases run customized kernels e.g. to run SPI based displays. Gratend - force them to use updated Linux kernels seem to be wise given the recent Linux kernel bugs, but on the other hand I guess the timing is so bad that they might miss that fix. > (I'd have preferred RPI2C vs. RPI2B for naming at least. But I'm not using the official materials generally so the issue is more noticable.) Me too. -- B.Walter <bernd@bwct.de> http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20161022204247.GC96251>