@ekaitz_zarraga@piggo I guess that makes Basque and Finnish somewhat similar. The latter can also sound a bit Japanese at times, and some words are even the same (same pronunciation; different concepts, tho)
Received an email in text/plain without the 70-something line wrapping advised by the corresponding RFC; which is horribly hard to read on a wide screen.
From the subject it looked like I would want to reply anyway. I opened Vim to compose a reply, and the first thing was using “Q” on the quoted part to reflow the original message to read it comfortably.
Remember I mentioned a while ago about using customasm to generate #riscv code? Well, I have put up a repository with most of rv32i and some of rv32m here: https://git.sr.ht/~aperezdc/customasm-riscv
It can only output flat binaries, and I have not yet checked that all possible inputs generate correct code, but it can already be used to assemble simple code.
@ekaitz_zarraga@tuxedocomputers (I have seen many embeddr devices throttle like crazy with the default cooling mechanisms provided, the Raspberry Pi is particularly prone to this and GPU performance suffers a lot; typically replacing the dissipator and/or adding a tiny fan solves the issue completely.)
@ekaitz_zarraga@tuxedocomputers could it be periodic throttling due to overheating? It might be worth checking what temperature is reported by the sensors, or doing the classic “touch the dissipator, see it it hurts” to make sure.
A pressurized bottle of hydrogen in a car is likely to explode, while expanded to fill a giant cigar tends to burn while the airship loses altitude slowly before the fire reaches the gondola.
Amusingly only one third of the people in the Hindenburg died (compare with an airplane accident!) and most of the deceased did not have a way to escape and jump out of their quarters.
Yesterday I found https://github.com/hlorenzi/customasm which seemed like an interesting take on how to write a generic assembler. Then managed to get some basic #riscv instructions encoded correctly (R and I encodings so far) by writing out their definition by hand. While this is nice, it will get boring soon, so an idea could be to use the data at https://github.com/riscv/riscv-opcodes to generate instruction definitions with a script :blobpeek:
The naken_asm assembler (which coincidentally I packaged for Arch Linux a while ago, it's in the AUR) supports #riscv without needing a GNU toolchain, and can cross compile so it will probably be a good option for bare metal programming: http://www.mikekohn.net/micro/hifive1_riscv_asm.php
@ekaitz_zarraga I still haven't decided on what to do, but I know that if I don't start with some bare metal programming from the beginning then I will feel lazy later on. That has happened to me when I got a ln ARM-based PandaBoard some years ago. So it's not sure what, but I want to start from the very bottom this time. And sure, I'll be posting here about whatever I end up doing because I haven't been this excited about a new piece of hardware for more than a decade! :blobaww:
As tempting as it may be to start playing with Linux on the board, I am tempted to make a small bare metal thingy in assembler—I have been reading a bit and the similarities with MIPS (which I know well) make me confident that I might be able to write something like a quick and dirty Forth :blobpeek:
Well, it seems that I may have successfully cleared from customs the #riscv Nezha board ordered from Indiegogo, if it arrives home in the next couple of days I still have some holidays to toy with it.
@ekaitz_zarraga you're welcome! I get the excitement of going from scratch, but having something else where to look for ideas can be handy, too :blobcatcoffee: