sfx2000

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...

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.

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.

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...

Running Ubuntu 20.04LTS on UTM on Macbook Air M1... https://mac.getutm.app/

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.

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

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...

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...

Shortcut perhaps... but this does override systemd assigning things there... Add the following line to /boot/armbianEnv.txt extraargs=net.ifnames=0 and then reboot... sfx

Indeed - and they both get along, and want to do a threesome.... It's so very wrong and right on many levels, LOL, and rarely ends well That being said - Microsoft is a very different company that it was under Gates/Ballmer with Windows/Office at all costs... WSL on Win10 for example, as well at the beast that is Azure... Embrace/Extend/Overcome? Who knows... sfx

Nice to see VS Code in the repo's - it's my goto editor these days on Mac/Win/Linux.. On lower end ARM's - it's a bit slow and memory intense, but it does run... The RPI folks recently added it to their debian based distro in the last couple of weeks...

ZFS support is nice to have - one can use EXT4 for the boot volume, and ZFS for attached drives as a storage pool... That being said, ZFS can, and often does, use more memory...

u-boot and device tree optimizing works wonders here - need to declare the interfaces before the kernel boots, otherwise it's going to grab the first one ready...

"best" is subjective - yes zsh is nice, and now the default shell even on MacOS BigSur. I'm a bit old-school - bash is good enough for me, I know it's quirks, and zsh (or others) is always an option post first-boot. On my other efforts - I'm still dealing with busybox (and that is ash.c)...