On Thu, Oct 17, 2019 at 06:52:33PM +0200, Philippe Mathieu-Daudé wrote: > Some firmwares don't parse the <Newline> control character and > expect a <carriage return>. > > Signed-off-by: Philippe Mathieu-Daudé <f4...@amsat.org> > --- > tests/acceptance/boot_linux_console.py | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/tests/acceptance/boot_linux_console.py > b/tests/acceptance/boot_linux_console.py > index 9ff2213874..bf9861296a 100644 > --- a/tests/acceptance/boot_linux_console.py > +++ b/tests/acceptance/boot_linux_console.py > @@ -30,7 +30,7 @@ class BootLinuxConsole(Test): > KERNEL_COMMON_COMMAND_LINE = 'printk.time=0 ' > > def exec_command_and_wait_for_pattern(self, command, success_message): > - command += '\n' > + command += '\r\n'
I'm actually wondering if '\r' alone is really what we should be using
here. Isn't that usually the character that actually pressing the
Enter key generates (on an old school tty)? IIRC it's the thing on
the other side of the console that echoes back a \r and \n in order to
reposition the cursor on the next line.
> self.vm.console_socket.sendall(command.encode())
> wait_for_console_pattern(self, success_message)
>
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
signature.asc
Description: PGP signature
