runqemu-internal: add "console=ttyS0" to ramfs image kernel parameters

The following changes since commit e273301efa0037a13c3a60b4414140364d9c9873:

gstreamer/lame: Better gcc 4.9 fix (2014-05-15 23:27:41 +0100)

are available in the git repository at:

git://git.openembedded.org/openembedded-core-contrib ChenQi/runqemu-ramfs
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=ChenQi/runqemu-ramfs

Chen Qi (1):
runqemu-internal: add "console=ttyS0" to ramfs image kernel
parameters

 scripts/runqemu-internal |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

1.7.9.5

We need this kernel command parameter so that when we start a ramfs image, we can actually get some output. Although we can make this happen by specifying the 'bootparams' for the 'runqemu' command, it's better to make this the default behaviour.

---
 scripts/runqemu-internal |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

index d317dfd..38745dd 100755
@@ -550,7 +550,7 @@ fi
 
 if [ "x$RAMFS" = "xtrue" ]; then
     QEMUOPTIONS="-initrd $ROOTFS -nographic"
-    KERNCMDLINE="root=/dev/ram0 debugshell"
+    KERNCMDLINE="root=/dev/ram0 console=ttyS0 debugshell"
 fi
 
 if [ "x$ISOFS" = "xtrue" ]; then

1.7.9.5

is this valid for all kind of qemu machines ?

I think so.
Notice in runqemu scripts, if '-nographic' is supplied to the qemu command, then 'console=ttyS0' is supplied to the '-append' option. This is the behaviour for the 'nographic' parameter for the 'runqemu' command. The exception is the case of starting a ramfs image. And this patch fixes this.

Thanks,
Chen Qi