[PATCH 1/2] fdt: correctly handle uncompressed node names

When handling uncompressed node names, we need to compare the last component rather than the entire string. Signed-off-by: Sascha Silbe --- scripts/dtc/libfdt/fdt_ro.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/scripts/dtc/libfdt/fdt_ro.c b/scripts/dtc/libfdt/fdt_ro.c index

[PATCH 2/2] of: fdt: fix unflattening of FDTs containing uncompressed paths

Probably since commit dfbd4c6eff35 ("drivers/of: Split unflatten_dt_node()"), unflattening an FDT containing uncompressed node names (e.g. "/gpio@d4019000/gpio@0") will abort after scanning the root node because fpsize wasn't updated to include the path len. Si

[PATCH 0/2] FDT fixes for running on native Open Firmware

Two fixes for bugs in the FDT code I discovered while trying to get the mainline kernel to run on OLPC XO-1.75. XOs are running Open Firmware natively, not just passing down some blob. Sascha Silbe (2): fdt: correctly handle uncompressed node names of: fdt: fix unflattening of FDTs containing

[PATCH] kbuild: add ARM support for tar-pkg

The fallback code for "unknown" architectures doesn't work on ARM because for ARM (and a couple of other architectures) KBUILD_IMAGE contains only the file name, not the full path. Having an explicit rule also avoids printing the warning for unknown architectures. Signed-off-b

Re: [PATCH] kbuild: add ARM support for tar-pkg

Dear Masahiro (is that right?), Masahiro Yamada writes: > 2017-05-13 20:31 GMT+09:00 Sascha Silbe : >> The fallback code for "unknown" architectures doesn't work on ARM >> because for ARM (and a couple of other architectures) KBUILD_IMAGE >> contains o

[PATCH v2] kbuild: add explicit ARM support for tar-pkg

buildtar warns when an architecture doesn't have an explicit rule on what files to copy, even when the generic rule works just fine. Add a rule for ARM that does the same as the explicit rule, but avoids the warning. Signed-off-by: Sascha Silbe --- v1→v2: rebased on top of todays linus m

[PATCH] USB: ftdi_sio: add GPIO support

ts requires the outputs to be written first) it's left as a potential future enhancement. Serial mode and GPIO mode were tested on FT232RL using a simple loopback setup (TXD connected to RXD). In addition, GPIO output mode was tested on FT245RL (8 channels). Signed-off-by: Sascha Silbe --

Re: [v3,6/9] mm/page_owner: use stackdepot to store stacktrace

FDT in RAM on ARM. Sascha -- Softwareentwicklung Sascha Silbe, Niederhofenstraße 5/1, 71229 Leonberg https://se-silbe.de/ USt-IdNr.: DE281696641 signature.asc Description: PGP signature

Re: [v3,6/9] mm/page_owner: use stackdepot to store stacktrace

[1] http://www.wandboard.org/index.php/details/wandboard [2] https://sascha.silbe.org/tmp/config-4.8.4-wandboard-28-3-g9e9b5d6 -- Softwareentwicklung Sascha Silbe, Niederhofenstraße 5/1, 71229 Leonberg https://se-silbe.de/ USt-IdNr.: DE281696641 signature.asc Description: PGP signature