Hi all: I am running Android Ecalir on Devkit8000 board OMAP3530. The kernel I used was git from 0xdroid branch omap3-2.6.32.
My goal is getting higher UART baud rate(3M). I found the patch “serial: Add OMAP high-speed UART driver”. http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=commitdiff;h=b612633b5928077441b979471869753bfa93d41a I followed the patch to add the 2.6.37 omap-serial driver (omap- serial.c, omap-serial.h,etc.) to 2.6.32 kernel. Because 2.6.32 serial.c doesn’t mention about “CONFIG _SERIAL_OMAP”, so I also replaced it with 2.6.37 serial.c. Problem: I can’t use UART1 and UART3 to communicate with PC now. Even the bootargs is “console=ttyS2,115200n8” or “console=ttyO2,115200n8”, there is no boot information on console. ===================================================================== The message stopped at : Starting kernel ... Uncompressing Linux............................................................................................................................................................................... done, booting the kernel. ===================================================================== After booting, it can enter android filesystem successfully. There is /dev/ttyS*, but there is no /dev/ttyO*. Then I disabled the new driver CONFIG _SERIAL_OMAP and used 8250, but the result is the same. Is it because I missed to modify any related files when I replaced 2.6.32 serial.c with 2.6.37 version? (For example, changing omap_hwmod_34xx.h to omap_hwmod_3xxx.c) Any idea to add the 2.6.37 omap-serial driver to 2.6.32 kernel or get / dev/ttyO* on 2.6.32? Thanks. Christine -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
