Hi,
I am trying create a USB class driver that hooks up with the io-pkt stack.

I have the USB side of it sorted out using the DDK - this all works fine and can receive and send data.

However, I can see that the io-pkt driver has a "entry" function that scans for hardware. How can this fit in with the 
USB "attach" and "detach" mechanism? (I'm aware that the USB DDK spawns threads, and these callbacks are executed in non
-pkt4 "compliant" threads and that I can use a pulse to invoke a call in the stack's context if need be - so I can make 
any calls to the stack occur in the correct context.)

Can I dynamically call net_attach when I get a USB insertion? (At the moment I get a core dump, but am not set up 
properly for debugging on the target... I think it's core dumping on the first call to the USB api.)

I tried writing some code that scanned the USB bus, and although I found all the device interfaces and endpoints for 
CDC_ECM, I just get "resource busy" when I try to do any USB configuration such as changing interfaces...?