On Tue, Jul 28, 2009 at 04:59:33PM +0200, Janusz Krzysztofik wrote: > Following that model, the line discipline code didn't seam to belong to a > codec driver for me. If it could be recognized as a new bus dirver, it should > be pushed down probably into a separate module. However, if it was rather > some kind of a bus adapter driver, it seamed to belong to the machine code. The way it looks with the current code the line discipline itself is going to apply equally well to any serial port that's used - I'm not clear what's system-specific about it. The bit that connects the line discipline to the line is a different matter but the bit that interacts with the TTY layer after registration is working through a pluggable abstraction layer and shouldn't, I'd expect, be specific to the particular serial port. -- 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
