4 ms·

So this seems to actually be available in China (https://app6hodqg6k9861.h5.xiaoeknow.com/p/decorate/homepage https://app6hodqg6k9861.h5.xiaoeknow.com/p/decorat

by nl 3y ago

So this seems to actually be available in China (https://app6hodqg6k9861.h5.xiaoeknow.com/p/decorate/homepage https://app6hodqg6k9861.h5.xiaoeknow.com/p/decorate/homepage) if not elsewhere. If my conversions are correct, the price (￥35) is more like US$5. There's some documentation (https://milkv.io/docs/duo https://milkv.io/docs/duo). It's a pity there isn't more explanation in some parts. The sales page says "Support Asymmetric multiprocessing" with mention of a RTOS, but unclear what that is exactly. The docs include this: https://milkv.io/docs/duo/resources/mmf https://milkv.io/docs/duo/resources/mmf which appears to be some kind of media co-processor.

happymellon 3y ago
Also, is that mainline Linux or are we going down the hacked kernel route of the ARM boards where someone is going to have to pick through the source to get the patches otherwise it will remain on an ancient unsupported kernel?
- lelanthran 3y ago
  > Also, is that mainline Linux or are we going down the hacked kernel route of the ARM boards where someone is going to have to pick through the source to get the patches otherwise it will remain on an ancient unsupported kernel? My initial impression is that there are no binary blobs[1]. You can look at the repo it is using over here: https://github.com/milk-v/cvitek-linux-5.10 https://github.com/milk-v/cvitek-linux-5.10 I think getting the full sources alone is sufficient. It might not be desirable for the Linux team to accept patches for every standalone piece of hardware. As long as the patches for the actual ISA are mainlined I consider that a win. [1] Maybe there are, I didn't look too closely at the repo, but it looks to me that it's all source code.
  - predictabl3 3y ago
    I own a small mountain of SBCs and I rather disagree. 5.10 is old as-is, and often times the patches aren't submitted upstream due to quality. I've made it a new rule to only buy boards where there is a recent fork of u-boot, and plans to upstream u-boot/linux patches. Life is short and I'm tired of doing work for companies pushing this stuff out. I can't back this up, but I believe mainlining prevents e-waste by keeping boards serviceable and relevant longer.
    - lelanthran 3y ago
      What are you making out of those boards? After all, on an appliance with no internet access, that cannot be updated OTA, how would having updates help? I'm thinking household appliances, factory monitoring, automotive infotainment systems, environmental control, etc. For most embedded stuff, your choices are leave it in the field or recall. For hobbyists, updates are important. For production it only matters if the device is internet connected.
      - viraptor 3y ago
        There's lots of reasons you may need updates anyway. We've seen components which die after an internal counter overflows some amount of days. (Was that SSDs?) Customers will find issues you didn't know about. You'll need to get extra metrics out of remote systems. And many others. Shipping hardware is costly in transport and worker-hours. Being able to update things on site is way better, even if it's "put this on a USB drive, plug in, restart".
      - justinclift 3y ago
        > After all, on an appliance with no internet access ... Just to point out, the sales page for this board says in big letters that it can do 10/100 ethernet with an add-on board.
        lelanthran 3y ago
        > Just to point out, the sales page for this board says in big letters that it can do 10/100 ethernet with an add-on board. So? If we lower the bar to "can do internet with an add-on" then everything can be internet connected, because there's a network addon (interface card/module, i2c, USB) that can be used by almost every single device out there. It's different when a SoC comes with network - that's obviously targeting always-connected devices.
      - ilyt 3y ago
        Ah, the obligatory "WhAt If No InTeRnet" comment that happens every time someone complains software support for board is shit. For one, to not have to keep ancient dev environments around when you need to make small change. Also when you decide to repurpose it for something else, which is far more likely for hobbyist board like this. > For most embedded stuff, your choices are leave it in the field or recall. Sure if you want to get fired. "Sir, you need to pack the $200k worth, 300kg CNC and send it to us so we can upgrade your firmware".
  - rbanffy 3y ago
    > It might not be desirable for the Linux team to accept patches for every standalone piece of hardware. I believe this may warrant an “extended mainline” kernel project that has all those extra modules and that works to consolidate them into the least amount of different variants as possible, all the while providing some continuous hardware testing. It could be maintained in part by the manufacturers themselves who’d need to provide hardware and high quality code at the very least to be able to claim support from this extended mainline. Sounds like my second business idea for the day. I’d love if someone would run with it.
    - londons_explore 3y ago
      > continuous hardware testing I have a non-thinkpad laptop, and it seems nearly every kernel release there is some regression. Touchpad not working.. Then GPU driver not working... Then suspend to disk broken... Regressions that, for a regular non-technical user would be a big headache. I would like to 'lend' hardware to someone to prevent this. I'd happily leave my laptop/desktop/SBC overnight compiling a kernel, rebooting into it, running tests, and hopefully finding regressions before they get into a release. Unfortunately, there doesn't seem to be any project to make this easy. I'd like to just "apt install volunteer-my-hardware-for-overnight-testing". A few thousand people doing that would soon find issues that only affect rare hardware.
      - londons_explore 3y ago
        For this kind of testing, you frequently want a 'watchdog' - which is hardware that can auto-reboot a computer if the software locks up or malfunctions. The way it works is that software 'pets' the watchdog every few minutes, and if the software malfunctions, then it doesn't pet the watchdog, and the system gets hard reset and boots a known good kernel. Unfortunately, while nearly all computer hardware has a watchdog, frequently the linux kernel doesn't implement support for it. That in turn means that testing buggy kernels on real hardware automatically frequently ends up with the hardware getting stuck and a human needs to reset stuff manually.
        3y ago
sberder 3y ago
Taobao has several stores selling it at around 68rmb which is a bit more than $9 at current FX. I'm quite curious about it and just ordered one, should get it in a couple days.

by nl 3y ago

happymellon 3y ago

Also, is that mainline Linux or are we going down the hacked kernel route of the ARM boards where someone is going to have to pick through the source to get the patches otherwise it will remain on an ancient unsupported kernel?

lelanthran 3y ago
> Also, is that mainline Linux or are we going down the hacked kernel route of the ARM boards where someone is going to have to pick through the source to get the patches otherwise it will remain on an ancient unsupported kernel? My initial impression is that there are no binary blobs[1]. You can look at the repo it is using over here: https://github.com/milk-v/cvitek-linux-5.10 https://github.com/milk-v/cvitek-linux-5.10 I think getting the full sources alone is sufficient. It might not be desirable for the Linux team to accept patches for every standalone piece of hardware. As long as the patches for the actual ISA are mainlined I consider that a win. [1] Maybe there are, I didn't look too closely at the repo, but it looks to me that it's all source code.
- predictabl3 3y ago
  I own a small mountain of SBCs and I rather disagree. 5.10 is old as-is, and often times the patches aren't submitted upstream due to quality. I've made it a new rule to only buy boards where there is a recent fork of u-boot, and plans to upstream u-boot/linux patches. Life is short and I'm tired of doing work for companies pushing this stuff out. I can't back this up, but I believe mainlining prevents e-waste by keeping boards serviceable and relevant longer.
  - lelanthran 3y ago
    What are you making out of those boards? After all, on an appliance with no internet access, that cannot be updated OTA, how would having updates help? I'm thinking household appliances, factory monitoring, automotive infotainment systems, environmental control, etc. For most embedded stuff, your choices are leave it in the field or recall. For hobbyists, updates are important. For production it only matters if the device is internet connected.
    - viraptor 3y ago
      There's lots of reasons you may need updates anyway. We've seen components which die after an internal counter overflows some amount of days. (Was that SSDs?) Customers will find issues you didn't know about. You'll need to get extra metrics out of remote systems. And many others. Shipping hardware is costly in transport and worker-hours. Being able to update things on site is way better, even if it's "put this on a USB drive, plug in, restart".
    - justinclift 3y ago
      > After all, on an appliance with no internet access ... Just to point out, the sales page for this board says in big letters that it can do 10/100 ethernet with an add-on board.
      - lelanthran 3y ago
        > Just to point out, the sales page for this board says in big letters that it can do 10/100 ethernet with an add-on board. So? If we lower the bar to "can do internet with an add-on" then everything can be internet connected, because there's a network addon (interface card/module, i2c, USB) that can be used by almost every single device out there. It's different when a SoC comes with network - that's obviously targeting always-connected devices.
    - ilyt 3y ago
      Ah, the obligatory "WhAt If No InTeRnet" comment that happens every time someone complains software support for board is shit. For one, to not have to keep ancient dev environments around when you need to make small change. Also when you decide to repurpose it for something else, which is far more likely for hobbyist board like this. > For most embedded stuff, your choices are leave it in the field or recall. Sure if you want to get fired. "Sir, you need to pack the $200k worth, 300kg CNC and send it to us so we can upgrade your firmware".
- rbanffy 3y ago
  > It might not be desirable for the Linux team to accept patches for every standalone piece of hardware. I believe this may warrant an “extended mainline” kernel project that has all those extra modules and that works to consolidate them into the least amount of different variants as possible, all the while providing some continuous hardware testing. It could be maintained in part by the manufacturers themselves who’d need to provide hardware and high quality code at the very least to be able to claim support from this extended mainline. Sounds like my second business idea for the day. I’d love if someone would run with it.
  - londons_explore 3y ago
    > continuous hardware testing I have a non-thinkpad laptop, and it seems nearly every kernel release there is some regression. Touchpad not working.. Then GPU driver not working... Then suspend to disk broken... Regressions that, for a regular non-technical user would be a big headache. I would like to 'lend' hardware to someone to prevent this. I'd happily leave my laptop/desktop/SBC overnight compiling a kernel, rebooting into it, running tests, and hopefully finding regressions before they get into a release. Unfortunately, there doesn't seem to be any project to make this easy. I'd like to just "apt install volunteer-my-hardware-for-overnight-testing". A few thousand people doing that would soon find issues that only affect rare hardware.
    - londons_explore 3y ago
      For this kind of testing, you frequently want a 'watchdog' - which is hardware that can auto-reboot a computer if the software locks up or malfunctions. The way it works is that software 'pets' the watchdog every few minutes, and if the software malfunctions, then it doesn't pet the watchdog, and the system gets hard reset and boots a known good kernel. Unfortunately, while nearly all computer hardware has a watchdog, frequently the linux kernel doesn't implement support for it. That in turn means that testing buggy kernels on real hardware automatically frequently ends up with the hardware getting stuck and a human needs to reset stuff manually.
      - 3y ago

sberder 3y ago

Taobao has several stores selling it at around 68rmb which is a bit more than $9 at current FX. I'm quite curious about it and just ordered one, should get it in a couple days.