I want to bring the following to the broader misc@ audience:

The entry in want.html reads:

USB wifi devices based on AR7010 chips (see link for specific product
names), with and without support for 5GHz channels, are needed in
Berlin, Germany, in order to improve and maintain athn(4) driver support
for open source firmware which can run on such devices. Contact
s...@openbsd.org.

The commit message is:

----------------------------
Add a request for AR7010 devices which I will need to continue working
on USB athn(4) open source firmware support.

These devices come in several variants, most of which are hard to track down,
and some of which are relatively expensive.
See https://wikidevi.com/wiki/Atheros_AR7010 for product names.

I have already received an offer for financial reimbursement, but my
biggest problem is that hunting these devices down takes time and effort.

Perhaps somebody has such a device somewhere gathering dust?

I will need at least a 5GHz (11a/b/g/n) variant and a 2GHz (11b/g/n) variant.
And having a device with accessible UART would be nice.

Some people have very vocally complained about closed wifi firmware on
our mailing lists. Now this is your chance to do something productive
about that issue and give back to the community.
----------------------------

I found:

Panasonic TYWL20U Wireless LAN Adaptor          EUR 137,--
https://www.amazon.de/Panasonic-TYWL20U-Wireless-LAN-Adaptor/dp/B007HH95F0

But cannot afford to just hit "buy" atm. 


Also interesting, previous commit message for want.html:
----------------------------
Remove my request for Atheros AR5008E-3NX devices.

One such device was donated some time ago, thanks to Gerrit Meyerheim.
Additional thanks to everyone else who subsequently offered to obtain
such a device for me.

The card I got cannot yet work with our athn(4) driver because it does not
have an EEPROM (which, among other things, provides the PCI device ID).

I now need help with finding a generic EEPROM and/or a way to generate
EEPOM images which contain suitable data. Since this is a narrowly scoped
task which does not require kernel driver development skills, I want to
delegate it. If you are interested in working on this task, and especially
if you have contacts in the OpenWRT community (who have solved this issue
in their OS), let me know.
----------------------------

Marcus

Reply via email to