Specifications of Qualcomm Atheros network cards

Question about which tools to use, bugs, the best way to implement a function, etc should go here. Don't forget to see if your question is answered in the wiki first! When in doubt post here.
Post Reply
Klakap
Member
Member
Posts: 299
Joined: Sat Mar 10, 2018 10:16 am

Specifications of Qualcomm Atheros network cards

Post by Klakap »

After much searching for usable specifications of Atheros network cards, I found this page: https://github.com/Deoptim/atheros/tree/master It seems that here are all (or almost all) specifications, and they contains informations that driver developer needs to write a functional driver, not just some info about circuits or similar things. However there is one problem. These files are marked as “COMPANY CONFIDENTIAL”, so for me it feels like existence of these files on public place/using these files is illegal. However if it would be somehow possible to use them, it would be big help for implementing drivers for Atheros cards (what would include wireless connection). So I would like to at least ask more experienced people, if it is really illegal to use these files, or is there maybe some way to use them without making contract with company?
User avatar
zaval
Member
Member
Posts: 660
Joined: Fri Feb 17, 2017 4:01 pm
Location: Ukraine, Bachmut
Contact:

Re: Specifications of Qualcomm Atheros network cards

Post by zaval »

The answer is "pfff, come on, just use it".
ANT - NT-like OS for x64 and arm64.
efify - UEFI for a couple of boards (mips and arm). suspended due to lost of all the target park boards (russians destroyed our town).
rdos
Member
Member
Posts: 3311
Joined: Wed Oct 01, 2008 1:55 pm

Re: Specifications of Qualcomm Atheros network cards

Post by rdos »

I'd even claim "download quickly before it's gone". I searched for this to a while ago but couldn't find it. Apparently, this company don't want people to write drivers, rather prefer to do this themselves for Windows and possibly Linux. This typically leads to poor drivers since hardware developers are not device driver experts.
Post Reply