summaryrefslogtreecommitdiffstats
path: root/documentation/kernel-dev
diff options
context:
space:
mode:
authorHannu Lounento <hannu.lounento@vaisala.com>2023-06-08 14:42:13 +0300
committerSteve Sakoman <steve@sakoman.com>2023-06-21 06:50:52 -1000
commitb9c3b9a2ef6d72ccc3bc57d271f039ada93de826 (patch)
tree093c8af3e3c93d44c81c11ed19ca0e0aacfac1aa /documentation/kernel-dev
parent3597212e5de39aca251d34a7631caf1ece1087ce (diff)
downloadpoky-b9c3b9a2ef6d72ccc3bc57d271f039ada93de826.tar.gz
profile-manual: fix blktrace remote usage instructions
The references to the target and host systems (i.e. the client and server respectively) were swapped in the instructions. Also, there's no need to specify the device node on the server command line that is run on the host system. The previous, incorrect, instructions resulted typically in: target# blktrace -l /dev/mmcblk1 server: waiting for connections... and host$ blktrace -d /dev/mmcblk2 -h target Invalid path /dev/mmcblk2 specified: 2/No such file or directory unless the same device node happened to exist on the host system. Based on target# blktrace --version blktrace version 2.0.0 and host$ blktrace --version blktrace version 2.0.0 (From yocto-docs rev: 3534c2898ce835a08e200f50412561dc782e9021) Signed-off-by: Hannu Lounento <hannu.lounento@vaisala.com> Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Signed-off-by: Steve Sakoman <steve@sakoman.com>
Diffstat (limited to 'documentation/kernel-dev')
0 files changed, 0 insertions, 0 deletions