On Tue, Apr 21, 2009 at 06:11:11PM +0100, David Woodhouse wrote: ... > The kernel output is going to be spewed when a console registers with > CON_PRINTBUFFER anyway, and if we printk a warning about userspace > console output being lost, that ought to be good enough to notify the > user that something may have been lost. For bonus points, we could even > make that 'dummy' tty driver buffer a limited amount of userspace > output, maybe. What in the world are users going to do when they see a message about output being lost? There is no way to recover the data and no way to prevent it in the future. I don't think this is a good approach. Remember, even though the previous functionality of USB consoles was, in theory, less reliable than it appeared, it actually has been working well for years. Thus, tossing output will count as a regression for most of the world. > If userspace cares, let _it_ wait, by using an ioctl to see what tty > device it's _really_ attached to. I have a notion, perhaps misguided, that userspace *always* cares about seeing all the output they have generated. I have no objection to a userspace solution, in the long run, but such an approach represents a significantly different approach to constructing boot filesystems and we need a transitional period. In the interim, let's get things working as they were. > David Woodhouse Open Source Technology Centre David VomLehn -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
