On Mon, 14 Mar 2011 14:45:53 -0700 (PDT) David Miller <davem@xxxxxxxxxxxxx> wrote: > From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> > Date: Mon, 14 Mar 2011 14:43:09 -0700 > > > > > (switched to email. Please respond via emailed reply-to-all, not via the > > bugzilla web interface). > > > > The reporter says "workaround suggested in: > > https://bugzilla.kernel.org/show_bug.cgi?id=16831 seems to work well > > for me as well". That workaround appears to be "dump the kernel driver > > and use the driver off the vendor's website". > > This is an issue you've brought up to me several months ago. > > I started looking into it, but because the vendor driver development > happens in a completely different universe the divergence noise is > substantial and it's a huge effort to consolidate these two drivers. > > I think that until the vendor starts to care, nothing is going to > happen to resolve these ASIC driver bugs. Yup. I suppose an alternative approach might be to feed the current vendor driver through the drivers/staging process (preferably with their assistance!) then run with two alternative drivers for a while and eventually remove the old one. But that's without having looked at the vendor code. Is it a Big Mess? -- 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
