vbatts/grub
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

* docs/grub.texi: Correctly use "terminal_input" and not "terminal" in

Browse source 
the example.
This commit is contained in:
Vladimir 'phcoder' Serbinenko 2011-03-30 09:35:35 +02:00
parent 5d8031749e
commit e1ad0edd11
2 changed files with 6 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
ChangeLog
View file

@ -1,3 +1,8 @@
2011-03-30 Vladimir Serbinenko <phcoder@gmail.com>
* docs/grub.texi: Correctly use "terminal_input" and not "terminal" in
the example.
2011-03-30 Vladimir Serbinenko <phcoder@gmail.com> 2011-03-30 Vladimir Serbinenko <phcoder@gmail.com>
* grub-core/term/at_keyboard.c (set_scancodes) * grub-core/term/at_keyboard.c (set_scancodes)

2
docs/grub.texi
View file

@ -1998,7 +1998,7 @@ The commands @command{terminal_input} (@pxref{terminal_input}) and
@command{terminal_output} (@pxref{terminal_output}) choose which type of @command{terminal_output} (@pxref{terminal_output}) choose which type of
terminal you want to use. In the case above, the terminal will be a terminal you want to use. In the case above, the terminal will be a
serial terminal, but you can also pass @code{console} to the command, serial terminal, but you can also pass @code{console} to the command,
as @samp{terminal serial console}. In this case, a terminal in which as @samp{terminal_input serial console}. In this case, a terminal in which
you press any key will be selected as a GRUB terminal. In the example above, you press any key will be selected as a GRUB terminal. In the example above,
note that you need to put both commands on the same command line, as you note that you need to put both commands on the same command line, as you
will lose the ability to type commands on the console after the first will lose the ability to type commands on the console after the first