4 ms·

This is my understanding - - A powerful alternative to Rpi-Zero/Rpi-pico. - When we don't need wireless i/f, it makes even more sense. - Compared to Rpi-pic

This is my understanding - - A powerful alternative to Rpi-Zero/Rpi-pico. - When we don't need wireless i/f, it makes even more sense. - Compared to Rpi-pico, where we can't run OS, here we can. - Compared to Rpi-zero, Duo has lesser price, hence makes more economic sense. - (Yes, Milk-V Duo does not have a wireless i/f) - Physical LAN needs an i/f board.

coupdejarnac 3y ago
I don't see the point in comparing this to a rpi pico. Totally different niches.
- nl 3y ago
  This is true, but the page itself compares it in the (somewhat weird!) graph comparing clock speed of "vector acceleration" (?)
  - userbinator 3y ago
    I guess they're referring to SIMD.
    - IshKebab 3y ago
      RISC-V has a vector extension. It's a bit different to normal SIMD because the code is agnostic to the data width, kind of like GPU code.
      - Taniwha 3y ago
        Yes, it's SIMD but vector too, more in a Cray sort of way rather than an x86
  - camel-cdr 3y ago
    They have one core that implements rvv 0.7.1, which is the pre ratification spec that doesn't get software support. I managed to get an old toolchain working, but don't expect any code not written by your self to tale advantage of it. That being said, the vector engine is really powerful in my experience. I'm currently working on a benchmarking library, so you might see a post about that in the future.