From 619a2a82043f49ce71b233800ec9d36e6c93efe0 Mon Sep 17 00:00:00 2001 From: Dmitry Vyukov Date: Fri, 16 Jun 2017 13:14:39 +0200 Subject: docs: say that Suzy-Q is not necessary --- docs/setup_linux-host_android-device_arm64-kernel.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/setup_linux-host_android-device_arm64-kernel.md') diff --git a/docs/setup_linux-host_android-device_arm64-kernel.md b/docs/setup_linux-host_android-device_arm64-kernel.md index e7ba1788c..e3ff3c094 100644 --- a/docs/setup_linux-host_android-device_arm64-kernel.md +++ b/docs/setup_linux-host_android-device_arm64-kernel.md @@ -3,7 +3,7 @@ Prerequisites: - go1.8+ toolchain (can be downloaded from [here](https://golang.org/dl/)) - Android NDK (tested with r12b) (can be downloaded from [here](https://developer.android.com/ndk/downloads/index.html)) - - [Suzy-Q](https://chromium.googlesource.com/chromiumos/platform/ec/+/master/docs/case_closed_debugging.md) device to capture console output (support for other development boards is possible, but it not implemented yet) + - Android Serial Cable or [Suzy-Q](https://chromium.googlesource.com/chromiumos/platform/ec/+/master/docs/case_closed_debugging.md) device to capture console output is preferable but optional. syzkaller can work with normal USB cable as well, but that can be somewhat unreliable and turn lots of crashes into "lost connection to test machine" crashes with no additional info. From `syzkaller` checkout: - Build `syz-manager` for host: -- cgit mrf-deployment