/freebsd-src/sys/dev/ath/ath_hal/ah_regdomain/ |
H A D | ah_rd_regenum.h | 34 * can operate in either a 5GHz or 2.4GHz wireless mode or 35 * both 5GHz and 2.4GHz wireless modes. 38 * 2.4GHz or 5GHz wireless mode for that particular 95 APL8_WORLD = 0x5D, /* Malaysia 5GHz */ 96 APL9_WORLD = 0x5E, /* Korea 5GHz; before 11/2007; now APs only */ 97 APL10_WORLD = 0x5F, /* Korea 5GHz; After 11/2007; STAs only */ 142 MKK14_MKKA1 = 0x92, /* Japan UNI-1 even + UNI-1 odd + 4.9GHz + MKKA1 */ 143 MKK15_MKKA1 = 0x93, /* Japan UNI-1 even + UNI-1 odd + UNI-2 + 4.9GHz + MKKA1 */ 145 MKK10_FCCA = 0xD0, /* Japan UNI-1 even + UNI-2 + 4.9GHz + FCCA */ 146 MKK10_MKKA1 = 0xD1, /* Japan UNI-1 even + UNI-2 + 4.9GHz + MKKA1 */ [all …]
|
/freebsd-src/sys/x86/cpufreq/ |
H A D | est.c | 128 /* 130nm 1.70GHz Pentium M */ 137 /* 130nm 1.60GHz Pentium M */ 146 /* 130nm 1.50GHz Pentium M */ 155 /* 130nm 1.40GHz Pentium M */ 163 /* 130nm 1.30GHz Pentium M */ 171 /* 130nm 1.30GHz Low Voltage Pentium M */ 181 /* 130 nm 1.20GHz Low Voltage Pentium M */ 190 /* 130 nm 1.10GHz Low Voltage Pentium M */ 198 /* 130 nm 1.10GHz Ultra Low Voltage Pentium M */ 206 /* 130 nm 1.00GHz Ultra Low Voltage Pentium M */ [all …]
|
/freebsd-src/sys/contrib/device-tree/src/arm/broadcom/ |
H A D | bcm47094-netgear-r8500.dts | 39 led-5ghz-1 { 40 label = "bcm53xx:white:5ghz-1"; 44 led-5ghz-2 { 45 label = "bcm53xx:white:5ghz-2"; 49 led-2ghz { 50 label = "bcm53xx:white:2ghz";
|
H A D | bcm47081-luxul-xap-1410.dts | 34 led-5ghz { 35 label = "bcm53xx:blue:5ghz"; 40 led-2ghz { 41 label = "bcm53xx:blue:2ghz";
|
H A D | bcm4708-luxul-xap-1510.dts | 34 led-5ghz { 35 label = "bcm53xx:blue:5ghz"; 40 led-2ghz { 41 label = "bcm53xx:blue:2ghz";
|
H A D | bcm4709-netgear-r8000.dts | 64 led-5ghz-1 { 65 label = "bcm53xx:white:5ghz-1"; 69 led-2ghz { 70 label = "bcm53xx:white:2ghz"; 84 led-5ghz-2 { 85 label = "bcm53xx:white:5ghz-2";
|
H A D | bcm947189acdbmr.dts | 33 led-5ghz { 34 label = "bcm53xx:blue:5ghz"; 38 led-2ghz { 39 label = "bcm53xx:blue:2ghz";
|
H A D | bcm47189-luxul-xap-810.dts | 26 led-5ghz { 27 label = "bcm53xx:blue:5ghz"; 41 led-2ghz { 42 label = "bcm53xx:blue:2ghz";
|
H A D | bcm4709-netgear-r7000.dts | 42 led-5ghz { 43 label = "bcm53xx:white:5ghz"; 47 led-2ghz { 48 label = "bcm53xx:white:2ghz";
|
H A D | bcm47081-tplink-archer-c5-v2.dts | 26 led-2ghz { 27 label = "bcm53xx:green:2ghz"; 64 led-5ghz { 65 label = "bcm53xx:green:5ghz";
|
H A D | bcm4709-tplink-archer-c9-v1.dts | 36 led-2ghz { 37 label = "bcm53xx:blue:2ghz"; 41 led-5ghz { 42 label = "bcm53xx:blue:5ghz";
|
H A D | bcm47094-luxul-xap-1610.dts | 40 led-2ghz { 41 label = "bcm53xx:blue:2ghz"; 45 led-5ghz { 46 label = "bcm53xx:blue:5ghz";
|
H A D | bcm47094-luxul-xwr-3100.dts | 82 led-2ghz { 83 label = "bcm53xx:green:2ghz"; 87 led-5ghz { 88 label = "bcm53xx:green:5ghz";
|
H A D | bcm47189-tenda-ac9.dts | 38 led-5ghz { 39 label = "bcm53xx:blue:5ghz"; 53 led-2ghz { 54 label = "bcm53xx:blue:2ghz";
|
/freebsd-src/share/man/man4/ |
H A D | otus.4 | 49 radio to operate in either 2.4GHz only or 2.4GHz and 5GHz. 51 The AR9101 radio supports 1T1R operation in 2GHz only. 53 The AR9102 radio supports 2T2R operation in 2GHz only. 55 The AR9104 radio supports 2T2R operation both 2GHz and 5GHz.
|
H A D | ral.4 | 70 an RT2720 (2.4GHz) or RT2750 (2.4GHz/5GHz) radio transceiver. 74 an RT2820 (2.4GHz) or RT2850 (2.4GHz/5GHz) radio transceiver. 110 The RT5390 chip operates in the 2GHz spectrum and supports 1 transmit path 112 The RT5392 chip operates in the 2GHz spectrum and supports up to 2 transmit
|
H A D | run.4 | 71 The RT3053 chip operates in the 2GHz and 5GHz spectra and supports up to 73 The RT5370 chip operates in the 2GHz spectrum and supports 1 transmit path 75 The RT5372 chip operates in the 2GHz spectrum and supports up to 2 transmit 77 The RT5572 chip operates in the 2GHz and 5GHz spectra and supports up to
|
/freebsd-src/sys/contrib/device-tree/src/arm64/broadcom/bcm4908/ |
H A D | bcm4906-netgear-r8000p.dts | 39 led-2ghz { 40 function = "2ghz"; 45 led-5ghz-1 { 46 function = "5ghz-1"; 51 led-5ghz-2 { 52 function = "5ghz-2";
|
/freebsd-src/sys/contrib/device-tree/src/arm64/broadcom/bcmbca/ |
H A D | bcm4906-netgear-r8000p.dts | 39 led-2ghz { 40 function = "2ghz"; 45 led-5ghz-1 { 46 function = "5ghz-1"; 51 led-5ghz-2 { 52 function = "5ghz-2";
|
/freebsd-src/sys/dev/rtwn/rtl8812a/ |
H A D | r12a_priv.h | 176 * * External 2GHz PA, type 0; 177 * * External 5GHz PA, type 0 or 5; 178 * * External 2GHz LNA, type 0 or 5; 179 * * External 5GHz LNA, type 0; 286 * External 2GHz LNA (type 0). 293 * External 2GHz LNA (type 5). 311 * External 5GHz LNA (type 0). 499 /* External 2GHz LNA, type 0 or 5. */ 517 /* External 5GHz LNA, type 0. */ 539 /* External 2GHz LNA, type 0 or 5. */ [all …]
|
/freebsd-src/sys/contrib/dev/iwlwifi/fw/api/ |
H A D | scan.h | 350 * @tx_cmd: tx command for active scan; for 2GHz and for 5GHz 391 * @band: 0 for 5.2 GHz, 1 for 2.4 GHz 681 * @IWL_UMAC_SCAN_GEN_FLAGS_V2_TRIGGER_UHB_SCAN: at the end of 2.4GHz and 682 * 5.2Ghz bands scan, trigger scan on 6GHz band to discover 684 * @IWL_UMAC_SCAN_GEN_FLAGS_V2_6GHZ_PASSIVE_SCAN: at the end of 2.4GHz and 5GHz 686 * 6GHz PS [all...] |
/freebsd-src/sys/contrib/dev/mediatek/mt76/mt7996/ |
H A D | Kconfig | 11 which support concurrent tri-band operation at 6GHz, 5GHz, 12 and 2.4GHz IEEE 802.11be 4x4:4SS 4096-QAM, 320MHz channels.
|
/freebsd-src/tools/tools/ath/ath_ee_v14_print/ |
H A D | ath_ee_v14_print.c | 256 /* 2ghz cal piers */ in eeprom_v14_calfreqpiers_print() 266 printf("2Ghz Cal Pier %d\n", i); in eeprom_v14_calfreqpiers_print() 278 /* 5ghz cal piers */ in eeprom_v14_calfreqpiers_print() 287 printf("5Ghz Cal Pier %d\n", i); in eeprom_v14_calfreqpiers_print() 330 /* 2ghz rates */ in eeprom_v14_print_targets() 331 printf("2Ghz CCK:\n"); in eeprom_v14_print_targets() 335 printf("2Ghz 11g:\n"); in eeprom_v14_print_targets() 339 printf("2Ghz HT20:\n"); in eeprom_v14_print_targets() 343 printf("2Ghz HT40:\n"); in eeprom_v14_print_targets() 348 /* 5ghz rates */ in eeprom_v14_print_targets() [all …]
|
/freebsd-src/lib/libpmc/pmu-events/arch/x86/ivytown/ |
H A D | uncore-power.json | 187 …les that the uncore was running at a frequency greater than or equal to 1.2Ghz. Derived from unc_p… 198 …ycles that the uncore was running at a frequency greater than or equal to 2Ghz. Derived from unc_p… 209 …ycles that the uncore was running at a frequency greater than or equal to 3Ghz. Derived from unc_p… 220 …ycles that the uncore was running at a frequency greater than or equal to 4Ghz. Derived from unc_p… 231 …es that the uncore transitioned to a frequency greater than or equal to 1.2Ghz. Derived from unc_p… 242 …imes that the uncore transitioned to a frequency greater than or equal to 2Ghz. Derived from unc_p… 253 …cles that the uncore transitioned to a frequency greater than or equal to 3Ghz. Derived from unc_p… 264 …cles that the uncore transitioned to a frequency greater than or equal to 4Ghz. Derived from unc_p…
|
/freebsd-src/lib/libpmc/pmu-events/arch/x86/jaketown/ |
H A D | uncore-power.json | 186 …les that the uncore was running at a frequency greater than or equal to 1.2Ghz. Derived from unc_p… 197 …ycles that the uncore was running at a frequency greater than or equal to 2Ghz. Derived from unc_p… 208 …ycles that the uncore was running at a frequency greater than or equal to 3Ghz. Derived from unc_p… 219 …ycles that the uncore was running at a frequency greater than or equal to 4Ghz. Derived from unc_p… 230 …es that the uncore transitioned to a frequency greater than or equal to 1.2Ghz. Derived from unc_p… 241 …imes that the uncore transitioned to a frequency greater than or equal to 2Ghz. Derived from unc_p… 252 …cles that the uncore transitioned to a frequency greater than or equal to 3Ghz. Derived from unc_p… 263 …cles that the uncore transitioned to a frequency greater than or equal to 4Ghz. Derived from unc_p…
|