M.Drochner@fz-juelich.de said:
> if_aue.c:
> 	if (uaa->iface != NULL)
> 		return (UMATCH_NONE); 
> That's actually a bug in that driver as I see it. It should work as
> well with an "==" at that point. 

Sorry, I confused this with another driver I'm having issues with.
The "aue" driver is correct. (Within the limits of the framework.)
Actually it doesn't matter at all...

To explain some more: USB driver attachment currently works as follows.
1. The device is not configured (in terms of USB), and aa->iface is NULL.
   A round of driver matches is done.
2. The framework selects a configuration (in theory one of multiple
   possibilities, but none of my devices has more than one). A configuration
   may consist if multiple interfaces.
   For each interfaces, aa->iface is set to it, and another round of
   driver matches is done.

This is pretty weak, and allows drivers to get away with all kinds
of misbehaviour.

best regards
Matthias