Profile cover photo
Profile photo
Riku Voipio
543 followers
543 followers
About
Riku's posts

Post has attachment
curl | sudo bash
This problem is totally misunderstood. Let's illustrate:

debian.org | asshat.hacks
curl | sudo bash | safe | unsafe
curl deb; sudo dpkg -i deb | safe | unsafe
...

Post has attachment
20 years of being a debian maintainer
fte (0.44-1) unstable; urgency=low

* initial Release.

-- Riku Voipio Wed, 25 Dec 1996 20:41:34 +0200 Welp I seem to have spent holidays of 1996 doing my first Debian package. The process of getting a package into Debian was quite straightforward then. ...

Post has shared content
QEMU Advent Calendar is back! Play with operating systems, neat code demos, and emulation goodness this December. Each day a new ready-to-go disk image is released for your enjoyment. Day 1 is today!

Thanks to Thomas Huth and Kashyap Chamarthy for running QEMU Advent Calendar this year.

Post has attachment
Legacy architecture emulation coming to windows for arm64

Post has shared content
ARMv8.3-A announced. Major features:

- Pointer authentication to mitigate against ROP and JOP attacks (AArch64 only)

- Nested virtualization, allowing guest hypervisors in theory with unlimited nesting, though in practice a hypervisor running transparently at EL1 is more likely (AArch64 only)

- Advanced SIMD floating-point complex number support (AArch64 and AArch32)

Post has shared content
I just added Device Tree support to the Grub bootloader for x86 / x86_64 [1] largely based on work already done by Linaro for ARM.

There is plenty of information on the web describing what Device Tree is [2][3], but in short, it's a way of describing what hardware is attached to a given machine via a non-discoverable bus. This type of hardware used to require platform data, a platform driver, and a board-specific file in arch/ within the Linux kernel. In an effort to simplify the Linux kernel source tree, kernel maintainers opted to use Device Tree to platform-specific information out of the kernel and into firmware. A given Device Tree description is compiled from a human readable format to a Device Tree Blob (DTB), a.k.a. Flattened Device Tree (FDT) using dtc[4].

With respect to how the DTB (or FDT) is passed from bootloader to kernel, that on ARM the pointer is passed in R2, whereas on x86, it's passed in boot_params.setup_header.setup_data.

Of course, the kernel must be built with CONFIG_OF to actually use the Device Tree that was passed in.

[1] https://github.com/cfriedt/grub/tree/feature/devicetree-x86
[2] http://www.devicetree.org
[3] https://events.linuxfoundation.org/sites/events/files/slides/petazzoni-device-tree-dummies.pdf
[4] https://git.kernel.org/cgit/utils/dtc/dtc.git

Photo

Post has shared content

Post has attachment
Samsung could just remove the case, remove battery, and sell the guts as an exynos 8890 SBC with 4GB of ram and LTE connectivity. If samsung won't do that, someone needs to pretend to be an korean e-waste dealer and provide samsung the cheapest disposal contract ;)

Post has attachment
Photo

Post has attachment
When in America, drink like Americans. Recommended by +Koen Kooi​
Photo
Wait while more posts are being loaded