Re: axen
Nick Hudson <[email protected]>
| Newsgroups | gmane.os.netbsd.devel.network |
|---|---|
| Message-ID | <[email protected]> |
On 11/08/2023 18:58, Robert Swindells wrote: > > Nick Hudson <[email protected]> wrote: >> On 08/08/2023 16:55, Robert Swindells wrote: >>> What kind of USB port is that connected to? > >> port 3 addr 3: super speed, power 124 mA, config 1, AX88179(0x1790), >> ASIX Elec. Corp.(0x0b95), rev 1.00(0x0100), serial 0000133B799271 > > Mine is rev 2.00 > > port 4 addr 1: super speed+, power 46 mA, config 1, AX88179A(0x1790), > ASIX(0x0b95), rev 2.00(0x0200), serial 00000000002A84 > > No idea why it is showing "AX88179A". Because that's what the device has in its descriptors. > >>> It doesn't work for me at all without the change to the length argument >>> to usbnet_enqueue(). >> >> Network is broken (can't ssh into host) and I get these >> >> [ 61.0568368] axen0: discarding oversize frame (len=1518) >> [ 61.0768365] axen0: discarding oversize frame (len=1518) >> [ 63.7768881] axen0: discarding oversize frame (len=1518) >> [ 67.5569789] axen0: discarding oversize frame (len=1518) >> >> I didn't investigate why > > Would expect it is caused by the length passed to usbnet_enqueue(). > > I'm guessing the device causing this error is the same as mine: > > <mail-index.netbsd.org/current-users/2023/08/11/msg044250.html> > > I get that error with the driver in the tree. I guess the AX88179A does things slightly different to previous chips and the driver needs to handle the difference. There appears to be a reference driver at https://www.asix.com.tw/en/support/download Nick