a conference committee wanted to know my telegram nick so...

... Finland making to the EBU finals ;-)

gym week #3

I don't usually put my own pics to social media but here's one that I randomly found from my girlfriends daughters 12th birthday (about year ago). I also take kids birthdays like a pro :-------)

EDIT: i do put a lot of pics of cool hardware tho...

The killa feature, GPU rendered GUI:

I think this is the most time-standing IT book that I own. It was published in 1999 and I still check it from time to time.

E.g. when collaborating with hpa on arch/x86/realmode, this book was my main reference in addition to ELF specification.

It is also as prose very nice reading with cool stories embedded!

@GrantMeStrength finnish advert

gotta love #tiktok

@oherrala ? :-)

#ChatGPT delivered me value for the first time ever :-) Asked what is the best 1000 W PSU on a budget.

still the most popular song

@ikkeT @timojyrinki @vathpela @viznut @vwbusguy

Most of the issues have been in Finnish but there's been couple of internal editions over the years too...

finally #fallout

@vathpela @vwbusguy commodore power!

The only wiring I have in it for serial TTY access:

Super-nice additional benefit of this shield: one cable less. Before I needed power cable and USB-TTL for TTY. Now only by connecting micro-USB to the shield it draws the power and provides serial access.

The screenshot has unmodified #BuildRoot master branch version built with visionfive2_defconfig. Seems to be much more stable than lean, at least for the kernel development, than the official SDK, which is quite scary looking construction tbh :-)

Also got this display, right now it is connected to a 7th gen NUC that use to test all x86 patches (because it has full sgx2 support). Display cost less than 50 euros and it is super handy for kernel testing.

No more fighting with a loose TTL-USB-cables: I have USB hub shield with USB-to-UART port :-) Or two of these: one for Raspberry Pi 3B+ and other for VisionFive 2 RISC-V SBC (in the pic). Need to still pile a TPM2 chip to the pins on top of the shield and hopefully it will still work. #arm #riscv #visionfive2 #raspberrypi

After couple of hours poking around I now know how to embed #typst markup from yaml to a typst document :-)

I’m working on resume made with typst (as I’m looking to find a new job by end of September), and in that I’m using #yaml file to separate presentation from the content. Job descriptions can involve links, and thus those entries need to be evaluated.

First observation was:

#eval(job.description, mode: "markup")

If mode-parameter is not defined, typst will try to parse the string as an expression (i.e. mode: "code" is the efault, which is feasible in this case.

Another problem was the use of the hash character for tags, which is used for comments in yaml.

I sorted that out by putting every description into double quotes after trying a few different approaches:

    description:
      "I first worked on Keystone Security Monitor for RISC-V by enabling it
      for CVA6 running on FPGA. This work was part of the EU funded
      #link(\"https://www.spirs-project.eu/\")[SPIRS project].
      It involved
      tuning the
      #link(\"https://buildroot.org/\")[BuildRoot]
      based embedded stack, and
      fixing various
      #link(\"https://github.com/keystone-enclave/keystone/issues/378\")[issues].
      in the OpenSBI firmware.
      For the second half of my contract I'm enabling Linux for the new SoC's
      developed by
      #link(\"https://sochub.fi/\")[SocHub project]."

The screenshot shows the end result.

Nothing too complicated but took some time to find working patterns so putting here as a #note for myself :-)