Seems it's not work, extra operating current @500mA for iPhone is not appeared in System Information -> USB
The screen shot shows the iPhone is connected as a high-speed device, for which 500mA is max. The extra-current errors are for super-speed devices only. They leave a message like this in system.log
The IOUSBFamily did not receive enough extra current for the SuperSpeed device ____ at _____, asked for 400mA but got 0 mA
Rampage Dev: The message
WaitForCMD: Timeout waiting for command completion, 100ms
indicates the xhci controller in stalled. The KP later is in Apple's code (AppleUSBHub), probably because the controller is stalled and returning errors AppleUSBHub doesn't process well. I'll need to see a xhcdump of the controller state. Maybe with no connected devices it won't KP so xhcdump can be recorded.
68x: Usually it's because auxillary power is not supplied to the xhci chip during sleep.
Your xhci chip can't sleep. The delay is because of bus reenumeration. I suggest you try booting with '-gux_nosleep' - the reenumeration might be faster that way because it starts from a better position.
The super class vtable '__ZTV17IOUSBControllerV3' for vtable '__ZTV14GenericUSBXHCI' is out of date. Make sure your kext has been built against the correct headers.
You're using some outdated IOUSBFamily. The one in OS 10.7.5 should be version 510.4.6. I tried loading GenericUSBXHCI with it in both 64-bit and 32-bit yesterday and it worked.
Can you clarify something? If this is installed on a 7 series chipset with intel native USB 3.0, does it work alongside the apple USB 3.0 drivers or does it supersede them? the reason is it seems for full compatibility it would be good if this driver were able to work on third party chipsets while allowing the apple driver to control the intel ones.
You can do this by editing GenericUSBXHCI.kext/Contents/Info.plist, and changing IOProbeScore from 1 to -1. AppleUSBXHCI has an IOProbeScore of 0. If you set it lower, the kernel will first try to start AppleUSBXHCI on all chips. It will succeed for Intel and fail for the others (provided you don't set AllowAnyXHCI to true). After that, GenericUSBXHCI will be loaded for the others.
Note on the extra-current error - I found where this error is coming from, but it's going to take some work to figure out how to make it go away. Stay tuned.