On Mon, Jul 04, 2016 at 10:45:02AM -0700, Guenter Roeck wrote: > On 07/04/2016 10:11 AM, Heikki Krogerus wrote: > [ ... ] > > > > > We should not forget also that the userspace can never rely on those > > > > details because of the fact that they simply will not always be > > > > available. > > > > > > > On the other side, not being able to rely on a well defined ABI makes the > > > ABI much less useful. > > > > What do we do about this? > > > I'll have to think about it. Unfortunately, I'll have to put this on the > back-burner for the time being. My primary problem is that I need > a functional driver _now_ (ie by the end of this week), to meet an > upcoming deadline. Due to to the locking problem, I can not rely on the > typec infrastructure ... meaning I have to take two steps back and get > my code working with the Android infrastructure (which, coincidentally, > does not require locking and thus doesn't have all the resulting > limitations and complexities). That is unfortunate. I added a commit where I remove the lock completely (at least for now) to my github. Cheers, -- heikki -- 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
