On Fri, Nov 05, 2010 at 05:09:57AM -0500, Ming Lei wrote:
2010/11/5 Grazvydas Ignotas <notasas@xxxxxxxxx>:
hi,
On Fri, Nov 5, 2010 at 10:39 AM, Enric Balletbò i Serra
<eballetbo@xxxxxxxxx> wrote:
Hello all,
With current mainline and stable 2.6.35.y branch I've some strange
features with USB ethernet gadget ...
root@igep0020:~# uname -a
Linux igep0020 2.6.37-rc1+ #1 Fri Nov 5 09:22:53 CET 2010 armv7l
unknown unknown GNU/Linux
root@igep0020:~# ifconfig
usb0 Link encap:Ethernet HWaddr 5A:A9:54:25:4C:04
inet addr:192.168.7.2 Bcast:192.168.7.255 Mask:255.255.255.0
inet6 addr: fe80::58a9:54ff:fe25:4c04/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:28 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:4951 (4.8 KiB)
Pinging seems not work
root@igep0020:~# ping -c5 192.168.7.1
PING 192.168.7.1 (192.168.7.1): 56 data bytes
--- 192.168.7.1 ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss
Curiously if I unplug and plug the USB cable, and ping again ...
root@igep0020:~# ping -c5 192.168.7.1
PING 192.168.7.1 (192.168.7.1): 56 data bytes
64 bytes from 192.168.7.1: seq=0 ttl=64 time=0.397 ms
64 bytes from 192.168.7.1: seq=1 ttl=64 time=0.489 ms
64 bytes from 192.168.7.1: seq=2 ttl=64 time=0.397 ms
64 bytes from 192.168.7.1: seq=3 ttl=64 time=0.366 ms
64 bytes from 192.168.7.1: seq=4 ttl=64 time=0.396 ms
--- 192.168.7.1 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 0.366/0.409/0.489 ms
Works, anyone knows if the ethernet gadget is broken in current
mainline or have observed this feature ?
Please try this patch:
http://marc.info/?l=linux-usb&m=128576496614332&w=2
Report back if it works, maybe then that patch will finally get merged..
No, the patch is not merged to now.
Felipe, seems it is time to send out this musb bugfix patches.
already queued.
--
balbi
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
