Mike: > Qi passes in the official Openmoko USB mac address; u-boot does not. That makes sense because I previously was using u-boot. It must have changed to eth1 or something without me realizing it. I've added your suggestion to the USB networking wiki page. :-)
> A word of caution ... Thanks for that, I won't try to connect via my mac then. Marcus: > You could try to install the images from http://panicking.kicks-ass.org/download/ Ok so I've done that, and it seems to be working better. But when I wake it up, my screen is in grayscale mode? I looked on the wiki page and searched the mailing list archives, but didn't see any mention of this: http://wiki.openmoko.org/wiki/Android_usage#Suspend Thanks, Ben On Tue, Apr 21, 2009 at 9:16 AM, Mike (mwester) <[email protected]> wrote: > David Hicks wrote: > > > > > > Quick, dumb suggestion without having read the full context of this - > > did you look to see if there's an eth1 (or other new) interface? > > > > I noticed mine changed from usb0 to eth1 when hooked up to my laptop > > some time ago. Maybe something to do with android, may be something to > > do with qi. > > Many host systems will assign eth<n> addresses when they detect an > official (non-locally-generated) mac address on the usb network connection. > > Qi passes in the official Openmoko USB mac address; u-boot does not. > > Mike (mwester) > > > (A word of caution -- the way Qi does this is broken; it assigns the > same mac address for both device and host, which is said to fail with > OS X as well as IPv6.) > _______________________________________________ > android-freerunner mailing list > [email protected] > http://android.koolu.org/listinfo.cgi/android-freerunner-koolu.org >
_______________________________________________ android-freerunner mailing list [email protected] http://android.koolu.org/listinfo.cgi/android-freerunner-koolu.org
