Re: want.html wifi stsp@

2017-11-21 Thread Stefan Sperling
On Tue, Nov 21, 2017 at 06:48:49PM +, Alfred Morgan wrote:
> I looked through your links and found some relatively inexpensive devices.
> Would any of these satisfy any of your requirements?
> 
> 15 GBP - Datel Wireless and Network Adaptor (Xbox 360)
> http://amzn.eu/6Bi93OR

See the remark about lack of support in the ath9k_htc driver here:
https://wikidevi.com/wiki/Datel_Wireless_%27N%27_Networking_Adapter_For_Xbox_360

That said, information on wikidevi might be outdated; perhaps Linux
supports this device nowadays? Best way of finding out is to buy and try.

But for now I'd prefer to work against a device that's known to work.

> 15 USD - TP- Link Wireless USB Adapter
> http://a.co/8Qjf8gN

Hard to know with this one. TP-Link has reused this product name for
different atheros and realtek chips:

https://wikidevi.com/wiki/TP-LINK_TL-WN822N_v1 some atheros legacy 11n :(
https://wikidevi.com/wiki/TP-LINK_TL-WN822N_v2 atheros AR7010 :)
https://wikidevi.com/wiki/TP-LINK_TL-WN822N_v3 realtek :(
https://wikidevi.com/wiki/TP-LINK_TL-WN822N_v4 realtek :(

I suppose that most athn USB users will end up with AR9271 instead of AR7010,
because AR9271 devices are much easier to track down for a reasonable price.
Still, I need an AR7010 to make sure my driver changes don't break it.

One such device has now been secured by sthen@, but for development it
would help to have at least two (e.g. to test client/hostap interaction).



want.html wifi stsp@

2017-11-21 Thread Alfred Morgan
I looked through your links and found some relatively inexpensive devices.
Would any of these satisfy any of your requirements?

15 GBP - Datel Wireless and Network Adaptor (Xbox 360)
http://amzn.eu/6Bi93OR

15 USD - TP- Link Wireless USB Adapter
http://a.co/8Qjf8gN
-- 
-alfred


Re: want.html wifi stsp@

2017-11-21 Thread Stefan Sperling
On Tue, Nov 21, 2017 at 12:40:32PM +0100, Marcus MERIGHI wrote:
> I found:
> 
> Panasonic TYWL20U Wireless LAN Adaptor  EUR 137,--
 
> But cannot afford to just hit "buy" atm. 

Beware, unfortunately there are some seriously overpriced offers for
this type of hardware. I think it's a shame. The hardware by itself
isn't nearly worth that much.

The expensive offers I've been shown are either for products tied to a
specific brand of equipment (e.g. Panasonic, Sony), or they come from shops
selling originally cheap but now suddenly very expensive rebranded devices
"certified" compatible with some "linux-libre" OS. This is taking advantage
of people who believe in software freedom but lack the expertise or community
support to choose their hardware accordingly.

I have already turned down an offer from someone who wanted to buy a device
from such a linux-libre shop for me. In my opinion, shops with such enormously
overblown prices are in opposition to ethical values implied by free software,
such as fairness and co-operation.

Should it turn out that these devices aren't cheaply and widely available
because they're being scooped up by such shops, this would call efforts for
supporting the open firmware into question.
These devices are supposed to be a commodity, not expensive toys.

Reasonable prices would be in the 10-30 Euro range.



Re: want.html wifi stsp@

2017-11-21 Thread Jesper Wallin
Hi Marcus,

I ordered a "TP-Link TL-WN821N" yesterday with the hopes of it
containing the AR7010 chip.  It will most likely arrive tomorrow or the
day after, if it contains what we want, it will be forwarded to stsp@.


Regards,
Jesper Wallin


On Tue, Nov 21, 2017 at 12:40:32PM +0100, Marcus MERIGHI wrote:
> 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



want.html wifi stsp@

2017-11-21 Thread Marcus MERIGHI
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