On Thu, Jan 20, 2011 at 2:33 PM, G, Manjunath Kondaiah <manjugk@xxxxxx> wrote: > On Thu, Jan 20, 2011 at 01:32:24PM +0800, Bob Liu wrote: >> On Wed, Jan 19, 2011 at 7:06 PM, Felipe Balbi <balbi@xxxxxx> wrote: >> > Hi, >> > >> > On Wed, Jan 19, 2011 at 06:57:33PM +0800, Bob Liu wrote: >> >> Any ideas? >> > >> > s/console=ttyS2,115200n8/console=ttyO2,115200n8/ >> > >> > on your CMDLINE. >> > >> >> Yeah, that work! Thanks! >> >> But my system still can't enter shell, I have changed /etc/inittab >> from "tty0::respawn:/sbin/getty -L ttyS2 115200 vt102" to >> "tty0::respawn:/sbin/getty -L ttyO2 115200 vt102", and also have added >> ttyO2 to /etc/securetty. > Looks like file system issue. You can try with below fs: > http://code.google.com/p/beagleboard/downloads/detail?name=ALSA-FS.tar.gz&can=2&q= > Yeah, I also think it's file system issue. I added major and minor number to omap-serial driver, it fix the problem temporary. > No need to edit /etc/inittab with above fs since ttyO2 is mapped to > console device file under /dev Do you know how to do this map during build a fs? Thanks. -- Regards, --Bob -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
