From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Fri, 13 Jul 2012 23:03:04 +0200 Subject: [Buildroot] /dev/ttyS0 in filesystem created by Buildroot can't be opened in Qemu In-Reply-To: References: <20120709084152.GJ22116@sapphire.tkos.co.il> <20120709161602.GG3783@tarshish> <20120710102910.GA4206@sapphire.tkos.co.il> <20120710144610.2d5599aa@skate> <20120710125411.GC4206@sapphire.tkos.co.il> Message-ID: <20120713230304.4576d10a@skate> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Le Tue, 10 Jul 2012 17:13:16 +0200, Mihajlo Jovanovi? a ?crit : > However, just for testing purposes, I have launched qemu with > "console=tty1" and then I got correct output in terminal window, whereas in > Qemu window there was Tux and outputs were finished with "Starting > network...". Probably the reason for that is discrepancy between specifying > "tty1" in Qemu invocation, and at the same time selecting "ttyAMA0" in > menuconfig You're confusing two different things: (1) The console=ttyXX kernel parameter. This tells the kernel were to output its messages, i.e all the messages displayed by kernel drivers and subsystems. (2) The ttyXX on which the getty program is run. getty is the userspace program that implements the login prompt. In Buildroot, it is started directly by Busybox init, as specified in the /etc/inittab file. The option in System configuration -> Port to run getty on adjust this tty. Best regards, Thomas -- Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com