From f88cb1f9aaa315dec401bc14dd174f8d5121ed8f Mon Sep 17 00:00:00 2001 From: Shawn Nock Date: Mon, 13 Jan 2020 15:57:38 -0500 Subject: [PATCH] Readme massaging --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index ca19fd8..1c2e4b0 100644 --- a/README.md +++ b/README.md @@ -21,4 +21,4 @@ This code only currently supports mipsel out of the box. The only parts specific - *uboot-feb2019.bin*: Same story. This is the version of u-boot I needed for mt7628 product. You'll almost certainly want to replace this file. Ask your doctor what version of u-boot is right for you - The [ioctl numbers used to ERASE and UNLOCK the mtd](https://git.sr.ht/~monadnock/zig-mtd/tree/master/src/mtd.zig#L8) are arch specific -> zig couldn't grok the nested ioctl #define horrors from the mtd headers. The easiest way I've found to determine these magic numbers is to compile the mtd-magic.c file in the repo with your target toolchain and run it on the target. It'll print out the macro expansions (e.g. `mipsel-openwrt-linux-gcc -o mtd-magic mtd-magic.c`) + zig couldn't grok the nested ioctl #define horrors from the mtd headers. The easiest way I've found to determine these magic numbers is to compile the mtd-magic.c file in the repo with your target toolchain and run it on the target. It'll print out the macro expansions (e.g. `mipsel-openwrt-linux-gcc -o mtd-magic mtd-magic.c`)