doc: replace example command "interface" with "adapter driver"

Keep documentation consisted after commands renaming.

Change-Id: I97b43887cae9d7c224b07e4ba0b7d04915a19fc4
Signed-off-by: Antonio Borneo <borneo.antonio@gmail.com>
Reviewed-on: http://openocd.zylin.com/5285
Tested-by: jenkins
Reviewed-by: Marc Schink <dev@zapb.de>
Reviewed-by: Oleksij Rempel <linux@rempel-privat.de>
This commit is contained in:
Antonio Borneo 2019-08-23 16:07:12 +02:00 committed by Oleksij Rempel
parent 2aa2ed1d8a
commit 0d598535a3
1 changed files with 4 additions and 4 deletions

View File

@ -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