-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Somebody in the thread at some point said: | Yes, could be this as I am seeing the same messages in the log. I did | update uboot on the weekend (which is when I got the device). | | A wall charger worked normally, its just usb charging (tried a laptop | and a desktop) thats the problem.
Well it sounds a bit out of place to say it, but: great. At least we understand what's happening. A wall charger doesn't try to talk with the device over USB, it is recognized by a magic resistor on the USB ID pin, that's why it works but host charging didn't. I made patches to reduce the probability of this from 50:50 to ~10% and just sent them out, I didn't find how to eliminate it yet. | Which uboot is "safe"? I'm not sure. I suspect older U-Boot had lower probability of making the same problem since we had no idea this was happening until now, and some of the fixes I added would have been needed on older versions too. ~ best bet is to update to tomorrow's U-Boot and we'll try to remove the remaining chance of the problem in the meanwhile. http://git.openmoko.org/?p=u-boot.git;a=commitdiff;h=00c27eb2887c07a9b6cdf095e7be016ab7e42d52 http://git.openmoko.org/?p=u-boot.git;a=commitdiff;h=d872d1ffdbbaf93de0f9ee95debeb414cc6da90c http://git.openmoko.org/?p=u-boot.git;a=commitdiff;h=5ebb764a8bfb44786ba80e5102c85cbeaa7139c5 - -Andy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkiStTUACgkQOjLpvpq7dMqCPQCfZARgZXUoe/xNII5iLaT6ac51 2XwAn04KpXM6Ku6VqoHvZk744o2zQXah =6cct -----END PGP SIGNATURE----- _______________________________________________ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support