similar to: Problems building on Raspberry Pi

It depends, of course, what operating system you have installed on the RPi, but given that it's an ARM1176JZFS (ARMv6) chip, I would expect to see armv6, not armv4t, in the CPU part of the triple. It has a VFP unit, so I'd assume that you'd want to set hardfp (unless you installed an OS that doesn't support hardfp in its standard library), but if ld is complaining then you almost

Resampling to 48khz speeds them both up but the disparity is about the same: 2.609 to 3.69. Best Regards, Stuart Marsden On 17 December 2013 17:04, Stuart Marsden <stuartmarsden at finmars.co.uk>wrote: > Christian, > > Complexity 0, 6kbps: > > 0.9.14 Speed 5.204 > 1.1 Speed 5.218 > > A slight win on that run but they vary enough to say about the same. At >

I wanted to roughly benchmark how the different version of libopus performed at each complexity level for a 6kbit/s output opus file. This was conducted on a Raspberry Pi so it is a constant hardware platform. This was done on an early Pi so only 256MB RAM but it was never used up so should not make a difference. I compiled the three final versions of each major release of libopus so that was

Targetting the raspberry pi, what triple/flags should I set? I tried triple: armv4t-unknown-linux-gnueabi and ld fails with: a.out uses VFP register arguments if i set hardfloat (using optdata.FloatABIType = FloatABI::Hard), ld fails with an assertion: 2.22 assertion fail ../../bfd/elf32-arm.c:11477 what am I missing?

Hi Samuel, Can you see if this commit fixes the problem: https://git.xiph.org/?p=opus.git;a=commitdiff;h=4507637cc Jean-Marc On 20/05/17 02:55 AM, Samuel Bearg wrote: > Hello, > > I'm following the directions that 'make check' gave me: to e-mail you > log files. > > I'm attempting to build opus on a raspberry pi zero w, which I think has > more or less

On 25/05/17 10:03 PM, Samuel Bearg wrote: > Do I use --disable-intrinsics on ./configure, or on make? --disable-intrinsics is a configure option. It will not compile any of the Neon code. By default, the library builds with Neon support, but only enables it when it detects that it can at run-time. The run-time detection didn't work with the unit tests and that's what my patch fixes.

Jean-Marc, I can try both of the things you suggested. Maybe this coming weekend. I installed the Raspbian libopus-dev package instead of building it myself and that's been working great. Do I use --disable-intrinsics on ./configure, or on make? On Thu, May 25, 2017 at 9:28 PM, Jean-Marc Valin <jmvalin at jmvalin.ca> wrote: > Hi Samuel, > > Can you see if this commit fixes

Hello, I'm following the directions that 'make check' gave me: to e-mail you log files. I'm attempting to build opus on a raspberry pi zero w, which I think has more or less the original hardware as an original raspberry pi + WiFi. I'm running a clean install of the latest version of raspbian lite. Note that lite has no gui, but also has less packages in general, so it

Hello, I've been having trouble with configuring NUT in my home system. First, I have NUT server installed in one raspberry with one UPS connected by USB to it, I followed Techno Tim's tutorial on the matter and it worked perfectly with the web GUI. Then, I have another raspberry pi with two UPS connected by USB that I want to connect to the first so I use just one GUI, but I

I was able to make NUT and my Powercom SPIDER UPS (USB port) work under the Raspberry Pi Desktop (Debian). Everything works in VMware Workstation 15 Player. But my Raspberry Pi 3b + (with raspbian) doesn’t work with the same UPS, and with same NUT configuration. Raspberry sees the UPS, but the driver does not cling. Here is the response of Raspberry 3b + to some commands. pi at raspberrypi:~

I installed the NUT under the latest Ubuntu Mate for Raspberry. The driver immediately earned with my UPS (Powercom SPD-850U). But my happiness was not long. After the first restart of Raspberry, the NUT did not start. It is treated by reconnecting the USB connector. Reconnection has to be performed after each reboot of Raspberry. The USB permissions for the "nut" group and priority

On Mon, Sep 11, 2017 at 10:56:10PM +0000, Guillermo Bisheimer wrote: > Just wanted to mention that I've published a docker image of tinc 1.1pre15 > for the raspberry pi 2/3. > > It was compiled from source on a raspberry 3 and published as > byscontrol/tinc-rpi <https://hub.docker.com/r/byscontrol/tinc-rpi/> along > witht the configuration instructions. > > The

Hi everybody and sorry by the insistence. Nobody has working Tinc Server over a Raspberry in an environment in production? Best regards and sorry again, Ramses De: Ramses II [mailto:ramses.sevilla at gmail.com] Enviado el: martes, 08 de octubre de 2013 17:59 Para: tinc at tinc-vpn.org Asunto: Tinc Server and Raspberry PI (Rev. B). Dear gentlemen, I need configure a VPN

Hey there, to be clear: You've mounted a HFS+ drive on your raspberry pi with rw permissions using fstab. You're able to write files (e.g. as root) on your shares directory without samba, right? As soon as you try to connect Samba using your Mac you haven't any write permissions, right? Have you tried using a Windows machine to connect to your share? Or to disable the Unix

What would be the proper clang (3.2) options to generate ARM for Raspberry pi for LLVM 3.2 with clang 3.2? I realized that "-ccc-host-triple" is no longer valid option in clang. p.s. I googled and found the following which doesn't work with clang 3.2. To cross-compile for Raspberry Pi add flags -ccc-host-triple arm-eabi -marm -mfpu=vfp -mcpu=arm1176jzf-s -mtune=arm1176jzf-s

Christian, I will give 64kbit/s a try and post the figures. My own project is voice only and requires low bitrate so was hoping that it was just the way I was compiling and not an actual regression in speed for SILK. The raspberry PI is quite a cheap and handy reference platform though the ARM side is fairly underpowered but has a great GPU. It also has no audio in which is a pain for playing

Folks I'm not sure this is the right mailing list for the Centos7 port to Raspberry Pi. On the chance that this is the right place... I just booted the Centos Linux 7 for Raspbery Pi 2, but have no idea what the built-in accounts or passwords are. I've tried user: pi password: raspberry and user: root password: password to no avail. Does anyone know? Is there a HOW-TO

On Jan 9, 2024, at 8:19?PM, Claudio Zanetta Penna via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> wrote: > > My problem is that I want to connect a second Raspberry to the first one with NUT server on it, so the information obtained by the second can be sent to the server > and be presented in only one web GUI. > If you are referring to this tutorial:

Cliff, Yes it would be good, but very hard to get a figure for the quality. At 6kbps I assume it does not bother trying to figure what mode to use as at that rate it can only use SILK. When I run some other bitrates it may get a bit slower trying to decide whether it is voice or music. I started with low bit rate because I am only really interested in Voice and very low bit rate. I think there

In R 3.3.2 detectCores() in package parallel reports 2 rather than 1 on Raspberry Pi B+ running Raspbian. (This report is just 'for the record'. The model is superseded and I think no longer produced.) The problem seems to be caused by grep processor /proc/cpuinfo processor : 0 model name : ARMv6-compatible processor rev 7 (v6l) (On Raspberry Pi 2 and 3 there is no error because