Re: Broadcom BCM2709, ARMv8, and missing CPU features

On Sat, Aug 06, 2016 at 04:25:13PM +0100, Luke Kenneth Casson Leighton wrote: > did i hear right that there's also a core design difference between > the A7 and the A53 which results in a performance/watt loss of around > 15%? so you're actually *worse off* going to 64-bit at the moment, if >

Re: Broadcom BCM2709, ARMv8, and missing CPU features

On Tue, Jul 26, 2016 at 11:28 PM, Jeffrey Walton wrote: > Hi Everyone, > > I recently purchased a Raspberry Pi 3. Its got a Broadcom SoC, and its > ARMv8. Its running a Debian-lite kernel, which I believe is a modified > 4.4 kernel. > > Below is the output from cpuinfo. I see

Re: Broadcom BCM2709, ARMv8, and missing CPU features

> the reason i ask that is, i'm not seeing any real difference: you > still have to download the linux kernel source (to submit dtsi > patches), the linux git repo is still the central location for dtsi > management... unless you're happy to set up an alternative parallel > repository (and

Re: Broadcom BCM2709, ARMv8, and missing CPU features

--- crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68 On Sat, Aug 6, 2016 at 8:15 PM, Stefan Monnier wrote: >> the only big advantage of dtb files (binary compiled) is *IF* the >> decision is made to respect dtb files and treat them as inviolate

Re: Broadcom BCM2709, ARMv8, and missing CPU features

> the only big advantage of dtb files (binary compiled) is *IF* the > decision is made to respect dtb files and treat them as inviolate > and supported forever without needing recompiles, you stand a > chance of being able to upgrade linux kernels *without* replacing > the dtb file. That

Re: Broadcom BCM2709, ARMv8, and missing CPU features

--- crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68 On Sat, Aug 6, 2016 at 2:57 PM, Stefan Monnier wrote: > Note also that you will sometimes *lose* performance by going to 64bit > because the pointers use up twice as much space, so if your

Re: Broadcom BCM2709, ARMv8, and missing CPU features

--- crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68 On Thu, Jul 28, 2016 at 5:35 PM, Gunnar Wolf wrote: > Keep in mind it's not different Debian images we are talking about — > "real" Debian cannot be booted on Raspberry hardware. I run a Debian >

Re: Broadcom BCM2709, ARMv8, and missing CPU features

> physically). What you often gain going to a 64 bit CPU is the ability > to do 64 bit arithmetic in one instruction, and store the variables [...] > 32 bit calculations, then it doesn't matter, so in many cases it isn't an > issue, but when it matters it can really make a difference in

Re: Broadcom BCM2709, ARMv8, and missing CPU features

On 28/07/16 17:35, Gunnar Wolf wrote: I'm far from an absolute expert in this area... But I am fairly certain of what I say — That is, I have a RPi 1 and 2B, and they cannot boot from the same images. That depends what is in the image. The current raspberry pi firmware works on all pi

Re: Broadcom BCM2709, ARMv8, and missing CPU features

On 2016-07-28, Gunnar Wolf wrote: > Alan Corey dijo [Thu, Jul 28, 2016 at 12:22:23PM -0400]: >> Huh? I thought they claimed they were interchangeable. I had an >> image from my model B days 3 years ago that I booted on my 3B. And I >> cloned a working current 3B SD card and booted a Zero from

Re: Broadcom BCM2709, ARMv8, and missing CPU features

On Thu, Jul 28, 2016 at 12:22:23PM -0400, Alan Corey wrote: > Huh? I thought they claimed they were interchangeable. I had an > image from my model B days 3 years ago that I booted on my 3B. And I > cloned a working current 3B SD card and booted a Zero from it. There > isn't a different Debian

Re: Broadcom BCM2709, ARMv8, and missing CPU features

Alan Corey dijo [Thu, Jul 28, 2016 at 12:22:23PM -0400]: > Huh? I thought they claimed they were interchangeable. I had an > image from my model B days 3 years ago that I booted on my 3B. And I > cloned a working current 3B SD card and booted a Zero from it. There > isn't a different Debian

Re: Broadcom BCM2709, ARMv8, and missing CPU features

Huh? I thought they claimed they were interchangeable. I had an image from my model B days 3 years ago that I booted on my 3B. And I cloned a working current 3B SD card and booted a Zero from it. There isn't a different Debian image for every brand of motherboard and CPU, they probe to see

Re: Broadcom BCM2709, ARMv8, and missing CPU features

