Hi,
Am 14.04.2013 16:01, schrieb Greg KH:
On Sun, Apr 14, 2013 at 11:42:06AM +0200, Karsten Malcher wrote:
please have a look at my last email in the bug report.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704242
Do you have an idea what's maybe the difference that this adapter is working with kernel 2.6.32 ?
Lots of things have changed from 2.6.32 to 3.2.
Yes - unfortunately and fortunately. :-)
Can you build your own kernels to test? If so, can you do a bisection
between those kernel releases to try to track down when things broke?
No sorry - at this time i only have an idea of the goal of it.
Maybe there are additional ideas at the debian team.
That's going to be the best/only way to try to figure this out.
I worried you will write somethnig like this.
Do you think it is something different in the driver itself or in the interaction of the driver and kernel?
When i look at the debug output of the opened working port i would say there is a polling for reading data about every
100 µs.
http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=42;filename=usingport.log;att=3;bug=704242
[ 1749.073740] /build/buildd-linux-2.6_2.6.32-38-amd64-bk66e4/linux-2.6-2.6.32/debian/build/source_amd64_none/drivers/usb/serial/pl2303.c: pl2303_chars_in_buffer - returns 0
[ 1749.073833] /build/buildd-linux-2.6_2.6.32-38-amd64-bk66e4/linux-2.6-2.6.32/debian/build/source_amd64_none/drivers/usb/serial/pl2303.c: pl2303_chars_in_buffer - returns 0
I didn't see something like this in kernel 3.2.0 ?
thanks,
greg k-h
Best regards
Karsten
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
