Bird|otherbox has quit [Read error: Connection reset by peer]
Bird|otherbox has joined #scopehal
Bird|ghosted has joined #scopehal
Bird|otherbox has quit [Ping timeout: 255 seconds]
Bird|ghosted has quit [Read error: Connection reset by peer]
<GenTooMan>
azonenberg, good fortune on your 2nd child.
<azonenberg>
Lol its the first one
<azonenberg>
i was just refering to fork(2), the syscall
<azonenberg>
Anyway, I've been busy the last few days on various other stuff, and assembling boards from way too long ago
<sorear>
wondering how to metaphorically interpret the fact that there's no NR_fork on linux on arm64 or riscv, only clone
<electronic_eel>
azonenberg: about the ethernet+ssh to uart you asked on twitter. i would not discount a linux based solution because of effort it takes to get it running & updated - when you use a distro that is (nearly) made for this task: openwrt
<electronic_eel>
the main thing is not the hardware, but the support in openwrt. i can click together my config in a kernel config menu interface and have it build a custom image
<monochroma>
is vocore still super expensive?
<electronic_eel>
the vocore is 18$ + shipping
<electronic_eel>
this is not the cheapest solution, but i consider it not freakishly expensive and i really like how easy it is to get it running with the openwrt support
<electronic_eel>
a sochip s3 based solution would be cheaper and faster hardware-wise, but there is no openwrt support. you'd have to build some small distro for it or at least combine parts from other distros. that might not be hard to do, but it still takes time. and when you want to keep your thing up to date, it means building and adapting this several times a year. this adds up. with my openwrt it is just a git fetch + make
<electronic_eel>
so you don't need the "vocore ultimate". that one is really expensive
<monochroma>
electronic_eel: oh dang, i remembered it being in the ~$50 range when it first came out, but that might have been with the 1st party breakout board
<electronic_eel>
yeah, that is the "vocore ultimate" thing i mentioned. that is expensive. i'm talking just about the "core"
<monochroma>
ahh
<monochroma>
hmm was the original based on an atheros SoC?
<monochroma>
don't remember it being mediatek
<monochroma>
errr no
<monochroma>
it was ralink, and then mediatek bought ralink
<monochroma>
yeah, they are just kinda spendy, and large
<electronic_eel>
but the problem i see with this is maintaining the software for this over the years. if i build something for home automation or similar, i want to run it for >5 years. and i want a somewhat current system without tons of known exploits.
<monochroma>
yeah, all tradeoffs
someone--else has joined #scopehal
someone--else has quit [Quit: Connection closed]
someone--else has joined #scopehal
noopwafe1 is now known as noopwafel
Bird|otherbox has joined #scopehal
<azonenberg>
electronic_eel: yeah i am eyeing something for a switch/router management interface here
<azonenberg>
(and possibly scopes too)
<azonenberg>
So i definitely want LTS level lifetime
<electronic_eel>
having some distro that is easy to build & customize and that has proven that it is capable of supporting devices over a longer timespan was the most important point for me
<electronic_eel>
there is also buildroot and yocto, but especially with yocto one device is most times tied to a given kernel version. if the vendor doesn't update it, it stays there for years (and no backports too, until someone does them)
<electronic_eel>
so i went for openwrt and looked at devices that would work well for my usecase
<azonenberg>
i have worked with buildroot based syhstems
<azonenberg>
but never created one from scratch
<electronic_eel>
i don't know how buildroot works in regards to providing support for a device over a longer timespan. if kernels are updated, how kernel patches required for one system are treated and so on.