Alan Corey dijo [Wed, Jul 27, 2016 at 01:28:31PM -0400]: > > 64-bit/ARMv8 on the RPi3 is still in progress. > > Yes, so they claim and I wonder how they're going to deal with the > fact that some Pis are 32 bit and some 64. I posted this question > there but I haven't looked into the links in

Re: Broadcom BCM2709, ARMv8, and missing CPU features

> Using '.byte' below rather than '.inst' or '.inst.w' is another can of > worms... > > $ gcc -g3 -O0 -march=armv7-a -mfpu=neon test.cc -o test.exe > $ ./test.exe > $ > > $ cat test.cc > #include > int main(int argc, char* argv[]) > { > __asm__ __volatile__ > ( > ".code 32" > > //

Re: Broadcom BCM2709, ARMv8, and missing CPU features

On Thu, Jul 28, 2016 at 3:06 AM, Tixy wrote: > On Thu, 2016-07-28 at 02:38 -0400, Jeffrey Walton wrote: > [...] >> >> // AES (aese) >> >> ".byte 0x4e, 0x28, 0x48, 0x20;\n" >> > >> > So as instructions are little-endian that's 0x2048284e for a 32-bit >> > instruction, or

Re: Broadcom BCM2709, ARMv8, and missing CPU features

On Thu, 2016-07-28 at 02:38 -0400, Jeffrey Walton wrote: [...] > >> // AES (aese) > >> ".byte 0x4e, 0x28, 0x48, 0x20;\n" > > > > So as instructions are little-endian that's 0x2048284e for a 32-bit > > instruction, or 0x284e2048 if it's a Thumb2 instruction (I'm showing > > that the same

Re: Broadcom BCM2709, ARMv8, and missing CPU features

>> Using '.byte' below rather than '.inst' or '.inst.w' is another can of >> worms... > > And if I'm not mistaken, the part of the reason why you got the > instructions wrong... > >> $ gcc -g3 -O0 -march=armv7-a -mfpu=neon test.cc -o test.exe >> $ ./test.exe >> $ > > Does the tool-chain default

Re: Broadcom BCM2709, ARMv8, and missing CPU features

On Thu, 2016-07-28 at 00:48 -0400, Jeffrey Walton wrote: > Using '.byte' below rather than '.inst' or '.inst.w' is another can of > worms... And if I'm not mistaken, the part of the reason why you got the instructions wrong... > $ gcc -g3 -O0 -march=armv7-a -mfpu=neon test.cc -o test.exe > $

Re: Broadcom BCM2709, ARMv8, and missing CPU features

On Wed, Jul 27, 2016 at 2:18 AM, Paul Wise wrote: > On Wed, Jul 27, 2016 at 11:28 AM, Jeffrey Walton wrote: > >> I recently purchased a Raspberry Pi 3. Its got a Broadcom SoC, and its >> ARMv8. > ... >> model name: ARMv7 Processor rev 4 (v7l) > > Looks like you are running it

Re: Broadcom BCM2709, ARMv8, and missing CPU features

On Thu, Jul 28, 2016 at 1:28 AM, Alan Corey wrote: > Yes, so they claim and I wonder how they're going to deal with the > fact that some Pis are 32 bit and some 64. ISTR that they plan on keeping 32-bit for the official stuff recommended by the RPi folks for simplification. -- bye, pabs

Re: Broadcom BCM2709, ARMv8, and missing CPU features

> 64-bit/ARMv8 on the RPi3 is still in progress. Yes, so they claim and I wonder how they're going to deal with the fact that some Pis are 32 bit and some 64. I posted this question there but I haven't looked into the links in the response a lot:

Re: Broadcom BCM2709, ARMv8, and missing CPU features

On Wed, Jul 27, 2016 at 11:28 AM, Jeffrey Walton wrote: > I recently purchased a Raspberry Pi 3. Its got a Broadcom SoC, and its > ARMv8. ... > model name: ARMv7 Processor rev 4 (v7l) Looks like you are running it in ARMv7 32-bit mode, perhaps that disables the ARMv8 features. I recently

Broadcom BCM2709, ARMv8, and missing CPU features

Hi Everyone, I recently purchased a Raspberry Pi 3. Its got a Broadcom SoC, and its ARMv8. Its running a Debian-lite kernel, which I believe is a modified 4.4 kernel. Below is the output from cpuinfo. I see ARMv8's crc32 is available, but I don't see pmull, aes or sha. At the moment, I'm not