Hi Tony, Current omap serial driver takes control of all 3 (4 on OMAP3640) UARTS. However, we have such a setup where UART2 for example is used by bluetooth driver. It uses the UART as non-standard way (there are some Nokia extensions to H4 protocol) so we cannot use the standard driver for driving the UART but have written special one for that purpose. Question is: Is there any, upstreamable, way of preventing omap serial driver to do this? Currently this is done with custom #ifdef hackery to mach-omap2/serial.c. Alternative solution that comes into mind is to specify UART configuration in board files and let serial driver to use that instead of hard-coded one. Or do you have some nice alternatives? Thanks, MW -- 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
