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.
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.
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.
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.
There is no way this utter pile of slop was written by a human.
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)
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…
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.
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…
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.
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…
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…
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 attribute…
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.
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…
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…
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…
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),…
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" collection of…
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...
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…
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…
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…
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…
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…
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.
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.
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.
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.
There is no way this utter pile of slop was written by a human.
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)
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…
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.
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…
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.
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…
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…
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 attribute…
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.
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…
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…
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…
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),…
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" collection of…
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...
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…
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…
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…
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…
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…