Jump to content


  • Posts

  • Joined

  • Last visited

1 Follower

Recent Profile Visitors

5289 profile views
  1. Converting Chrome devices over - each one is a bit different, and each one takes perhaps more skill on the user to get there... Here's the Alpine link... https://wiki.alpinelinux.org/wiki/Alpine_on_the_Aopen_Chromebase_or_Chromebox_Mini_with_Mainline_Kernel
  2. Picked up a couple of these over at the local second hand store... https://www.aopen.com/AU_en/products_info/Chromebox-Mini My guess is that these were digital signage oriented, as they were in a crate with a few Startech USB-DVI adatpers, etc... Anyways - they're end-of-support for ChromeOS... There's a couple of posts over on Alpine to get things running there... It's close enough to TinkerBoard to maybe do some effort, and with Chromeboxes/Chromebooks on the same SoC/BSP...
  3. Grabbed the latest Jammy download for NanoPi Neo 2 - https://redirect.armbian.com/nanopineo2/Jammy_current Have to ask - why servers preinstalled and default configured? I found NFS/rpcbind and OpenVPN preinstalled on the image - this is a security risk that can be easily avoided.
  4. cloud is preferred - that being said, if it is sensitive, or even classified, data, this is the wrong forum to be in. We're not the ones to comment on any approach here - most companies and organizations have strong policy guidance as to how their data is handled.
  5. Seems like nobody has responded... Yes, a Macbook Air M1 is a nice machine and works well with iOS via iCloud.
  6. Something to consider for your CI/CD pipeline... https://www.servethehome.com/oracle-cloud-giving-away-ampere-arm-a1-instances-always-free/ There is always AWS, but that ain't free...
  7. Just noticed how small the M1 MacMini mainboard is... I'm surprised it even has a fan, they could have done a heat pipe to the housing, and that likely would have been "good enough" - that's the nice thing about my MBAir-M1, no fans, it's dead silent.
  8. Part of the challenges working with folks like STM is getting ahold of the right folks that can actually help without needing NDA's and all that... They already have a debian buster image available, so with the right setup on the host side, pretty much it's a done project. I just wrapped up something similar for embedded on a Microchip SAMA5D series SoC, not looking to pull in something else for the moment.
  9. Runs well enough - it's all native, but QEMU is suggesting it's a Cortex-A72 It's a stock ISO from Ubuntu, so it's whatever kernel they're shipping with...
  10. Running Ubuntu 20.04LTS on UTM on Macbook Air M1... https://mac.getutm.app/
  11. Exactly - MV3720 running in 64-bit is fairly impressive all told, which is why I kind of mentioned that one might be better off rather than using CESA on that chip. Armada 38X and XP, it's the other way around, where CESA is much better than running on cores - benefit of those chips being focused on networking/communications processing as opposed to application focused.. Depending on needs of course - the main benefit of running CESA is the offload from the cores so they are available for other tasks.
  12. Was kind of seeing if anyone would mention things, since the processor has been out for better part of a year now... Asahi team is making good progress at bringing up the kernel at a board level, so one could probably bring debain into userland with not much effort. Homebrew folks have made the port over from x86_64 to arm64 recently, so toolchain support should be a bit better. Looking below - nice finegrained clocks for CPU/GPU on the chip - note that the cores are individually clocked... Will be nice to see what newer ARM cores bring to the table - looking forward to Cortex-A78 sfx
  13. Armada 38x is fairly decent with CESA in specific use cases - and it's worth the effort perhaps to get it up and running (armbian, if I recall, doesn't enable it by default) MV3720 is a different chip - and there, it's better to skip the CESA units, and go with software on the cores, IMHO...
  14. Atheros 9331 can do this all day long on 100-Base-T... 400MHz MIPS32 [SUM] 0.00-10.00 sec 102 MBytes 85.5 Mbits/sec sender [SUM] 0.00-10.00 sec 101 MBytes 84.4 Mbits/sec receiver 64MB RAM/16MB SPI-NOR - running OpenWRT If you need a bit more horsepower to route traffic - MV3720 on Gigabit can do wire speed there... Alternate for 1GB - QCA IPQ-40xx - I've got a IPQ-4019 board running QSDK (based on an older OpenWRT with QCA special sauce), and it can route actually better than the MV3720 - and that's a QuadCore Cortex-A7... Key thing here - AR9331/MV3720/IPQ4019 - these are all communications focused devices, not application processors/boards...
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines