Discussion:
ar9485 support
(too old to reply)
Jaap Boender
2013-12-24 15:35:57 UTC
Permalink
Hi all,

Just upgraded to -CURRENT a laptop that contains an Atheros AR9485
chip. It currently doesn't seem to be recognised by athn, though I notice
that there is some support for it in the code. pcictl confirms that it's an
AR9485.

Anything I can do to help add/test support for this device?

best,

Jaap
--
"Then I'll tell the truth. We're allowed to do that in emergencies."

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
Robert Elz
2013-12-24 15:55:02 UTC
Permalink
Date: Tue, 24 Dec 2013 15:35:57 +0000
From: Jaap Boender <***@kerguelen.org>
Message-ID: <***@kerguelen.org>

| Just upgraded to -CURRENT a laptop that contains an Atheros AR9485
| chip.

Mine has the same - from a quick look at the code, I had decided to try
just adding the chip id to the list of supported devices - I suspect that's
all that might be missing.

It hasn't been urgent for me, as there's still (I think) no support
in NetBSD's X for the display adaptor in my laptop, and that's a much
more serious problem (wireless access can be had via a USB dongle,
graphics, not so easy...)

kre


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
Jaap Boender
2013-12-24 17:27:00 UTC
Permalink
Post by Robert Elz
Mine has the same - from a quick look at the code, I had decided to try
just adding the chip id to the list of supported devices - I suspect that's
all that might be missing.
Doing this certainly makes the chip be recognized, I now have an
athn0 device. It doesn't quite work, however, when I try to run
wpa_supplicant I get a bunch of
'athn0: could not initialize calibration'
messages.

But this is definitely progress - I'm not at all an expert at device driver
programming, so I can't really help out with the actual work, but I'd be
happy to test things out if anyone'd like to tell me what to do.

cheers,

Jaap
--
"Then I'll tell the truth. We're allowed to do that in emergencies."

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
Robert Elz
2013-12-24 17:01:25 UTC
Permalink
Date: Tue, 24 Dec 2013 17:27:00 +0000
From: Jaap Boender <***@kerguelen.org>
Message-ID: <***@kerguelen.org>

| It doesn't quite work, however, when I try to run
| wpa_supplicant I get a bunch of 'athn0: could not initialize calibration'
| messages.

That's actually useful info - it should save sometime. The freebsd
driver works, and the AR9485 is supposed to be quite similar to some
other atheros chip that NetBSD already supports, so between those I
suspect that making this one work should not be all that difficult.

However, while working on this is on my todo list, I can't promise any
time on it in the next month or so. Maybe, but ...

kre


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
Loading...