Am Sonntag, Februar 10, 2019 14:19 CET, Stefan Sperling <[email protected]> schrieb:
> On Sun, Feb 10, 2019 at 11:50:35AM +0100, Sebastian Reitenbach wrote: > > The non-working one shows up as AR7015 in Windows, but I don't see a AR7015 > > chipset > > mentioned in athn(4), therefore I wanted to verify, if that particular > > chipset is actually > > supported by our athn(4) at all? > > Indeed, it looks like our athn(4) driver does not support this device > properly. My guess is that the driver should be using ar9287_attach() > instead of ar9285_attach() for this device. > > What happens when you try this diff with the non-working device? > (This diff will break devices which are already working, that is expected.) I get the same bad ROM checksum message with the broken device, and indeed, the device that worked before, now gives the same bad ROM checksum message when I insert it. It only give a different checksum: previously working device: 0x2243 non-working device: 0x2c64 cheers, Sebastian > > Index: athn.c > =================================================================== > RCS file: /cvs/src/sys/dev/ic/athn.c,v > retrieving revision 1.99 > diff -u -p -r1.99 athn.c > --- athn.c 26 Apr 2018 12:50:07 -0000 1.99 > +++ athn.c 10 Feb 2019 13:15:28 -0000 > @@ -196,7 +196,7 @@ athn_attach(struct athn_softc *sc) > error = ar9285_attach(sc); > #if NATHN_USB > 0 > else if (AR_SREV_9271(sc)) > - error = ar9285_attach(sc); > + error = ar9287_attach(sc); > #endif > else if (AR_SREV_9287(sc)) > error = ar9287_attach(sc); > > > >
