Ron M
unread,Jan 5, 2012, 11:03:07 AM1/5/12Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Android-x86
Hi all,
Introduction:
I am trying to connect my development host to my target android-x86
device (some Dell Latitude) over serial null-modem cable.
When I set the "console=ttyS0,<AnyBaudRate>" parameters I am able to
see the output of the boot process,
but then I can't type anything into the console when I run Android-x86
in debug mode.
I think that it is because there is no agetty/getty running as in a
standard linux variant ( e.g. initab respawning login on agetty ).
The setup is as follows:
Both serial interfaces are at /ttyS0 - and have the same
characteristics (these are essentially the same computers), as seen in
the output of setserial on both host and Android-x86 target:
PROMPT$ setserial -g /dev/ttyS0
/dev/ttyS0, UART: 16550A, Port: 0x03f8, IRQ: 4
Had I tried to connect serially in a (non-ubuntu...) linux, I would do
something like this:
On the server: agetty -L /dev/ttyS0
On the client: connect to /dev/ttyS0 with screen, minicom, or
whatever.
Now, I can't find a "getty" equivalent on Android-x86-honeycomb,
neither can I find the "login" binary.
I am referring to both having the kernel console redirected, and to
be able to logging via serial on "linux userland" via some agetty
mechanism.
Can anyone help me come up with a way of connecting via the serial
port? I am confident that at least some of you guys connect to your
Android-x86 targets over a serial port on a regular basis.
I appreciate your help.
Ron.