Add hint to how you can start to figure out what protocol a remote uses. Signed-off-by: Sean Young <sean@xxxxxxxx> --- utils/ir-ctl/ir-ctl.1.in | 3 +++ utils/keytable/ir-keytable.1.in | 9 +++++++++ 2 files changed, 12 insertions(+) diff --git a/utils/ir-ctl/ir-ctl.1.in b/utils/ir-ctl/ir-ctl.1.in index 226bf606..f6192dab 100644 --- a/utils/ir-ctl/ir-ctl.1.in +++ b/utils/ir-ctl/ir-ctl.1.in @@ -233,3 +233,6 @@ License GPLv2: GNU GPL version 2 <http://gnu.org/licenses/gpl.html>. .br This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. +.SH SEE ALSO +To display decoded IR, or set IR decoding options, use +ir\-keytable(1). diff --git a/utils/keytable/ir-keytable.1.in b/utils/keytable/ir-keytable.1.in index c8ff722e..e7fd7760 100644 --- a/utils/keytable/ir-keytable.1.in +++ b/utils/keytable/ir-keytable.1.in @@ -118,6 +118,13 @@ To read the current keytable, on the second remote controller: To enable NEC protocol and load a BPF protocol, with a parameter for the BPF protocol: .br \fBir\-keytable \-p nec,pulse_distance \-e pulse_header=9000 +.PP +If you do not know what protocol a remote uses, it can be helpful to first +try with all kernel decoders enabled. The decoded protocol and scancodes +will be displayed in the output: +.br + \fBir\-keytable \-c \-p all \-t\fR + .SH BUGS Report bugs to \fBLinux Media Mailing List <linux-media@xxxxxxxxxxxxxxx>\fR .SH COPYRIGHT @@ -127,3 +134,5 @@ License GPLv2: GNU GPL version 2 <http://gnu.org/licenses/gpl.html>. .br This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. +.SH SEE ALSO +To transmit IR or receive raw IR, use ir\-ctl(1). -- 2.20.1
