Re: kern/51644: wifi atheros driver ar9485

[Robert Elz <kre%munnari.OZ.AU@localhost>]

The following reply was made to PR kern/51644; it has been noted by GNATS.

From: Robert Elz <kre%munnari.OZ.AU@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: kern/51644: wifi atheros driver ar9485 
Date: Thu, 24 Nov 2016 07:50:57 +0700

     Date:        Wed, 23 Nov 2016 07:50:00 +0000 (UTC)
     From:        maoamid%yahoo.ro@localhost
     Message-ID:  <20161123075000.3EA757A32C%mollari.NetBSD.org@localhost>
 
   | vendor 0x168c product 0x0036 (miscelanous network, revision 0x01) at pci2 dev 0 function 0 not configured
   | 
   | model founded list here:
   | http://pcidatabase.com/search.php?device_search_str=atheros
   | 
   | A similar problem seems discussed 3 years ago:
   | https://mail-index.netbsd.org/tech-net/2013/12/24/msg004437.html
 
 Similar, but not the same, my chip is (was) reported as ...
 
 vendor 0x168c product 0x0032 (miscellaneous network, revision 0x01) at pci3 dev
 0 function 0 not configured
 
 which is not the same product code,  The pci databases suggest that 0036
 is the  QCA9565 / AR9565 Wireless Network Adapter (sometimes listed as 956x).
 
 There is one weird listing that shows it as
 	Qualcomm Atheros AR9485WB-EG Wireless Network Adapter
 though (though that entry in the database, while found with a search for
 device code 0036, lists the code as 168c - the same as the vendor code - looks
 like a database error of some kind.)
 
 I have not (in the past almost 3 years) even started looking at what is
 needed to support my ar9485 - I have kind of settled into using linux
 and virtualbox, and running NetBSD that way (which mostly works quite well,
 though native NetBSD would be much better).
 
 Now we have better nouveau support, I plan on testing NetBSD again
 sometime soon (but I might need EFI boot to make the test smooth, (don't
 know yet) - I want to try booting from an external USB drive, that is GPT
 partitioned, so I can avoid needing to do anything to disturb the current
 setup - I have already managed to destroy linux's default network config,
 and have no idea how to put that back without a reinstall, I'd like to
 avoid destroying basic booting ...)
 
 But if it (NetBSD & nouveau) works when I test it, then I'll have a need to
 make the wifi work (for short term I can use an external dongle) and when
 that happens, I'll merge as much of the hardware support from the current
 FreeBSD driver as seems to make sense.
 
 But all this is unlikely to happen this year.
 
 kre