swetland

14 ms·

1.
by swetland 4mo ago
I create value the same way I always have. Meanwhile people are creating garbage with "ai" tools. I wish them the best of luck with their shit.
2.
by swetland 4mo ago
Fuck off. No, I'm not using it. No, I'm not enjoying it. The only thing performative around here is all you assholes evangelizing this worthless shit.
3.
by swetland 4mo ago
It's useful indicator in these days of useless slop coded shit. Few things are a bigger waste of my time than reading about someone's proudly "ai"-generated pile of garbage.
4.
by swetland 4mo ago
Actually it's quite useful information. As soon as I see another useless "ai coded" project I immediately stop reading/caring about it. Fuck your slop code. Nobody wants that shit.
5.
by swetland 6mo ago
There is no way this utter pile of slop was written by a human.
6.
by swetland 1y ago
Don't suppose there's actually documentation for the CPU anywhere? (I mean more than a tiny "datasheet" with a very high level overview and/or a pile of random Linux/uboot patches)
7.
by swetland 2y ago
Lots of nice improvements here. The RISC-V RV32I option is nice -- so many RV32 MCUs have absurdly tiny amounts of SRAM and very limited peripherals. The Cortex M33s are a biiig upgrade from the M0+s in the RP2040. Real atomic operations.
8.
by swetland 2y ago
They actually let you choose one Cortex-M33 and one RISC-V RV32 as an option (probably not going to be a very common use case) and support atomic instructions from both cores.
9.
by swetland 2y ago
That's the expected clock rate for the TT07 run... but Tiny Tapeout designs only have 8 in, 8 out, and 8 bidirectional IOs (plus a reset and clock input) available, so they're using a multiplexing strategy where the Z80 clock runs
10.
by swetland 2y ago
Yeah, the whole "what could we do with the original CPU and PPU of the NES given much more RAM and game data storage" experiment is pretty neat -- and based on what they've shown so far the results are quite impressive.
11.
by swetland 3y ago
I had moved on from Android by 2013, so I definitely don't have much insight into what it's become over the past decade. In the earlier years it was very much about working hard to build the platform, products, and ecosystem. Th
12.
by swetland 3y ago
The whole "throw everything in the trash and start over" thing is massively overstated. The iPhone announcement absolutely impacted things, not entirely all bad -- there was interest from OEMs before that, but it went through the
13.
by swetland 3y ago
Yeah, I take exception to the painting of Android as inherently "unhealthy" and not "solving real problems for users." Also with lumping it in with the unmitigated disaster that was the Social/G+ effort. I attribut
14.
by swetland 3y ago
Oh I don't even mean the FPGA side (of course that'd be nice), just the SoC's CPU complex and its peripherals! The only "documentation" I've found is a high level block diagram.
15.
by swetland 3y ago
Not finding any documentation for this SoC on either the beagleboard or microchip websites. I'm still waiting for a RISC-V SoC that actually has reasonable documentation instead of a pile of random linux kernel and (maybe) bootloader
16.
by swetland 3y ago
The intent behind the vDSO style interface for syscalls in Fuchsia was primarily to avoid baking specific syscall mechanisms into the ABI, hopefully to allow future changes to the mechanism without breaking binary compatibility -- which was
17.
by swetland 3y ago
Most of that was when the team was pretty tiny. It was fun starting from when the kernel was just beginning to run userspace code. I'm still very happy with how the syscalls turned out. If I did it again, I'd stick with a (smal
18.
by swetland 3y ago
SiFive has pretty good documentation for their cores and chips -- they are more PC/Server class (some lowspeed peripherals plus PCIE and Ethernet) than SoC style. The databook does not have register level docs for PCIE and Ethernet bu
19.
by swetland 3y ago
Okay, so is there actual documentation for the SoC used on this critter? I mean a full Databook / Technical Reference Manual, not maybe 30 pages of overview, maybe a list of register base addresses (if you're lucky), and a pile o
20.
by swetland 3y ago
The place where it breaks down is if you want to build a keyboard that doesn't use a typical collection of contours and widths of keys or a subset thereof. I haven't found a shop that'll do a "nonstandard" collecti
21.
by swetland 3y ago
It's replicating the ZX81 keyboard, including all the quirks except for the horrific membrane keys. https://upload.wikimedia.org/wikipedia/commons/8/8a/Sinclair...
22.
by swetland 3y ago
The ZX80 and ZX81, like a number of 80s personal computers featured a set of graphical characters in addition to standard alphanumeric and punctuation and provided a way to enter then directly from the keyboard. On the Sinclair machines yo
23.
by swetland 3y ago
I've had a lot of fun with this project, but want to be clear that the actual "replicate the ZX81 using discrete 74xx logic (like the ZX80) instead of the ULA chip" PCB design is the work of Mahjongg2 who has shared their wor
24.
by swetland 3y ago
Somewhat amusingly, the keycaps were the most expensive component ($60 plus shipping), second most expensive being the keyswitches. I really wanted something that captured all the information presented by the original keyboard and also fit
25.
by swetland 4y ago
The CPU itself (Core Complex, including cache, irq controller, etc) is documented by SiFive: https://www.sifive.com/cores/u74-mc Unfortunately there appears to be no detailed documentation at all (unless you count a
26.
by swetland 4y ago
It's definitely nicer to have source than a bunch of opaque binaries. (Is there source for the full boot path? Sounds like they have patches for OpenSBI and u-boot -- didn't see if there was source or docs for the on-die boot ro
27.
by swetland 4y ago
Still no sign of an actual Technical Reference Manual or any other detailed documentation on the SoC (registers, peripherals, etc). A big pile of Linux patches, while better than nothing, is a poor substitute for actual documentation. SiFi
28.
by swetland 4y ago
This repo archives a bunch of ncsa httpd releases: https://github.com/TooDumbForAName/ncsa-httpd cgi_src/jj.c exists in 1.1, but not 0.5 (and no versions between those two are in the archive) 0.5 - 6 sep 1993 - h
29.
by swetland 4y ago
The "ISA" mentioned above is the "Industry Standard Architecture", the 8/16bit bus used by PCs and PC clones back in the day, not "Instruction Set Architecture (x86, ARM, RISC-V, etc): https://en.wik
30.
by swetland 5y ago
Using half of zero-page for IO (and then dedicating 1/4 of that to a string printing interface) is a somewhat odd design choice. Most nontrivial 6502 software leans heavily on zero page (since there are very few registers and shorter&#

More ›