From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, HTML_MESSAGE,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2 autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 9488 invoked from network); 31 Jul 2022 17:58:49 -0000 Received: from tb-ob21.topicbox.com (173.228.157.67) by inbox.vuxu.org with ESMTPUTF8; 31 Jul 2022 17:58:49 -0000 Received: from tb-mx0.topicbox.com (tb-mx0.nyi.icgroup.com [10.90.30.73]) by tb-ob21.topicbox.com (Postfix) with ESMTP id 1C31C1FDE4 for ; Sun, 31 Jul 2022 13:58:46 -0400 (EDT) (envelope-from bounce.mMf7759a301a20f1a6e655ffc0.r522be890-2105-11eb-b15e-8d699134e1fa@9fans.bounce.topicbox.com) Received: by tb-mx0.topicbox.com (Postfix, from userid 1132) id B99372EF6DCE; Sun, 31 Jul 2022 13:58:45 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=9fans.net; h=from:to :message-id:date:mime-version:content-type :content-transfer-encoding:list-help:list-id:list-post :list-subscribe:reply-to:subject:list-unsubscribe; s=dkim-1; t= 1659290325; x=1659376725; bh=3A9gXrIwf+8xJoSXhk14J91i85p5yYro4zV sSxY/khM=; b=b9VPbrjncwO78UWYHXniAPLq/7oCnxt6HX4e8XT4WDKg/O598GA cPf29/IItlwRHVdVxqoHnLvSNVJxaxbQ2Pif8soefI1DqFmPzstvWZ9VtHdf+wOe WgCvZEL+my8ia3xw+EnbKj+qj0tYeBHmb9jPV3atOOjNFcwnYGZ9bS50= From: adr@sdf.org To: 9fans <9fans@9fans.net> Message-Id: <16592903190.8e7cccc4d.691312@composer.9fans.topicbox.com> Date: Sun, 31 Jul 2022 13:58:39 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary=16592903191.f4fCBd7fA.691312 Content-Transfer-Encoding: 7bit Topicbox-Policy-Reasoning: allow: sender is a member Topicbox-Message-UUID: 6866aef6-10fa-11ed-b1e3-a8aa1d2d11b0 Archived-At: =?UTF-8?B?PGh0dHBzOi8vOWZhbnMudG9waWNib3guY29tL2dyb3Vwcy85?= =?UTF-8?B?ZmFucy9UNjY4NjQzZDExMTQ5ZmFiNC1NZjc3NTlhMzAxYTIwZjFhNmU2NTVm?= =?UTF-8?B?ZmMwPg==?= List-Help: List-Id: "9fans" <9fans.9fans.net> List-Post: List-Software: Topicbox v0 List-Subscribe: Precedence: list Reply-To: 9fans <9fans@9fans.net> Subject: [9fans] USB3 1Gb ethernet card working on 9legacy (rpi 4) List-Unsubscribe: , Topicbox-Delivery-ID: 2:9fans:437d30aa-c441-11e9-8a57-d036212d11b0:522be890-2105-11eb-b15e-8d699134e1fa:Mf7759a301a20f1a6e655ffc0:1:xp8rCdQw0iGRR-My8qk0dqS7OjKQYvWR-pK8TPCuknc --16592903191.f4fCBd7fA.691312 Date: Sun, 31 Jul 2022 13:58:39 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable https://es.aliexpress.com/item/1005003167747779.html First time using usb/ether, so let me share my experience for other users. This is on the last 9pi image at 9legacy. First, I added a line with did=3D0x8153 to /sys/src/cmd/usb/usbd/usbdb. Browsing the list's archives I thought that ether1=3Dtype=3Dusb should be added to the configuration file (cmdline.txt on the pi), but etherusb wasn't in the link section of the pi4 kernel configuration file, so #l1 wasn't created. I added, compiled the kernel and then a dummy #l1 was created, impossible to configure. I could use manually usb/ether and configure the device mounted in /net, but usbd didn't detect the usb card. Then I removed the ether parameters in cmdline.txt and etherusb from pi4 to be sure, now usbd recognize the card and creates the device /dev/etherU0. Other programs expect the devices mounted in /net. I'm binding the device inside a directory in /tmp and then binding this directory to /net. I would appreciate if someone shares the correct way of doing this. In summary, the=C2=A0sequence was: ether1=3Dtype=3Dusb in plan9.ini (cmdline.txt) etherusb in kernel config #l1 is created but useless usbd doesn't work because etherusb usb/ether works and the device appears on /net/ remove=C2=A0ether1=3Dtype=3Dusb and=C2=A0etherusb from the kernel now usbd works but the device doesn't appear on /net but on /dev I finally made it work, but this is a mess, really. ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/T668643d11149fab4-Mf7759= a301a20f1a6e655ffc0 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription --16592903191.f4fCBd7fA.691312 Date: Sun, 31 Jul 2022 13:58:39 -0400 MIME-Version: 1.0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

First time using usb/ether, so let me sha= re my experience for other users.

This is = on the last 9pi image at 9legacy.

First, I added a line with did=3D0x8153 = to /sys/src/cmd/usb/usbd/usbdb.
Browsing the list's arc= hives I thought that ether1=3Dtype=3Dusb should be
added to= the configuration file (cmdline.txt on the pi), but etherusb
wasn't in the link section of the pi4 kernel configuration file, so = #l1
wasn't created. I added, compiled the kernel and th= en a dummy #l1 was
created, impossible to configure. I coul= d use manually usb/ether and
configure the device mounted i= n /net, but usbd didn't detect the usb
card. Then I rem= oved the ether parameters in cmdline.txt and etherusb
from = pi4 to be sure, now usbd recognize the card and creates the
device /dev/etherU0. Other programs expect the devices mounted in
/net. I'm binding the device inside a directory in /tmp and the= n
binding this directory to /net. I would appreciate if som= eone shares
the correct way of doing this.

In summary, the sequence was:<= /div>
ether1=3Dtype=3Dusb in plan9.ini (cmdline.txt)
et= herusb in kernel config
#l1 is created but useless
usbd doesn't work because etherusb
usb/ether works an= d the device appears on /net/
remove ether1=3Dtype=3Dusb and=  etherusb from the kernel
now usbd works but the devic= e doesn't appear on /net but on /dev

I= finally made it work, but this is a mess, really.
= --16592903191.f4fCBd7fA.691312--