pali

When you consider adding such proxy support, it would be nice to have ability to proxy UPnP client requests to upstream PCP. Because e.g. Windows systems supports only UPnP IGD.

@miniupnp: Do you have any plans for implementing this functionality? It looks like that more people are interested in it and due to higher usage of CG-NATs and DS-Lite, such...

Yes, and that libusb-1.0 hotplug mechanism is unusable too. As wrote I think the whole libusb is slow due to asynchronous code. So hotplug (as async too) cannot help here....

Here is combined log from dmesg and above testing hotplug code. It was started with env LIBUSB_DEBUG=4 and against libusb-1.0.20 compiled from tarball: ``` [timestamp] [threadID] facility level [function call]...

Here is libusb 0.1 code which use busy waiting: ``` #include #include #include #include static volatile sig_atomic_t signal_quit; static void signal_handler(int signum) { signal_quit = 1; (void)signum; } static int...

I do not know why you need that log as libusb 0.1 is working and such busy waiting log is long, but here is (again combined with dmesg): ``` usb_set_debug:...

@mcuee Thats all? Or do you need anything else?

Use case (as already wrote): start communication with device at correct time. If computer does not negotiate device protocol in 0.3s time window, then device disconnect from usb. I already...

What I need to achieve? Communicate with that device ("Nokia USB ROM ") which is on usb bus just for 0.3s.

Short: Query various parameters, change boot settings or load own boot code. In details: See my project 0xFFFF: https://github.com/pali/0xFFFF But reason for device communication is irrelevant in this bug report....