> And what happens if it's not in the Port_#xxxx_Hub_#yyyy format? Do we set
> all the ports from that hub as port 0?
No I kept the SPDRP_ADDRESS call, however if the SPDRP_LOCATION_INFORMATION is
in the right format it will override that (possibly wrong) value.
> Also, what exactly does the ASMedia driver return as a string for this query?
Port_#0007.Hub_#0001. (while the SPDRP_ADDRESS call returns 0, usbview confirms
7 *IS* the right value. extra annoying is that the SPDRP_ADDRESS isn't always
wrong, hell it's right most of the time. but most of the time isn't really
cutting it )
> From what I'm seeing, your intent is to set the port number to zero, which is
> invalid, in the case of poking anything on an ASMedia connected hub, and
> pretend that everything's copacetic.
Wrong, I'm parsing out the 7 from the above string the replace the wrong
address the SPDRP_ADDRESS call gave me.
> Well, with the code less than 5 lines above pretty much saying "if we can't
> retrieve valid port data, then we eliminate the device"
It's more, hey double check the value out of SPDRP_ADDRESS and patch up the
value with the right information if you can. The device was already getting
eliminated due to the wrong address, i'm trying to un-eliminate it cause i want
to talk to it.
> it kind of looks like you are trying to hide your ASMedia annoyance.
Correct.
> (most likely a driver bug that ASMedia should be the ones to fix) under the
> rug.
Correct.
> As such, I don't think this is something we can really go with: displacing
> the problem, rather than solving it, will only end up impacting other users.
Your call, not happy about it but I understand where you are coming from.
> This may sound like an acceptable solution to you, but for everyone who
> expects consistency with how we assign port numbers, and/or uniquely identify
> a device, not so much...
Fair enough, on the other hand, usbview is perfectly able to figure out the
device is actually on port 7. if they can so should you.
> Have you tried upgrading your ASMedia drivers to the latest version?
ASMedia is somewhat annoying in this regard, they offer no downloads on their
website, so you'll end up on creepy forum links where someone keeps a
collection of fishy links. I have installed what i think is the latest
driver+fw (and newer than what asus is offering me for my motherboard) but if
it's really the latest? who knows. Which is also the main reason i tried
sweeping it under the rug in libusbx instead of contacting the vendor, even if
they did fix it, how do end users that code? asmedia isn't publishing it on
their website, and asus doesn't post updates (given i was able to find newer
stuff, months old so they had plenty of time) by the looks of it.
> My other questions to you then are:
> Have you contacted ASMedia support and asked them if they are aware that
> their driver is not compliant with Microsoft's API and breaks USB
> applications? What did they say?
No, not yet, given the hard to get nature of the ASMedia FW/Drivers,i figured
offering a work around was more productive us of my time.
But in the end yeah ideally ASMedia fixes this bug and makes a new driver+fw
available for all, I'm pretty sure i don't live in an ideal world though.
Your call if/what you want do do about it. I've seen this problem many many
times with people with RTL-SDR sticks which usually end up plugging their
sticks in usb2 ports to make the problem go away, That however was not a
solution for my usb3 device.
I'll contact asmedia but in all honesty i'm not expecting much there.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/147#issuecomment-25085947
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
_______________________________________________
libusbx-devel mailing list
libusbx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusbx-devel
