From 0d598535a30ea553f5a5d4a0047010807fcc5996 Mon Sep 17 00:00:00 2001 From: Antonio Borneo Date: Fri, 23 Aug 2019 16:07:12 +0200 Subject: [PATCH] doc: replace example command "interface" with "adapter driver" Keep documentation consisted after commands renaming. Change-Id: I97b43887cae9d7c224b07e4ba0b7d04915a19fc4 Signed-off-by: Antonio Borneo Reviewed-on: http://openocd.zylin.com/5285 Tested-by: jenkins Reviewed-by: Marc Schink Reviewed-by: Oleksij Rempel --- doc/openocd.texi | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/openocd.texi b/doc/openocd.texi index b203656fca..1c89d8c0b1 100644 --- a/doc/openocd.texi +++ b/doc/openocd.texi @@ -2338,7 +2338,7 @@ A few cases are so simple that you only need to say what driver to use: @example # jlink interface -interface jlink +adapter driver jlink @end example Most adapters need a bit more configuration than that. @@ -2719,7 +2719,7 @@ For example, to connect remotely via TCP to the host foobar you might have something like: @example -interface remote_bitbang +adapter driver remote_bitbang remote_bitbang_port 3335 remote_bitbang_host foobar @end example @@ -2728,7 +2728,7 @@ To connect to another process running locally via UNIX sockets with socket named mysocket: @example -interface remote_bitbang +adapter driver remote_bitbang remote_bitbang_port 0 remote_bitbang_host mysocket @end example @@ -3036,7 +3036,7 @@ For example, the interface configuration file for a classic ``Wiggler'' cable on LPT2 might look something like this: @example -interface parport +adapter driver parport parport_port 0x278 parport_cable wiggler @end example -- 2.30.2