Devialet Chat

Full Version: Raspberry Pi3 released
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2
This is going to be interesting, especially when Win10 will be supported. With this, I can build a Roon Server with Devialet AIR. Its official case is small and beautiful, too. Big Grin
oooh now thats tantalising

but im guessing that will be reliant on Devialet supporting Win 10 IoT?
I have one on order.
Nick, you're quick. Awaits your implementation and test results.
Only 1 Gb RAM so Win10 IoT for Roon will be constrained - will make a nice end point though.
I hear the Pi3 still has a shared bus for USB/ethernet, which seemed to be the biggest point of concern with the 2 for audio use. Wonder if this will still be a problem?
No they are no longer shared
Wrong.

The Raspberry Pi 3 shares the same SMSC LAN9514 chip as its predecessor, the Raspberry Pi 2, adding 10/100 Ethernet connectivity and four USB channels to the board. As before, the SMSC chip connects to the SoC via a single USB channel, acting as a USB-to-Ethernet adaptor and USB hub.

Source: https://www.raspberrypi.org/magpi/raspbe...enchmarks/
Ah, it was mentioned that Pi3 has no Ethernet but Wifi.

" The addition of this wireless connectivity also reduces the chance of bottlenecking the board. A gripe about earlier models of the Pi is that USB and Ethernet share the same data bus. This shared bus limits the data that can be passed to and from the Pi. Consequently when a user attempts to simultaneously pass large amounts of data over Ethernet and to a USB-attached device, say storage, data transfer rates can bog down.

The Pi 3's wireless LAN doesn't share the USB bus - lessening the constraints on network connectivity."
(01-Mar-2016, 11:27)Hifi_swlon Wrote: [ -> ]I hear the Pi3 still has a shared bus for USB/ethernet, which seemed to be the biggest point of concern with the 2 for audio use. Wonder if this will still be a problem?
What exactly is this concern? I've been using a Pi2 for a few months and haven't noticed any issues. I've seen this alluded to in places but never a proper explanation of what the issue might be for our usage (e.g. endpoint).
Pages: 1 2