From: adr@sdf.org
To: 9fans <9fans@9fans.net>
Subject: [9fans] USB3 1Gb ethernet card working on 9legacy (rpi 4)
Date: Sun, 31 Jul 2022 13:58:39 -0400 [thread overview]
Message-ID: <16592903190.8e7cccc4d.691312@composer.9fans.topicbox.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1668 bytes --]
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=0x8153 to /sys/src/cmd/usb/usbd/usbdb.
Browsing the list's archives I thought that ether1=type=usb 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 sequence was:
ether1=type=usb 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 ether1=type=usb and etherusb 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-Mf7759a301a20f1a6e655ffc0
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 2815 bytes --]
next reply other threads:[~2022-07-31 17:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-31 17:58 adr [this message]
2022-07-31 18:08 ` hiro
2022-07-31 18:09 ` adr
2022-07-31 21:35 ` Richard Miller
2022-08-01 9:16 ` Richard Miller
2022-08-01 16:29 ` adr
2022-08-02 8:50 ` Richard Miller
2022-08-03 0:34 ` adr
2022-08-03 3:00 ` adr
2022-08-03 10:57 ` Richard Miller
2022-08-03 18:46 ` adr
2022-08-04 10:13 ` Richard Miller
2022-08-04 11:56 ` ori
2022-08-04 19:34 ` adr
2022-08-05 12:14 ` ori
2022-08-01 16:43 ` adr
2022-08-01 17:06 ` adr
2022-08-02 3:45 ` Lucio De Re
2022-08-02 9:07 ` Richard Miller
2022-08-03 0:52 ` adr
2022-08-03 1:08 ` adr
2022-08-03 12:41 ` Richard Miller
2022-08-03 18:47 ` adr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=16592903190.8e7cccc4d.691312@composer.9fans.topicbox.com \
--to=adr@sdf.org \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).