On Sat, 4 Feb 2006, Helmut Toplitzer wrote:
You said above that there's no evidence that a device reset would help.
You need to find a way to get that evidence, either positive or negative.
Ok. Tried one other thing. Read about gcc-incompatibilities/fixes in the
the sourcecode (kernel Makefile). So I tried to use
another gcc-version (gcc-3.4 (GCC) 3.4.4 20050314 (prerelease) (Debian
3.4.3-13) instead of gcc (GCC) 3.3.5 (Debian 1:3.3.5-13))
Todo this I set MAKEFLAGS="CC=gcc-3.4 HOSTCC=gcc-3.4 HOSTCXX=g++-3.4" during
kernel-build-process and for building pvrusb2 and lirc modules.
Yes. It's running now for more than 120min. I will do some more tests in
the next days. So if you have some test-suggestions, you're welcome.
(BTW: Matrix is showing up at these minutes. Looks like there's another
glitch in the Matrix :-)
Helmut
Anything further here? Was that just a coincidence or is it really
working better for you now?
-Mike
--
| Mike Isely | PGP fingerprint
Spammers Die!! | | 03 54 43 4D 75 E5 CC 92
| isely @ pobox (dot) com | 71 16 01 E2 B5 F5 C1 E8
| |
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
