On Saturday 23 September 2017 00:12:11 Alan Corey wrote:
> I don't know, it just works for me. Even over VNC, I just tried it
> from vncviewer on an OpenBSD machine. The "copy from device" is blank
> until I click the down arrow on it, then it finds /dev/mmcblk0. I'm
> running it on the
On 09/22/2017 03:57 PM, Uwe Kleine-König wrote:
>
> for the package sparse I have to distinguish armel and armhf. The reason
> is that sparse parses system headers and so has to know which cpp
> symbols to define. Usually it uses uname -m to distinguish platforms but
> that isn't suitable to tell
I don't know, it just works for me. Even over VNC, I just tried it
from vncviewer on an OpenBSD machine. The "copy from device" is blank
until I click the down arrow on it, then it finds /dev/mmcblk0. I'm
running it on the machine that's running tightvncserver which I'm
logged into. I use VNC
On Fri, Sep 22, 2017 at 3:57 PM, Uwe Kleine-König
wrote:
>...
> For armhf I need to define __ARM_PCS_VFP but that must be absent on armel.
Forgive my ignorance... If the compiler was built for the native
platform, then wouldn't the compiler and preprocessor definitions
On Friday 22 September 2017 22:14:48 Alan Corey wrote:
> I thought piclone was great for that. With a couple manual edits you
> can even clone an sd to a hard drive.
I have never been able to make it work. No helpfull manpage, nor does it
have a help option that I've found other than what you
I thought piclone was great for that. With a couple manual edits you
can even clone an sd to a hard drive.
On 9/22/17, Gene Heskett wrote:
> Greetings;
>
> Trying to dd a copy of the micro-sd card the pi-3b is booting from, to
> another micro-sd card in a usb
Greetings;
Trying to dd a copy of the micro-sd card the pi-3b is booting from, to
another micro-sd card in a usb reader/writer, and winding up with
nothing but an empty lost+found directory on it.
Obviously some sort of a syntax error, but it still takes the pi several
hours to do it, with
On Fri, Sep 22, 2017 at 09:57:02PM +0200, Uwe Kleine-König wrote:
>Hello,
>
>for the package sparse I have to distinguish armel and armhf. The reason
>is that sparse parses system headers and so has to know which cpp
>symbols to define. Usually it uses uname -m to distinguish platforms but
>that
On 09/22/2017 10:51 PM, John Paul Adrian Glaubitz wrote:
> Override the signal for SIGILL, then try to execute an instruction that is
> only available on either architecture, maybe?
That won't work. On an armv7 which runs armel (but which could run
armhf) the instruction will not fault but still
Override the signal for SIGILL, then try to execute an instruction that is only
available on either architecture, maybe?
Adrian
> On Sep 22, 2017, at 9:57 PM, Uwe Kleine-König wrote:
>
> Hello,
>
> for the package sparse I have to distinguish armel and armhf. The
Yeah, and cat /proc/cpuinfo doesn't really help much either. I don't
suppose it's kosher to look at some file names in
/var/cache/apt/archives. I had that problem with a phone I installed
Debian on a couple years ago. Finally gave up and left it armel when
I could have gone to armhf (I think).
Hello,
for the package sparse I have to distinguish armel and armhf. The reason
is that sparse parses system headers and so has to know which cpp
symbols to define. Usually it uses uname -m to distinguish platforms but
that isn't suitable to tell armel and armhf apart.
For armhf I need to define
On a Pi 3B with Raspbian Jessie I get:
==2188== Memcheck, a memory error detector
==2188== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==2188== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==2188== Command: ls
==2188==
getline.txt
InRelease
inrelease.txt
Hi everyone,
I'm getting mixed results trying to use valgrind on various ARM64
devices. Specifically, it works on my ODROID-C2 (Amlogic SoC with
kernel 3.14.29), and on my APM Xgene system with kernel 4.9.1801,
but not on a Scaleway virtual machine (Cavium ThunderX with kernel
4.9.23, under
Hi,
We'll have the traditional cross-distribution BoF at Linaro connect
Wednesday 27.9, at 3PM US pacific time - 22.00 UTC. We don't have a
set agenda, but if anything is bugging you, replying to this mail is
great way to make it into our topics :)
Riku
15 matches
Mail list logo