Skip to content

Instantly share code, notes, and snippets.

Avatar

Joshua Harlow harlowja

View GitHub Profile
@harlowja
harlowja / arm64-on-Win10.md
Created Feb 8, 2021 — forked from billti/arm64-on-Win10.md
ARM64 Linux on Win10
View arm64-on-Win10.md

Below are the steps to get an ARM64 version of Ubuntu running in the QEMU emulator on Windows 10.

Install QEMU

Install for Windows from https://qemu.weilnetz.de/w64/ (I used qemu-w64-setup-20181211.exe)

Put C:\Program Files\qemu on your PATH, and run the below to check it's working (which will list out the CPUs the AArch64 emulator can emulate):

qemu-system-aarch64 -M virt -cpu help
@harlowja
harlowja / pr_etiquette.md
Created Nov 9, 2018 — forked from naupaka/pr_etiquette.md
Pull Request Etiquette
View pr_etiquette.md

Pull Request Etiquette

Why do we use a Pull Request workflow?

PRs are a great way of sharing information, and can help us be aware of the changes that are occuring in our codebase. They are also an excellent way of getting peer review on the work that we do, without the cost of working in direct pairs.

Ultimately though, the primary reason we use PRs is to encourage quality in the commits that are made to our code repositories

Done well, the commits (and their attached messages) contained within tell a story to people examining the code at a later date. If we are not careful to ensure the quality of these commits, we silently lose this ability.

@harlowja
harlowja / get_cuda_sm.sh
Created Oct 9, 2018 — forked from eyalroz/get_cuda_sm.sh
Shell script for determining the SM value for your (single) GPU
View get_cuda_sm.sh
#!/bin/bash
#
# Prints the compute capability of the first CUDA device installed
# on the system, or alternatively the device whose index is the
# first command-line argument
device_index=${1:-0}
timestamp=$(date +%s.%N)
gcc_binary=${CMAKE_CXX_COMPILER:-$(which c++)}
cuda_root=${CUDA_DIR:-/usr/local/cuda}