Val Packett valpackett

Foreward

This document was originally written several years ago. At the time I was working as an execution core verification engineer at Arm. The following points are coloured heavily by working in and around the execution cores of various processors. Apply a pinch of salt; points contain varying degrees of opinion.

It is still my opinion that RISC-V could be much better designed; though I will also say that if I was building a 32 or 64-bit CPU today I'd likely implement the architecture to benefit from the existing tooling.

Mostly based upon the RISC-V ISA spec v2.0. Some updates have been made for v2.2

Original Foreword: Some Opinion

The RISC-V ISA has pursued minimalism to a fault. There is a large emphasis on minimizing instruction count, normalizing encoding, etc. This pursuit of minimalism has resulted in false orthogonalities (such as reusing the same instruction for branches, calls and returns) and a requirement for superfluous instructions which impacts code density both in terms of size and

Porting coreboot to a Haswell / Lynx Point laptop: GIGABYTE P34G v2

This was sold by Schenker XMG as C404, while the original model name by GIGABYTE is P34G v2.

The board schematics are not publicly available. However, from another laptop board's schematics, we can learn a bit about the components it should have:

autoport

Running Windows software on the Raspberry Pi (and other ARM devices) with Wine

Speedrunning FAQ/Glossary

by 0xabad1dea September 2018

You may notice a decidedly Nintendo bias to the examples. I can't change who I am.

What is Speedrunning?

Speedrunning is:

Completing a video game

	{-# LANGUAGE DataKinds #-}
	{-# LANGUAGE PolyKinds #-}
	{-# LANGUAGE TypeOperators #-}
	{-# LANGUAGE UndecidableInstances #-}
	{-# LANGUAGE UnsaturatedTypeFamilies #-}

	import GHC.TypeLits
	import Prelude hiding (Functor, Semigroup)

	type Main = (Fizz <> Buzz) <$> (0 `To` 100)

	#!/bin/bash

	# This script is based on https://unix.stackexchange.com/revisions/480191/9 .
	# The following changes proved to be necessary to make it work on CentOS 7:
	# * removed disk info (model, size) - not very useful, might not work in many cases.
	# * using "bw" instead of "bw_bytes" to support fio version 3.1 (those availible through yum @base)
	# * escaping exclamation mark in sed command
	# * the ".fiomark.txt" is not auto-removed

	LOOPS=5 #How many times to run each test

	pragma solidity =0.4.25;

	contract AcoraidaMonicaGame{
	uint256 public version = 4;
	string public description = "Acoraida Monica admires smart guys, she'd like to pay 10000ETH to the one who could answer her question. Would it be you?";
	string public constant sampleQuestion = "Who is Acoraida Monica?";
	string public constant sampleAnswer = "$!&#^[` [email protected];Ta&T` R`<`~5Z`^5V You beat me! :D";
	Logger public constant logger=Logger(0x5e351bd4247f0526359fb22078ba725a192872f3);
	address questioner;
	string public question;

	oot from normal
	mt_pll_init +
	CLK_GATING_CTRL1:d891923e
	after set, CLK_GATING_CTRL1:d891923e
	CLK_GATING_CTRL2:7afdbf10
	[PWRAP] pmic ID: 2092.
	[EMI] MDL number = 0

	[EMI] PCDDR3

	;
	; the "monitor ROM" of an apple 1 fit in one page (256 bytes).
	;
	; this is my attempt to take the disassembled code, give names to the
	; variables and routines, and try to document how it worked.
	;
	;
	; an apple 1 had 8KB of RAM (more, if you hacked on the motherboard), and a
	; peripheral chip that drove the keyboard and video. the video was run by a
	; side processor that could treat the display as an append-only terminal that

	default['sshd']['sshd_config']['AuthenticationMethods'] = 'publickey,keyboard-interactive:pam'
	default['sshd']['sshd_config']['ChallengeResponseAuthentication'] = 'yes'
	default['sshd']['sshd_config']['PasswordAuthentication'] = 'no'