lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 4 Jul 2016 10:45:02 -0700 From: Guenter Roeck <linux@...ck-us.net> To: Heikki Krogerus <heikki.krogerus@...ux.intel.com> Cc: Greg KH <gregkh@...uxfoundation.org>, Oliver Neukum <oneukum@...e.com>, Felipe Balbi <felipe.balbi@...ux.intel.com>, Roger Quadros <rogerq@...com>, Rajaram R <rajaram.officemail@...il.com>, linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org Subject: Re: [PATCHv4 1/2] usb: USB Type-C connector class 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). Guenter
Powered by blists - more mailing lists