On Tue, Jul 05, 2011 at 05:04:11PM -0700, bernie@xxxxxxxxxxxx wrote: > Udlfb has been binding the framebuffer device to its parent, which > isn't correct and causes confusion with operations like udev remove. > > Coming plug and play multiseat support is dependent on this fix. > > Signed-off-by: Bernie Thompson <bernie@xxxxxxxxxxxx> On Sun, Jul 10, 2011 at 12:30:00AM -0700, bernie@xxxxxxxxxxxx wrote: > Match udlfb only against vendor-specific class (e.g. only DisplayLink > graphics, not composite standard audio class interfaces). This enables > compatibility with composite graphics+audio devices (e.g. HDMI). > > Match udlfb only against compatible subclass 0 and protocol 0 chips. > DisplayLink's USB 3.0 generation chips increment these values > to signal that they have a incompatible protocol, preventing udlfb > from erroneously matching to hardware it does not support. > > Tested to confirm proper behavior on both USB 2.0 and USB 3.0 > generation devices. > > Reported-by: Andrew Kephart <akephart@xxxxxxxxxxxx> > Signed-off-by: Bernie Thompson <bernie@xxxxxxxxxxxx> Both queued for 3.0, thanks. -- To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
