| /linux/drivers/ata/pata_parport/ |
| H A D | Kconfig | 15 tristate "MicroSolutions backpack (Series 5) protocol"
19 parallel port Series 5 IDE protocol. (Most BACKPACK drives made
20 before 1999 were Series 5) Series 5 drives will NOT always have the
21 Series noted on the bottom of the drive. Series 6 drivers will.
23 In other words, if your BACKPACK drive doesn't say "Series 6" on the
27 tristate "MicroSolutions backpack (Series 6) protocol"
31 parallel port Series 6 IDE protocol. (Most BACKPACK drives made
32 after 1999 were Series 6) Series 6 drives will have the Series noted
33 on the bottom of the drive. Series 5 drivers don't always have it
36 In other words, if your BACKPACK drive says "Series 6" on the
|
| /linux/arch/m68k/include/asm/ |
| H A D | machines.h | 46 #define SM_3_160 0x01 /* Sun 3/160 series */
47 #define SM_3_50 0x02 /* Sun 3/50 series */
48 #define SM_3_260 0x03 /* Sun 3/260 series */
49 #define SM_3_110 0x04 /* Sun 3/110 series */
50 #define SM_3_60 0x07 /* Sun 3/60 series */
51 #define SM_3_E 0x08 /* Sun 3/E series */
54 #define SM_3_460 0x01 /* Sun 3/460 (460,470,480) series */
55 #define SM_3_80 0x02 /* Sun 3/80 series */
58 #define SM_4_260 0x01 /* Sun 4/200 series */
59 #define SM_4_110 0x02 /* Sun 4/100 series */
[all …]
|
| /linux/Documentation/devicetree/bindings/hwmon/ |
| H A D | moortec,mr75203.yaml | 32 Some of the units have number of series, each series can have slightly
94 moortec,ts-series:
106 Default for series 5 = 60000
107 Default for series 6 = 57400
115 Default for series 5 = 200000
116 Default for series 6 = 249400
124 Default for series 5 = 4094
125 Default for series 6 = 4096
132 Default for series 5 = -100
133 Default for series 6 = 0
|
| /linux/drivers/phy/samsung/ |
| H A D | Kconfig | 6 tristate "Exynos SoC series Display Port PHY driver"
15 tristate "S5P/Exynos SoC series MIPI CSI-2/DSI PHY driver"
29 Enable PCIe PHY support for Exynos SoC series.
33 tristate "Exynos SoC series UFS PHY driver"
43 tristate "S5P/Exynos SoC series USB 2.0 PHY driver"
81 tristate "Exynos5 SoC series USB DRD PHY driver"
90 Enable USB DRD PHY support for Exynos 5 SoC series.
92 present on Exynos5 SoC series.
|
| /linux/Documentation/scsi/ |
| H A D | scsi-generic.rst | 28 - sg version 2 from lk 2.2.6 in the 2.2 series. It is based on
30 - sg version 3 found in the lk 2.4 series (and the lk 2.5 series).
40 This describes the sg version 3 driver found in the lk 2.4 series.
43 lk 2.2 series can be found at
66 Both packages will work in the lk 2.4 series. However, sg3_utils offers more
76 Here is a list of Linux kernels in the 2.4 series that had the new version
87 For reference here is a list of Linux kernels in the 2.2 series that had
99 The lk 2.5 development series currently contains sg version 3.5.23
|
| /linux/drivers/thermal/st/ |
| H A D | Kconfig | 7 tristate "Thermal sensors on STMicroelectronics STi series of SoCs"
9 Support for thermal sensors on STMicroelectronics STi series of SoCs.
13 tristate "STi series memory mapped access based thermal sensors"
16 tristate "Thermal framework support on STMicroelectronics STM32 series of SoCs"
20 Support for thermal framework on STMicroelectronics STM32 series of
|
| /linux/arch/m68k/sun3/ |
| H A D | idprom.c | 33 { .name = "Sun 3/160 Series", .id_machtype = (SM_SUN3 | SM_3_160) },
35 { .name = "Sun 3/260 Series", .id_machtype = (SM_SUN3 | SM_3_260) },
36 { .name = "Sun 3/110 Series", .id_machtype = (SM_SUN3 | SM_3_110) },
40 { .name = "Sun 3/460 Series", .id_machtype = (SM_SUN3X | SM_3_460) },
43 // { .name = "Sun 4/100 Series", .id_machtype = (SM_SUN4 | SM_4_110) },
44 // { .name = "Sun 4/200 Series", .id_machtype = (SM_SUN4 | SM_4_260) },
45 // { .name = "Sun 4/300 Series", .id_machtype = (SM_SUN4 | SM_4_330) },
46 // { .name = "Sun 4/400 Series", .id_machtype = (SM_SUN4 | SM_4_470) },
|
| /linux/Documentation/devicetree/bindings/iio/pressure/ |
| H A D | honeywell,hsc030pa.yaml | 7 title: Honeywell TruStability HSC and SSC pressure sensor series
11 series.
17 The vendor calls them "HSC series" and "SSC series". All of them have an
34 …nsors/board-mount-pressure-sensors/trustability-hsc-series/documents/sps-siot-trustability-hsc-ser…
35 …nsors/board-mount-pressure-sensors/trustability-ssc-series/documents/sps-siot-trustability-ssc-ser…
|
| /linux/Documentation/process/ |
| H A D | maintainer-kvm-x86.rst | 67 room for the size of a series, patches that are "cache hot", etc. Fixes,
80 on series that break the build or fail tests lead to unhappy maintainers!
98 The only exception to using ``kvm-x86/next`` as the base is if a patch/series
99 is a multi-arch series, i.e. has non-trivial modifications to common KVM code
101 arch patch/series should instead be based on a common, stable point in KVM's
103 you're unsure whether a patch/series is truly multi-arch, err on the side of
112 :ref:`maintainer-tip-coding-style`, as patches/series often touch both KVM and
211 E.g. when doing a series of "git blame", the details of each change along the
245 At a bare minimum, *all* patches in a series must build cleanly for KVM_INTEL=m
317 Do not explicitly reference bug reports, prior versions of a patch/series, etc.
[all …]
|
| H A D | maintainer-netdev.rst | 14 - don't post large series (> 15 patches), break them up
166 the mailing list. For example to mark a series as Changes Requested
171 As a result the bot will set the entire series to Changes Requested.
172 This may be useful when author discovers a bug in their own series
245 Please always resend the entire patch series and make sure you do number your
252 Occasionally a patch series gets applied before receiving critical feedback,
253 or the wrong version of a series gets applied.
258 the patches the way they would look like if your latest patch series was to be
295 should generally come as one series. If series becomes too large
301 user space patches should form separate series (threads) when posted
[all …]
|
| /linux/Documentation/arch/arm/spear/ |
| H A D | overview.rst | 19 - SPEAr3XX (3XX SOC series, based on ARM9)
26 - SPEAr6XX (6XX SOC series, based on ARM9)
29 - SPEAr13XX (13XX SOC series, based on ARM CORTEXA9)
52 Each machine series have a directory with name arch/arm/mach-spear followed by
53 series name. Like mach-spear3xx, mach-spear6xx and mach-spear13xx.
|
| /linux/drivers/scsi/bfa/ |
| H A D | bfad_attr.c | 8 * Linux driver for QLogic BR-series Fibre Channel Host Bus Adapter.
747 "QLogic BR-series 4Gbps PCIe dual port FC HBA"); in bfad_im_model_desc_show()
750 "QLogic BR-series 8Gbps PCIe dual port FC HBA"); in bfad_im_model_desc_show()
753 "QLogic BR-series 4Gbps PCIe dual port FC HBA for HP"); in bfad_im_model_desc_show()
756 "QLogic BR-series 8Gbps PCIe dual port FC HBA for HP"); in bfad_im_model_desc_show()
759 "QLogic BR-series 10Gbps single port CNA"); in bfad_im_model_desc_show()
762 "QLogic BR-series 10Gbps dual port CNA"); in bfad_im_model_desc_show()
765 "QLogic BR-series 10Gbps CNA for IBM Blade Center"); in bfad_im_model_desc_show()
768 "QLogic BR-series 4Gbps PCIe single port FC HBA"); in bfad_im_model_desc_show()
771 "QLogic BR-series 8Gbps PCIe single port FC HBA"); in bfad_im_model_desc_show()
[all …]
|
| /linux/sound/firewire/ |
| H A D | Kconfig | 33 * Midas Klark Teknik VeniceF series
54 * Mackie(Loud) Onyx-i series (former models)
108 * Behringer Digital Mixer X32 series (X-UF Card)
151 tristate "TASCAM FireWire series support"
164 tristate "Mark of the unicorn FireWire series support"
191 tristate "RME Fireface series support"
195 Say Y here to include support for RME fireface series.
|
| /linux/arch/loongarch/kernel/ |
| H A D | mcount_dyn.S | 25 * that the T series regs are available and safe because each C functions
91 * As we didn't use S series regs in this assmembly code and all calls
92 * are C function which will save S series regs by themselves, there is
93 * no need to restore S series regs. The T series is available and safe
94 * at the callsite, so there is no need to restore the T series regs.
|
| /linux/drivers/comedi/drivers/ni_routing/ |
| H A D | README | 62 (a) ni_route_values/ni_[series-label]series.c
229 NI_CtrA(0) G0_A_Select see M-Series user
231 NI_CtrA(1) G1_A_Select see M-Series user
233 NI_CtrB(0) G0_B_Select, up/down see M-Series user
235 NI_CtrB(1) G1_B_Select, up/down see M-Series user
237 NI_CtrZ(0) see M-Series user
239 NI_CtrZ(1) see M-Series user
|
| /linux/Documentation/fb/ |
| H A D | sisfb.rst | 8 - SiS 300 series: SiS 300/305, 540, 630(S), 730(S)
9 - SiS 315 series: SiS 315/H/PRO, 55x, (M)65x, 740, (M)661(F/M)X, (M)741(GX)
10 - SiS 330 series: SiS 330 ("Xabre"), (M)760
18 driver for the 315 series).
20 On the 300 series, sisfb on kernels older than 2.6.3 furthermore plays an
138 is in kilobytes. On 300 series, the default is 4096, 8192 or
140 has. On 315/330 series, the default is the maximum available ram
|
| /linux/drivers/net/ethernet/brocade/bna/ |
| H A D | Kconfig | 3 # QLogic BR-series network device configuration
7 tristate "QLogic BR-series 1010/1020/1860 10Gb Ethernet Driver support"
10 This driver supports QLogic BR-series 1010/1020/1860 10Gb CEE capable
|
| /linux/drivers/net/ethernet/brocade/ |
| H A D | Kconfig | 3 # QLogic BR-series device configuration
7 bool "QLogic BR-series devices"
15 the questions about QLogic BR-series cards. If you say Y, you will be
|
| /linux/drivers/net/wireless/ath/ath5k/ |
| H A D | desc.h | 251 #define AR5K_4W_TX_DESC_CTL2_XMIT_TRIES0 0x000f0000 /* series 0 max attempts */
253 #define AR5K_4W_TX_DESC_CTL2_XMIT_TRIES1 0x00f00000 /* series 1 max attempts */
255 #define AR5K_4W_TX_DESC_CTL2_XMIT_TRIES2 0x0f000000 /* series 2 max attempts */
257 #define AR5K_4W_TX_DESC_CTL2_XMIT_TRIES3 0xf0000000 /* series 3 max attempts */
261 #define AR5K_4W_TX_DESC_CTL3_XMIT_RATE0 0x0000001f /* series 0 tx rate */
262 #define AR5K_4W_TX_DESC_CTL3_XMIT_RATE1 0x000003e0 /* series 1 tx rate */
264 #define AR5K_4W_TX_DESC_CTL3_XMIT_RATE2 0x00007c00 /* series 2 tx rate */
266 #define AR5K_4W_TX_DESC_CTL3_XMIT_RATE3 0x000f8000 /* series 3 tx rate */
306 #define AR5K_DESC_TX_STATUS1_FINAL_TS_IX_5212 0x00600000 /* [5212] final TX attempt series ix */
|
| /linux/arch/arm/boot/dts/intel/ixp/ |
| H A D | intel-ixp43x.dtsi | 4 * in the IXP 43x series. This series has 64 interrupts and adds a few more
5 * peripherals over the 42x series.
|
| /linux/drivers/net/wireless/intel/iwlwifi/ |
| H A D | Kconfig | 14 Intel 6000 Series Wi-Fi Adapters (6200AGN and 6300AGN)
18 Intel 6005 Series Wi-Fi Adapters
19 Intel 6030 Series Wi-Fi Adapters
21 Intel 100 Series Wi-Fi Adapters (100BGN and 130BGN)
22 Intel 2000 Series Wi-Fi Adapters
|
| /linux/drivers/eisa/ |
| H A D | eisa.ids | 42 ACR3221 "AcerFrame 486 Series SYSTEM-2"
43 ACR3231 "AcerFrame 486 Series SYSTEM-3"
44 ACR3241 "AcerFrame 486 Series SYSTEM-4"
46 ACR3271 "AcerFrame 486 Series SYSTEM-2"
47 ACR3281 "AcerFrame 486 Series SYSTEM-3"
48 ACR3291 "AcerFrame 486 Series SYSTEM-4"
93 AMI44C1 "AMI SCSI Host Adapter - Series 44"
102 AMI4801 "AMI Series 48 EISA Fast SCSI Host Adapter"
423 DEC1031 "DECpc MTE Series System Board"
563 HWPC000 "Series 700 EISA System Board"
[all …]
|
| /linux/Documentation/maintainer/ |
| H A D | rebasing-and-merging.rst | 25 "Rebasing" is the process of changing the history of a series of commits
30 - Changing the parent (starting) commit upon which a series of patches is
75 series must move to a new base, pick a stable point (such as one of
78 - Realize that reparenting a patch series (or making significant history
81 patch series should, as a general rule, be treated like new code and
85 patch series that has clearly been reparented, often to a random commit,
86 shortly before the pull request was sent. The chances of such a series
|
| /linux/drivers/atm/ |
| H A D | Kconfig | 44 Driver for the Efficient Networks ENI155p series and SMC ATM
131 such as the Intel Neptune series.
155 series. Say Y if you have one of those.
252 tristate "FORE Systems 200E-series"
256 This is a driver for the FORE Systems 200E-series ATM adapter
305 tristate "ForeRunner HE Series"
308 This is a driver for the Marconi ForeRunner HE-series ATM adapter
|
| /linux/Documentation/i2c/busses/ |
| H A D | i2c-ismt.rst | 7 * Intel S12xx series SOCs
37 The S12xx series of SOCs have a pair of integrated SMBus 2.0 controllers
40 The S12xx series contain a pair of PCI functions. An output of lspci will show
|