All SBCs are useless to me... How am I supposed to encode vp8 in real time with them?
Build a kubernetes cluster out of them and deploy pods which would encode one frame at a time. Then you just need to map-reduce. Easy!
Milk-V Mars: RISC-V credit card size SBC
51–60 of 79 posts
Re: Milk-V Mars: RISC-V credit card size SBC
#52Re: Milk-V Mars: RISC-V credit card size SBC
#53Quite excited by this whole line up, the Pioneer ( https://milkv.io/pioneer ) looks interesting too.
I really hope they can pull this all off. I've ordered a couple of the MlikV-Duos should arrive in the next week or so, let's see how things go!
Re: Milk-V Mars: RISC-V credit card size SBC
#54Re: Milk-V Mars: RISC-V credit card size SBC
#55Earlier quoted context omitted.
> if you ever want to convert your project to something commercial, I would still consider raspberry pi and beaglebone Last time I checked, Broadcom forced you to integrate their compute modules into your product because there was no way they would sell their CPUs alone, no matter how many of them one would be willing to buy. That is not normal in the industrial world. As an example, the Allwinner H3 used in a lot of…
I will just use SOM modules from RPi for products, carrier board is relatively easy to design
Also, depending on your designs, certifications may already be taken care of for WiFi, BT, etc by integrating it on the module.
Re: Milk-V Mars: RISC-V credit card size SBC
#56This is definitely not the first RISC-V SBC at this size (the Sipeed Nezha SBC[0] launched over two years ago based on the Allwinner D1, and the ARIES FIVEBerry[1] launched almost a month ago based on the Renesas RZ/Five). It's not even the first SBC with that specific SoC, as StarFive (the company behind the JH7110 SoC used by this SBC) launched the VisionFive 2 SBC[2] on KickStarter back in September, and Pine64 ha…
If you want to talk about customers actually receiving stuff, rather than announcements or taking preorders, then the timing is:
- Nezha: late June / early July 2021
- VisionFive 2: February 2023
- Star64: May 2023
The PineTab-V also uses the JH7110. It was supposed to ship late May at the same time as the (very similar) A55-based PineTab2, but according to the company they found something they wanted to fix before shipping. Hopefully soon! My VF2 that arrived in February was supposed to have been in November, and the Star64 was scheduled to ship in December, so slips of a few months are just in the nature of the industry, especially at this time.
Re: Milk-V Mars: RISC-V credit card size SBC
#57How does it boot? Or is RISC-V going to follow the same problems as the ARM SBC system where each board has an obscure and unique boot process meaning images need to be carefully pre-built with who knows what installed for each board.
I don't know about interrupts/device tree/etc. but at least for the boot process itself, UEFI/EDK2 was ported to RISC-V. (I actually learned this because I was looking up information about the Windows PE format and was surprised to see relocations support for RISC-V; they needed to add support for it to the PE specification since PE is the native binary format of UEFI!)
UEFI/EDK2 has been demoed with the JH7110 on VisionFive2.
It's not quite complete yet (e.g. lacks drivers for hdmi display and usb), but it boots Linux.
The simpler u-boot SPL --> opensbi --> u-boot flow is mature, and patches have been submitted upstream.
Re: Milk-V Mars: RISC-V credit card size SBC
#58The cores still lack bitmanip/clz/ctz/clmul. :(
AIUI they got Zba and Zbb.
I expect next batch of cores to be full RVA22+V.
Re: Milk-V Mars: RISC-V credit card size SBC
#59The cores still lack bitmanip/clz/ctz/clmul. :(
JH7110 has Zba, Zbb. So not clmul, but yes clz, popcount, etc.