141–150 of 232 posts
It would really compete against the RPi if it was on the same price category. Being 15 dollars more expensive breaks the whole purpose of having a descent, small and cheap computer/board as the RPi has been all this time.
Is there a reason why everybody just HAS to stick to the RPi's when the BeagleBone Black/Green/Blue/etc. are: 1) Far more open (you can get documentation and chip supply to build your own BeagleBone) 2) No more expensive 3) Mainline Debian
As open as they are, they still aren't fully open. For me, that means there really isn't any point to them. I'd take a 486 DX4 SoC with no better than VGA output if it was entirely open.
Maybe someone can help: is it possible to build an SBC can boot Linux and has just a CPU, gig ethernet and gobs of RAM (at least 8gb)? Don't need display port, GPU, WiFi, Bluetooth, GPIO pins, etc - just a CPU + lots of RAM + an ethernet port to get stuff in/out.
Are you asking if it's possible, or asking for advice on a practical way to get it done?
Alternatively, is there a practical way to attach external DDRAM to an existing 64-bit SBC, perhaps using the GPIO pins?
I have zero electronics knowledge so forgive my questions if they are stupid.
Earlier quoted context omitted.
Also wired Ethernet. Running a server over WiFi is flaky, especially on a phone optimized for low power usage. The Pi's wired networking is lackluster, but it's still more stable than WiFi. And adding on to GPIO, the Pi has easy to use SPI and i2c busses. That opens up a huge range of sensors and other things like displays that work with easy to understand code. For a lot of use cases it's better to think of the RasP…
Hi, I'm looking to understand the sensors bit. Beyond the fact that the most common sensors/peripherals are built in...I can find a lot of USB sensors that work with Android. In general you can also drop down to NDK (c code) on Android if you want. So I'm still curious on which sensors would not work with a Android phone that people would want to.
How would you stick an Android phone plus a whole octopus of usb peripherals inside a nice neat box? It would be at least shoe box size.
If you need a board that will run 24/7 and control some process, remember Android goes into power management to save battery, and you need to fight it to operate continously. Might not even be possible any more with newer Androids that restrict wake locks.
RPi reliability isn't as good as it could be, at least not without cooling, but I would trust it for long time operation any time over a $30 phone that had to include a screen and a battery in that price and thus has made a lot more compromises.
Earlier quoted context omitted.
H3 was already quite old back when we looked. The support offered by Allwinner for old chips (like the H3) back then was basically "If you're buying a ton, sure we'll support!", which was very off-putting. H5's mainline support is still lacking in key areas. I2C, I2S, and cpufreq are deal-breakers for our product. Of course, combined with the fact that it will soon be out of support for a not-huge-buyer like us, it i…
Sure, none of these chips are new, and the older models (which are easily & cheaply accessible) have mainline support. I wouldn't expect jack from Allwinner besides their crummy kernel 3.4 branch, but that is the beauty in mainline support, you aren't limited to what Allwinner supports!
The then-older chips were not available with the future volume we needed, unless we increased our volumes a few times. We had little choice but to build on their newer chips for the volume bracket we fell into. Perhaps the situation has changed in two years.
> I wouldn't expect jack from Allwinner besides their crummy kernel 3.4 branch, but that is the beauty in mainline support, you aren't limited to what Allwinner supports!
You can see how that is off-putting, especially when other vendors (e.g., the Raspberry Pi Foundation) themselves support the latest LTS (and non-LTS) kernel with maintained patches, and upstream their patches. And their code is not utter garbage. New RPis have a much easier time getting mainlined precisely because of these reasons.
Has anyone of you seen such fan-less board with PCI express slot? I'd like to use it in a mining rig.
Same form factor was very convenient since I could use my old case and hats. ASUS ported WiringPi as well, so all my Rpi scripts worked without modification. And finally, a dedicated Ethernet controller means I get way better speeds than my old Pi 2 could even dream about.
If you care about Ethernet speeds the decision is pretty much a no-brainer.
I was using a Raspberry Pi 2 as my home webserver for a long time but I recently switched to a Tinker Board and was really pleased with the process. Same form factor was very convenient since I could use my old case and hats. ASUS ported WiringPi as well, so all my Rpi scripts worked without modification. And finally, a dedicated Ethernet controller means I get way better speeds than my old Pi 2 could even dream abou…
Earlier quoted context omitted.
Tinker only does 4k30, I need 4k60. I'm currently using a RaspPi for 1080p60, but I am configuring the ROCK64 now. Also, in case you misunderstood, I'm not using a camera with these devices, I am using these devices as a camera. I plug the HDMI out directly into my capture device to test capture/rendering/encoding/etc. Previously, I had to use a real camera and point it at a move to get some nice motion and color. No…
I think you mean to say you are using these devices to simulate a camera?
http://www.lcdracks.com/racks/DLW/V-SG4K-HDI-signal-generato...
https://photos.app.goo.gl/wWTKOLbiXooyYmkA3
I was disappointed to see that the folks at Raspberry are not interested in upping the specs by much. For my workloads I wanted to get more RAM on each node as my processors were not working all that hard.
I've bought ASUS products with confidence for years and I'm glad they have an offering in this space.