From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: Re: [9fans] USB3 1Gb ethernet card working on 9legacy (rpi 4)
Date: Sun, 31 Jul 2022 22:35:17 +0100 [thread overview]
Message-ID: <1fb1629ae1bac84f3378269735b40860@hamnavoe.com> (raw)
In-Reply-To: <16592903190.8e7cccc4d.691312@composer.9fans.topicbox.com>
What you're trying to do should work. I've just checked an ASIX usb2 ether
dongle on a pi4 as '#l1', usbd recognises it and I can mount '#l1' on /net
and configure it. I did have to add etherusb to the kernel config and rebuild
first, as you did.
The tricky part is that the real usb ether driver is /sys/src/cmd/usb/ether,
which makes the device appear in /dev because that's the default directory
where usbd mounts itself. (Use the -m flag for a different dir if you really
want to.)
The etherusb 'device' in the kernel is just a stub, which passes packets
directly between the usb endpoint to the network interface, without having
to go back and forth to the usb driver process. Just a performance shortcut;
you can use a usb ether driver without etherusb but it's slower.
When you start a usb ether driver, it tries a "bind" command with each
of the '#l' ctl files in the kernel to see if one of them works as etherusb.
If etherusb is configured in the kernel and enabled by a kernel parameter
eg ether1=type=usb, the bind will succeed and link the '#l1' device with
the usb ether driver which did the bind. You can then mount '#l1' on /net
in the usual way and configure /net/ether1.
You should see a kernel message when the etherusb and usb ether drivers
link up, with the MAC address of the dongle. For instance I see
etherusb asix: 000606e00ae7
This should happen whether usbd starts the driver automatically or you
do it by hand with usb/ether.
Do you get any interesting error messages if you try 'usb/ether -d' ?
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T668643d11149fab4-Mfe74a807004d1901910c0e32
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2022-07-31 21:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-31 17:58 adr
2022-07-31 18:08 ` hiro
2022-07-31 18:09 ` adr
2022-07-31 21:35 ` Richard Miller [this message]
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=1fb1629ae1bac84f3378269735b40860@hamnavoe.com \
--to=9fans@hamnavoe.com \
--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).