adi

twtxt.net

No description provided.

Recent twts from adi
In-reply-to » "Magic Clock" for Plan 9 (and p9p). http://a.9srv.net/src/img/magicclock-p9p.png http://a.9srv.net/src/magicclock.c (man and other info at http://a.9srv.net/src/).

@Anthony_Sorace@a.9srv.net I’m getting:

magicclock.c:189 function args not checked: drawclock
magicclock.c:234 function args not checked: drawclock

btw, fixed it myself”

⤋ Read More
In-reply-to » "Magic Clock" for Plan 9 (and p9p). http://a.9srv.net/src/img/magicclock-p9p.png http://a.9srv.net/src/magicclock.c (man and other info at http://a.9srv.net/src/).

@Anthony_Sorace@a.9srv.net I have a ton of ideas to implement for Plan 9 but I recently discovered http://www.collyer.net/who/geoff/9/ Geoff’s 9k but still didn’t get it to boot on OpenBSD vmm. For now, main problem is the serial console is not working I think. I’ll have to diff with jmk… I think again.

⤋ Read More
In-reply-to » I'm tinkering with the Plan 9 9k kernel https://github.com/0intro/plan9-contrib/tree/main/sys/src/9k testing if I can boot it on OpenBSD vmm, it's booting but interrupts don't work.

Also, not sure about those lost RAM.

⤋ Read More
In-reply-to » I'm tinkering with the Plan 9 9k kernel https://github.com/0intro/plan9-contrib/tree/main/sys/src/9k testing if I can boot it on OpenBSD vmm, it's booting but interrupts don't work.

Serial console doesn’t work tho.

⤋ Read More

@movq@www.uninformativ.de I’m pretty happy with my naming abilites. I do alot of research before hand tho so that my names fit with the overall naming scheme. dusage is not a bad name to be honest, but we already have du with is short for “disk usage”, if you don’t have a du in OS/2 I think it’s an ok name.

⤋ Read More
In-reply-to » Ok, had some fun porting 9front virtio drivers to 9legacy for OpenBSD vmd:

@movq@www.uninformativ.de https://9front.org/ is a fork of the original https://plan9.io/plan9/. I just ported 9fronts drivers (https://git.9front.org/plan9front/plan9front/1b51d5683a5d8adcde03bbd277e6331f23c2f723/sys/src/9/pc/ethervirtio.c/f.html and https://git.9front.org/plan9front/plan9front/1b51d5683a5d8adcde03bbd277e6331f23c2f723/sys/src/9/pc/sdvirtio.c/f.html) to the original Plan 9. It was almost drop in to be honest. If I were to build one from scratch, there’s this: https://brennan.io/2020/03/22/sos-block-device/, looks digestible.

⤋ Read More
In-reply-to » I just figured out, their domain was just one letter different from another EV charging company domain.

In their defense, they don’t have a web site up at that domain address.

⤋ Read More
In-reply-to » Oh, btw, previous guys I worked with never heard of Go!

@prologic@we.loveprivacy.club They were doing embedded development just like you would JavaScript development, using only “the framework”, as I said: https://github.com/espressif/esp-idf, compile times were super long (20s), the boss asked “How many times do I compile per day?” I said: “constantly….”. Just couldn’t work with the framework, was super slow. Had to develop the driver bare metal and after that integrate it!

⤋ Read More
In-reply-to » @lyse This is what I was using cu for https://github.com/espressif/esp-idf?tab=readme-ov-file#viewing-serial-output

@lyse@lyse.isobeef.org That was for an energy metering driver I made (EV charging stations).

I’m currently working on a VCS for small projects. Single file, plain text repository made entirely of just patches. I’m currently porting to 9Front and all I have is to do add suport for 3 way merging (I think I’ll just use diff3 on Linux and merge3 on OpenBSD for that. Currently it only supports plain text and no binaries.

This an example repo for my dotfiles https://0x0.st/HRnc.diff, view log implementation in awk: https://0x0.st/HRnT.sh

@everybody
If interested, some 💵 would be great as I’ve been out of job for a few months now and they payed like shit when I was working with them.

https://www.paypal.com/donate/?hosted_button_id=7QXC2F3ANCDC2

You could clone that repo with only:

curl https://0x0.st/HRnc.diff | tee v | patch -p0 

However, patch would leave some extra files in the directory.

⤋ Read More
In-reply-to » I remembered cu is next to vi in the "impossible to quit software" list.

You quit cu by pressing ~.. If that doesn’t work, “just hit Enter a couple of times before the combination” (read it on some forum).

⤋ Read More