Hy,
> The following thread is quite good. The author is quite good
> at USB and he thinks that usbser.sys is weird.
> http://www.cygnal.org/ubb/Forum9/HTML/000945.html
Thanks for your hint, i'll check it.
> Still I will think "unable to open COM Port" error may not be
> due to the device at all.
Hy,
> Were you getting such messages from the kernel? "dmesg"
> would show them if you were.
Sorry, i forgot to mention that i included some "extended" printk's by myself.
> But again: if you're not already getting those warnings,
> don't bother looking since that's not the problem.
I get no me
On Wednesday 16 January 2008, Thomi Aurel RUAG A wrote:
> > Alternatively, the issue might be the way the SET_LINE_CODING or
> > SET_CONTROL_LINE_STATE requests are rejected by the current serial
> > gadget code. Fixing that should be a straightforward patchlet. If
> > you're NOT getting one of
Hy Dave, Gregg
Thanks for your answers.
To Dave:
> I've heard some folk report that the MS-Windows support for CDC is a
> bit flakey. Maybe that's part of their general strategy of
> undermining standards-based interoperability...
I googled for some details about the used usbser.sys driver but fo
