> Ok, I really have almost no sympathy for systems that don't use hardware > flow control and yet expect no overruns to happen. Come on, we learned > this decades ago that this is not a good idea. Don't force additional > software complexity onto systems that refuse to use two hardware gpio > lines properly. However, your idea of disabling input during console printk isn't a legitimate use of hardware handshaking. By coupling the input and output handshaking, you've created a lock ordering dependency. What if two such machines try to do a console printk simultaneously? Either they ignore handshaking during the printk, or deadlock. In the use case I'm thinking of (cross-connected serial consoles), 100% reliability isn't necessary; we just want a very high probability that important debug messages aren't getting mangled. -- To unsubscribe from this list: send the line "unsubscribe linux-serial" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
