On Wed, Nov 05, 2014 at 11:18:12PM +0100, Sebastian Andrzej Siewior wrote: > * Krzysztof Opasiak | 2014-10-27 11:53:09 [+0100]: > > >Main difference is that each loaded fabric module provides its own > >directory (/sys/kernel/config/target/$FABRIC_MOD/). This means that > >each loaded or built-in module has there it own directory. > > So I assumed they don't do and I don't recall this by the time I want > through the code. But if they really do this (as in code of current git) > why not stick to the same way instead of hacking a procfs/sysfs > interface?
The problem is that we would now have userland ABI problems, unless we have a way of providing backwards compatibility. We would also need patches to libusbg making sure it works with both old and new ways. Without that, we can't move forward :-s -- balbi
signature.asc
Description: Digital signature
