adrian 334291414b Break out the "memory" EEPROM data read method from being AR9130 specific ... to being more generic. Other embedded SoCs also throw the configuration/PCI register info into flash. For now I'm just hard-coding the AR9280 option (for on-board AR9220's on AP94 and commercial designs (eg D-Link DIR-825.)) TODO: * Figure out how to support it for all 11n SoC NICs by doing it in ar5416InitState(); * Don't hard-code the EEPROM size - add another field which is set by the relevant chip initialisation code. * 'owl_eep_start_loc' may need to be overridden in some cases to 0x0. I need to do some further digging.		2012-01-15 19:22:34 +00:00
..
ar9130_attach.c	Break out the "memory" EEPROM data read method from being AR9130 specific	2012-01-15 19:22:34 +00:00
ar9130_eeprom.c	Break out the "memory" EEPROM data read method from being AR9130 specific	2012-01-15 19:22:34 +00:00
ar9130_eeprom.h	Break out the "memory" EEPROM data read method from being AR9130 specific	2012-01-15 19:22:34 +00:00
ar9130_phy.c	Introduce AR9130 (HOWL) WMAC support to the FreeBSD HAL.	2011-04-28 12:47:40 +00:00
ar9130_phy.h	Introduce AR9130 (HOWL) WMAC support to the FreeBSD HAL.	2011-04-28 12:47:40 +00:00
ar9130.ini	Introduce AR9130 (HOWL) WMAC support to the FreeBSD HAL.	2011-04-28 12:47:40 +00:00
ar9130reg.h	Introduce AR9130 (HOWL) WMAC support to the FreeBSD HAL.	2011-04-28 12:47:40 +00:00
ar9160_attach.c	Implement the first part of the BB read workaround.	2011-10-18 03:01:41 +00:00
ar9160.ini	Add an explanation of the inivals	2011-04-03 11:59:52 +00:00