<div dir="auto"><div>Ok, so to be clear, I should disable serial console and USB cdc ether will work?<br><br><div class="gmail_quote"><div dir="ltr">On Wed, Jan 30, 2019, 06:27 Joel Wirāmu Pauling <<a href="mailto:aenertia@aenertia.net">aenertia@aenertia.net</a> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto">It slows down the SPI bus frequency and breaks several other DTB overlays.<div dir="auto"><br></div><div dir="auto">The sunxi stuff has proper Uarts separate to ghr GPIO which is one reason I favour them over the real rpi.</div></div><br><div class="gmail_quote"><div dir="ltr">On Tue., 29 Jan. 2019, 18:26 Marc MERLIN <<a href="mailto:marc@merlins.org" target="_blank" rel="noreferrer">marc@merlins.org</a> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Tue, Jan 29, 2019 at 06:15:15PM +1300, Joel Wirāmu Pauling wrote:<br>
> I Enable the gpio serial it works with UART normally but due to<br>
> architectural issues with the broadcom SOCs can interfere with perf.<br>
<br>
Are you saying that using serial console breaks usb ethernet?<br>
<br>
> On Tue., 29 Jan. 2019, 18:02 Marc MERLIN <<a href="mailto:marc@merlins.org" rel="noreferrer noreferrer" target="_blank">marc@merlins.org</a> wrote:<br>
> <br>
> > On Tue, Jan 29, 2019 at 07:04:24AM +1100, Wes Cilldhaire wrote:<br>
> > ><br>
> > ><br>
> > > ----- On 26 Jan, 2019, at 7:17 PM, martin f krafft <a href="mailto:madduck@madduck.net" rel="noreferrer noreferrer" target="_blank">madduck@madduck.net</a><br>
> > wrote:<br>
> > > > On the Pi I just get the message<br>
> > ><br>
> > > > "udc-core: couldn't find an available UDC - added [g_cdc] to list<br>
> > > > of pending drivers."<br>
> > ><br>
> > > > which the article says means that I didn't enable the dwc2 properly.<br>
> > ><br>
> > > > But hey:<br>
> > ><br>
> > > > # grep dwc /proc/cmdline<br>
> > > > 8250.nr_uarts=0 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416<br>
> > > > bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:3B:08:DD<br>
> > > > vc_mem.mem_base=0x1ec00000 vc_mem.mem_size=0x20000000<br>
> > > > dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1<br>
> > > > root=PARTUUID=9a617d9a-02 rootfstype=ext4 elevator=deadline<br>
> > > > fsck.repair=yes rootwait modules-load=dwc2,g_cdc<br>
> > > > ^^^^^^^^^^<br>
> > ><br>
> > > You need to add the dtoverlay=dwc2 line in config.txt as well so the<br>
> > device actually appears in the device tree for the module to find.<br>
> > ><br>
> > > Yes, I overlooked this step too initially, something about its position<br>
> > in the instructions seems to make one's mind skip over it :)<br>
> > > (null)<br>
> ><br>
> > I can't get cdc_ether working<br>
> ><br>
> > I used the rPi image that was available from the burner near rego.<br>
> ><br>
> > As indicated here, I did this:<br>
> > root@raspberrypi:~# grep dwc2 /boot/config.txt<br>
> > dtoverlay=dwc2<br>
> > root@raspberrypi:~# grep dwc2 /boot/*.txt<br>
> ><br>
> > /boot/cmdline.txt:dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1<br>
> > root=PARTUUID=b4261201-02 rootfstype=ext4 elevator=deadline<br>
> > fsck.repair=yes rootwait splash plymouth.ignore-serial-consoles<br>
> > modules-load=dwc2,g_ether<br>
> > /boot/config.txt:dtoverlay=dwc2<br>
> ><br>
> > interface seems to come up:<br>
> > [ 5.655024] dwc2 20980000.usb: 20980000.usb supply vusb_d not found,<br>
> > using dummy regulator<br>
> > [ 5.655159] dwc2 20980000.usb: 20980000.usb supply vusb_a not found,<br>
> > using dummy regulator<br>
> > [ 6.113258] dwc2 20980000.usb: EPs: 8, dedicated fifos, 4080 entries in<br>
> > SPRAM<br>
> > [ 6.154975] dwc2 20980000.usb: DWC OTG Controller<br>
> > [ 6.162747] dwc2 20980000.usb: new USB bus registered, assigned bus<br>
> > number 1<br>
> > [ 6.252180] dwc2 20980000.usb: irq 33, io mem 0x20980000<br>
> > [ 7.044669] g_ether gadget: Ethernet Gadget, version: Memorial Day 2008<br>
> > [ 7.053989] g_ether gadget: g_ether ready<br>
> > [ 7.060353] dwc2 20980000.usb: bound driver g_ether<br>
> > [ 7.189129] dwc2 20980000.usb: new device is high-speed<br>
> > [ 7.236167] i2c /dev entries driver<br>
> > [ 7.565138] dwc2 20980000.usb: new device is high-speed<br>
> > [ 7.693246] dwc2 20980000.usb: new device is high-speed<br>
> > [ 7.766371] dwc2 20980000.usb: new address 10<br>
> > [ 7.787912] g_ether gadget: high-speed config #1: CDC Ethernet (ECM)<br>
> ><br>
> > I give it an IP:<br>
> > root@raspberrypi:~# ifconfig usb0<br>
> > usb0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500<br>
> > inet 192.168.1.2 netmask 255.255.255.0 broadcast 192.168.1.255<br>
> > inet6 fe80::15e4:95ea:e740:aa7d prefixlen 64 scopeid 0x20<link><br>
> > ether be:e6:a6:5b:35:18 txqueuelen 1000 (Ethernet)<br>
> ><br>
> > On my computer, I give it an IP too:<br>
> > root@raspberrypi:~# ifconfig usb0<br>
> > usb0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500<br>
> > inet 192.168.1.2 netmask 255.255.255.0 broadcast 192.168.1.255<br>
> > inet6 fe80::15e4:95ea:e740:aa7d prefixlen 64 scopeid 0x20<link><br>
> ><br>
> > dmesg says:<br>
> > Jan 28 20:38:26 saruman kernel: [728255.209791] usb 1-2: new high-speed<br>
> > USB device number 40 using xhci_hcd<br>
> > Jan 28 20:38:26 saruman kernel: [728255.358611] usb 1-2: New USB device<br>
> > found, idVendor=0525, idProduct=a4a2, bcdDevice= 4.14<br>
> > Jan 28 20:38:26 saruman kernel: [728255.358615] usb 1-2: New USB device<br>
> > strings: Mfr=1, Product=2, SerialNumber=0<br>
> > Jan 28 20:38:26 saruman kernel: [728255.358617] usb 1-2: Product:<br>
> > RNDIS/Ethernet Gadget<br>
> > Jan 28 20:38:26 saruman kernel: [728255.358619] usb 1-2: Manufacturer:<br>
> > Linux 4.14.79+ with 20980000.usb<br>
> > Jan 28 20:38:26 saruman kernel: [728255.359846] cdc_subset: probe of<br>
> > 1-2:1.0 failed with error -22<br>
> > Jan 28 20:38:26 saruman kernel: [728255.361388] cdc_ether 1-2:1.0 usb0:<br>
> > register 'cdc_ether' at usb-0000:00:14.0-2, CDC Ethernet Device,<br>
> > 62:3c:c9:7f:9d:e5<br>
> ><br>
> > Not sure if cdc_subset probe failed is bad.<br>
> ><br>
> > If I ping my computer from the rPi, I see its packets on my laptop:<br>
> > 20:58:43.391704 ARP, Request who-has 192.168.1.1 tell 192.168.1.2, length<br>
> > 28<br>
> > 20:58:43.391727 ARP, Reply 192.168.1.1 is-at 62:3c:c9:7f:9d:e5, length 28<br>
> ><br>
> > But no packet from my laptop never seems to make it back to the rPi.<br>
> ><br>
> > For those who got it to work, do I have the wrong rPi image or some<br>
> > other driver problem that causes the rPi not to get packets back in?<br>
> ><br>
> > Thanks,<br>
> > Marc<br>
> > --<br>
> > "A mouse is a device used to point at the xterm you want to type in" -<br>
> > A.S.R.<br>
> > Microsoft is to operating systems ....<br>
> > .... what McDonalds is to gourmet<br>
> > cooking<br>
> > Home page: <a href="http://marc.merlins.org/" rel="noreferrer noreferrer noreferrer" target="_blank">http://marc.merlins.org/</a> | PGP<br>
> > 7F55D5F27AAF9D08<br>
> > --<br>
> > Chat mailing list<br>
> > <a href="mailto:Chat@lists.lca2019.linux.org.au" rel="noreferrer noreferrer" target="_blank">Chat@lists.lca2019.linux.org.au</a><br>
> > <a href="http://lists.lca2019.linux.org.au/mailman/listinfo/chat" rel="noreferrer noreferrer noreferrer" target="_blank">http://lists.lca2019.linux.org.au/mailman/listinfo/chat</a><br>
> ><br>
<br>
-- <br>
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.<br>
Microsoft is to operating systems ....<br>
.... what McDonalds is to gourmet cooking<br>
Home page: <a href="http://marc.merlins.org/" rel="noreferrer noreferrer noreferrer" target="_blank">http://marc.merlins.org/</a> <br>
</blockquote></div>
</blockquote></div></div></div>