From: adr@sdf.org
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] USB3 1Gb ethernet card working on 9legacy (rpi 4)
Date: Mon, 1 Aug 2022 12:29:18 -0400 [thread overview]
Message-ID: <16593713580.F1ef9C5A9.763092@composer.9fans.topicbox.com> (raw)
In-Reply-To: <093ec4619e7568c054a825f5d5d8cc7f@hamnavoe.com>
[-- Attachment #1: Type: text/plain, Size: 1415 bytes --]
I've been experimenting again. With etherusb in the kernel, usbd is
triggering usb/ether and the device is mounted at /dev. I don't know
what happened before.
But there is no etherusb device.
; echo noauto ether > /dev/usbdctl
(unplug and plug again the device)
; sed /ether/q /dev/usb/ctl
...
ep9.0 enabled control rw speed super maxpkt 512 pollival 0 samplesz 0 hz 0 hub 0 port 1 rootport 2 addr 7 idle
255 csp 0x00ffff csp 0x000602 csp 0x00000a vid 0x0bda did 0x8153 Realtek 'USB 10/100/1000 LAN' xhci
; usb/ether -ddd /dev/usb/ep9.0
[...]
ether: ep in /dev/usb/ep9.1 maxpkt 1024; ep out /dev/usb/ep9.2 maxpkt 1024
usb/ether: etherusb bind #l0: bad process or channel control request
usb/ether: etherusb bind #l1: bad maxpkt "bind cdc #u/usb/ep9.1/data #u/usb/ep9.2/data 00e04c680cfb 2000 1024"
usb/ether: etherusb bind #l2: no free devices
usb/ether: 1 buffers
usb/ether: dev ref 3
usb/ether: etherbread
usb/ether: fsadd etherU9
So bad maxpkt... etherusb check for maxpkt < 512 which is the max for
bulk transfers in usb2 high speed. Using 1024 instead fixes the problem.
Should it chek for the speed of the usb device and set the limit accordingly?
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T668643d11149fab4-M829ca30175f489f095e58ae9
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 2416 bytes --]
next prev parent reply other threads:[~2022-08-01 16:29 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
2022-08-01 9:16 ` Richard Miller
2022-08-01 16:29 ` adr [this message]
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=16593713580.F1ef9C5A9.763092@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).