#
6a068746 |
| 15-May-2012 |
Alexander Motin <mav@FreeBSD.org> |
MFC
|
#
3d328873 |
| 30-Apr-2012 |
Gleb Smirnoff <glebius@FreeBSD.org> |
Merge head r233826 through r234834.
|
#
38f1b189 |
| 26-Apr-2012 |
Peter Grehan <grehan@FreeBSD.org> |
IFC @ r234692
sys/amd64/include/cpufunc.h sys/amd64/include/fpu.h sys/amd64/amd64/fpu.c sys/amd64/vmm/vmm.c
- Add API to allow vmm FPU state init/save/restore.
FP stuff discussed with: kib
|
#
b890549d |
| 15-Apr-2012 |
Adrian Chadd <adrian@FreeBSD.org> |
Override some default values to work around various issues in the deep, dirty and murky past.
* Override the default cache line size to be something reasonable if it's set to 0. Some NICs initial
Override some default values to work around various issues in the deep, dirty and murky past.
* Override the default cache line size to be something reasonable if it's set to 0. Some NICs initialise with '0' (eg embedded ones) and there are comments in the driver stating that various OSes (eg older Linux ones) would incorrectly program things and 0 out this register.
* Just default to overriding the latency timer. Every other driver does this.
* Use a default cache line size of 32 bytes. It should be "reasonable enough".
Obtained from: Linux ath9k, Atheros
show more ...
|
#
79f57b35 |
| 13-Apr-2012 |
Adrian Chadd <adrian@FreeBSD.org> |
Upgrade ATH_EEPROM_FIRMWARE to a configuration option.
|
#
0f60da6f |
| 13-Apr-2012 |
Adrian Chadd <adrian@FreeBSD.org> |
Introduce the ability to grab local EEPROM data from the firmware(9) interface.
* Introduce a device hint, 'eeprom_firmware', which is the name of firmware to lookup. * If the lookup succeeds, tak
Introduce the ability to grab local EEPROM data from the firmware(9) interface.
* Introduce a device hint, 'eeprom_firmware', which is the name of firmware to lookup. * If the lookup succeeds, take a copy of it and use it as the eeprom data.
This isn't enabled by default - you have to define ATH_EEPROM_FIRMWARE. I'll add it to the configuration variables in a later commit.
TODO:
* just keep a firmware reference in ath_softc, and remove the need to waste the extra memory in having sc_eepromdata be a malloc()ed block.
show more ...
|
Revision tags: release/8.3.0_cvs, release/8.3.0 |
|
#
8fa0b743 |
| 23-Jan-2012 |
Xin LI <delphij@FreeBSD.org> |
IFC @230489 (pending review).
|
Revision tags: release/9.0.0 |
|
#
3ee1a36e |
| 22-Nov-2011 |
Peter Grehan <grehan@FreeBSD.org> |
IFC @ r227804
Pull in the virtio drivers from head.
|
#
0f0c074e |
| 08-Nov-2011 |
Adrian Chadd <adrian@FreeBSD.org> |
Conditionally compile the PCI latency workaround; I think it's only required for some earlier NICs.
|
#
3dd85b26 |
| 08-Nov-2011 |
Adrian Chadd <adrian@FreeBSD.org> |
Begin merging in some of my 802.11n TX aggregation driver changes.
* Add a PCU lock, which isn't currently used but will eventually be used to serialise some of the driver access.
* Add in all th
Begin merging in some of my 802.11n TX aggregation driver changes.
* Add a PCU lock, which isn't currently used but will eventually be used to serialise some of the driver access.
* Add in all the software TX aggregation state, that's kept per-node and per-TID.
* Add in the software and aggregation state to ath_buf.
* Add in hooks to ath_softc for aggregation state and the (upcoming) aggregation TX state calls.
* Add / fix the HAL access macros.
Obtained from: Linux, ath9k Sponsored by: Hobnob, Inc.
show more ...
|
#
70d8f36a |
| 27-Oct-2011 |
Peter Grehan <grehan@FreeBSD.org> |
IFC @ r226824
|
#
2c0dd4bb |
| 18-Oct-2011 |
Adrian Chadd <adrian@FreeBSD.org> |
Add in a currently-disabled WAR for PCI NICs.
Some earlier series (~AR5212?) play badly with BIOSes.
In these instances, they may require a forced reset (by transitioning the NIC through D0 -> D3 -
Add in a currently-disabled WAR for PCI NICs.
Some earlier series (~AR5212?) play badly with BIOSes.
In these instances, they may require a forced reset (by transitioning the NIC through D0 -> D3 -> D0) before they probe/attach correctly.
This is currently disabled because:
* I haven't figured out the "right" code to ensure this only happens for PCI NICs (not PCIe or Cardbus); * I haven't at all done wide scale testing for this, and I'm not yet ready for said wide-scale testing.
I'm documenting this primarily so users with misbehaving NICs have something to tinker with.
Obtained from: Atheros
show more ...
|
#
65d1eb94 |
| 18-Oct-2011 |
Adrian Chadd <adrian@FreeBSD.org> |
Add a WAR from the reference code - clear the PCI error status upon detach.
Obtained from: Atheros
|
#
cdd36f96 |
| 14-Oct-2011 |
Adrian Chadd <adrian@FreeBSD.org> |
ath_pci PCI setup fixes.
* Break out the PCI setup override code into a new function. * Re-apply the PCI overrides on powersave resume. The retry timeout register isn't currently being saved/resum
ath_pci PCI setup fixes.
* Break out the PCI setup override code into a new function. * Re-apply the PCI overrides on powersave resume. The retry timeout register isn't currently being saved/resumed by the PCI driver/bus code.
show more ...
|
#
dba9c859 |
| 31-Mar-2011 |
Adrian Chadd <adrian@FreeBSD.org> |
Break out the ath PCI logic into a separate device/module.
Introduce the AHB glue for Atheros embedded systems. Right now it's hard-coded for the AR9130 chip whose support isn't yet in this HAL; it'
Break out the ath PCI logic into a separate device/module.
Introduce the AHB glue for Atheros embedded systems. Right now it's hard-coded for the AR9130 chip whose support isn't yet in this HAL; it'll be added in a subsequent commit.
Kernel configuration files now need both 'ath' and 'ath_pci' devices; both modules need to be loaded for the ath device to work.
show more ...
|
Revision tags: release/7.4.0_cvs, release/8.2.0_cvs, release/7.4.0, release/8.2.0, release/8.1.0_cvs, release/8.1.0, release/7.3.0_cvs, release/7.3.0, release/8.0.0_cvs, release/8.0.0 |
|
#
10b3b545 |
| 17-Sep-2009 |
Dag-Erling Smørgrav <des@FreeBSD.org> |
Merge from head
|
#
7d4b968b |
| 17-Sep-2009 |
Dag-Erling Smørgrav <des@FreeBSD.org> |
Merge from head up to r188941 (last revision before the USB stack switch)
|
#
2e370a5c |
| 26-May-2009 |
Oleksandr Tymoshenko <gonzo@FreeBSD.org> |
Merge from HEAD
|
#
b8f5836a |
| 15-May-2009 |
Warner Losh <imp@FreeBSD.org> |
The module name convention is foo, not if_foo.
|
Revision tags: release/7.2.0_cvs, release/7.2.0 |
|
#
1829d5da |
| 12-Mar-2009 |
Warner Losh <imp@FreeBSD.org> |
Update the projects tree to a newer FreeBSD current.
|
#
155a83e8 |
| 09-Mar-2009 |
Warner Losh <imp@FreeBSD.org> |
remove now-redunant cardbus attachment.
|
#
50666d87 |
| 06-Jan-2009 |
Sam Leffler <sam@FreeBSD.org> |
remove the ath_rate module dependency; it's all bundled
|
Revision tags: release/7.1.0_cvs, release/7.1.0 |
|
#
e57c2b13 |
| 04-Dec-2008 |
Dag-Erling Smørgrav <des@FreeBSD.org> |
integrate from head@185615
|
#
33644623 |
| 01-Dec-2008 |
Sam Leffler <sam@FreeBSD.org> |
Switch to ath hal source code. Note this removes the ath_hal module; the ath module now brings in the hal support. Kernel config files are almost backwards compatible; supplying
device ath_hal
giv
Switch to ath hal source code. Note this removes the ath_hal module; the ath module now brings in the hal support. Kernel config files are almost backwards compatible; supplying
device ath_hal
gives you the same chip support that the binary hal did but you must also include
options AH_SUPPORT_AR5416
to enable the extended format descriptors used by 11n parts. It is now possible to control the chip support included in a build by specifying exactly which chips are to be supported in the config file; consult ath_hal(4) for information.
show more ...
|
Revision tags: release/6.4.0_cvs, release/6.4.0 |
|
#
b032f27c |
| 20-Apr-2008 |
Sam Leffler <sam@FreeBSD.org> |
Multi-bss (aka vap) support for 802.11 devices.
Note this includes changes to all drivers and moves some device firmware loading to use firmware(9) and a separate module (e.g. ral). Also there no l
Multi-bss (aka vap) support for 802.11 devices.
Note this includes changes to all drivers and moves some device firmware loading to use firmware(9) and a separate module (e.g. ral). Also there no longer are separate wlan_scan* modules; this functionality is now bundled into the wlan module.
Supported by: Hobnob and Marvell Reviewed by: many Obtained from: Atheros (some bits)
show more ...
|