"Young, Joseph" <[email protected]> writes: > I am porting the Davinci Linux kernel to a new and similar TI device, called > Jacinto2. I am at the point where the init program passed to the kernel by the > bootloader is initialized. The problem that I am experiencing is that, > whichever init program I pass, it can display text, but it cannot receive > characters from the keyboard. > > I know the serial interface is ok, because I inserted prinktk's and it both > issues a serial interrupt when I press any key, as well as retrieves the > correct character from the UART buffer. However, the characters I type do not > show up in the shell, and it doesn't seem to react to keyboard signals. > > When one passes /bin/sh as the init program, it will display the '# /' of the > shell prompt, but the keyboard has no effect. When I wrote a simple 'hello > world' program to print text, receive text from the user, and then print > another line, it will print but not receive the keystrokes. > > Passing /bin/ls (which redirects to busybox) will display my file system as I > expect, so I don't think that my busybox is broken. > > Is anyone familiar with how this is initialized when the kernel is booting? > Does anyone have a clue what I could be missing so that the serial interface > would record keystrokes but not pass it to the tty interface or shell?
Not sure about the details of Jacinto2, but on the other SoCs in the family, the UART TX and RX signals are commonly mux'd with other pins. Have you confirmed that all the UART signals are mux'd correctly? Kevin _______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
