-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Somebody in the thread at some point said: | Andy Green wrote: |> So... it's a firmware problem we can't do anything about? | | We'll see. I haven't heard back from Atheros yet. | | Since the module duly reports when it has crashed, we could also | catch that indication (there's already a notification mechanism | in place that can also convey this kind of errors) and restore | sanity by resetting the module.
Just wondering where the point is that we shrug and move on if it is intimately tied into the non-updateable firmware action. It seems that we might be able to clear up remaining problems by somehow having the interface being logically taken up and down also cycle the modules. If wpa_supplicant's automatic up and down action when it loses association does that and hard resets everything on the module and stack, it might avoid us having to do time consuming and intricate cartography on the completely dark firmware landscape. - -Andy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkl4+8YACgkQOjLpvpq7dMo06ACfaexZblGN7P7XJLgtpKuBjCKf u2YAni3WfFFKMGMmeuoe+lshvtxQcG0P =xsYj -----END PGP SIGNATURE----- _______________________________________________ devel mailing list devel@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/devel
