Home
last modified time | relevance | path

Searched full:windows (Results 1 – 25 of 1654) sorted by relevance

12345678910>>...67

/kernel/linux/linux-5.10/drivers/usb/serial/
Dipaq.c60 { USB_DEVICE(0x045E, 0x0400) }, /* Windows Powered Pocket PC 2002 */
61 { USB_DEVICE(0x045E, 0x0401) }, /* Windows Powered Pocket PC 2002 */
62 { USB_DEVICE(0x045E, 0x0402) }, /* Windows Powered Pocket PC 2002 */
63 { USB_DEVICE(0x045E, 0x0403) }, /* Windows Powered Pocket PC 2002 */
64 { USB_DEVICE(0x045E, 0x0404) }, /* Windows Powered Pocket PC 2002 */
65 { USB_DEVICE(0x045E, 0x0405) }, /* Windows Powered Pocket PC 2002 */
66 { USB_DEVICE(0x045E, 0x0406) }, /* Windows Powered Pocket PC 2002 */
67 { USB_DEVICE(0x045E, 0x0407) }, /* Windows Powered Pocket PC 2002 */
68 { USB_DEVICE(0x045E, 0x0408) }, /* Windows Powered Pocket PC 2002 */
69 { USB_DEVICE(0x045E, 0x0409) }, /* Windows Powered Pocket PC 2002 */
[all …]
/kernel/linux/linux-4.19/drivers/usb/serial/
Dipaq.c60 { USB_DEVICE(0x045E, 0x0400) }, /* Windows Powered Pocket PC 2002 */
61 { USB_DEVICE(0x045E, 0x0401) }, /* Windows Powered Pocket PC 2002 */
62 { USB_DEVICE(0x045E, 0x0402) }, /* Windows Powered Pocket PC 2002 */
63 { USB_DEVICE(0x045E, 0x0403) }, /* Windows Powered Pocket PC 2002 */
64 { USB_DEVICE(0x045E, 0x0404) }, /* Windows Powered Pocket PC 2002 */
65 { USB_DEVICE(0x045E, 0x0405) }, /* Windows Powered Pocket PC 2002 */
66 { USB_DEVICE(0x045E, 0x0406) }, /* Windows Powered Pocket PC 2002 */
67 { USB_DEVICE(0x045E, 0x0407) }, /* Windows Powered Pocket PC 2002 */
68 { USB_DEVICE(0x045E, 0x0408) }, /* Windows Powered Pocket PC 2002 */
69 { USB_DEVICE(0x045E, 0x0409) }, /* Windows Powered Pocket PC 2002 */
[all …]
/kernel/linux/linux-4.19/Documentation/acpi/
Dosi.txt21 but where Linux was installed to replace the original OS (Windows or OSX).
23 The larger group is the systems tested to run only Windows. Not only that,
24 but many were tested to run with just one specific version of Windows.
25 So even though the BIOS may use _OSI to query what version of Windows is running,
30 with all versions of Windows.
32 But Linux isn't actually compatible with Windows, and the Linux community
34 Windows to its list of _OSI strings. So it is possible that additional strings
38 What should an OEM do if they want to support Linux and Windows
40 for Linux to deal with how Linux is different from Windows.
73 Windows 98, SE: "Microsoft Windows"
[all …]
/kernel/linux/linux-5.10/Documentation/firmware-guide/acpi/
Dosi.rst24 but where Linux was installed to replace the original OS (Windows or OSX).
26 The larger group is the systems tested to run only Windows. Not only that,
27 but many were tested to run with just one specific version of Windows.
28 So even though the BIOS may use _OSI to query what version of Windows is running,
33 with all versions of Windows.
35 But Linux isn't actually compatible with Windows, and the Linux community
37 Windows to its list of _OSI strings. So it is possible that additional strings
41 What should an OEM do if they want to support Linux and Windows
43 for Linux to deal with how Linux is different from Windows.
76 Windows 98, SE: "Microsoft Windows"
[all …]
/kernel/linux/linux-5.10/drivers/acpi/acpica/
Dutosi.c27 * the latest version of Windows, which would respond to the latest/newest
28 * _OSI string. Not responding TRUE to the latest version of Windows will
46 * for this string. Basically, the only safe OS strings are windows-related
51 * Windows that the BIOS has requested.
56 {"Windows 2000", NULL, 0, ACPI_OSI_WIN_2000}, /* Windows 2000 */
57 {"Windows 2001", NULL, 0, ACPI_OSI_WIN_XP}, /* Windows XP */
58 {"Windows 2001 SP1", NULL, 0, ACPI_OSI_WIN_XP_SP1}, /* Windows XP SP1 */
59 {"Windows 2001.1", NULL, 0, ACPI_OSI_WINSRV_2003}, /* Windows Server 2003 */
60 {"Windows 2001 SP2", NULL, 0, ACPI_OSI_WIN_XP_SP2}, /* Windows XP SP2 */
61 …{"Windows 2001.1 SP1", NULL, 0, ACPI_OSI_WINSRV_2003_SP1}, /* Windows Server 2003 SP1 - Added 03/2…
[all …]
/kernel/linux/linux-5.10/drivers/pci/endpoint/
Dpci-epc-mem.c41 * @windows: pointer to windows supported by the device
42 * @num_windows: number of windows device supports
48 struct pci_epc_mem_window *windows, in pci_epc_multi_mem_init() argument
62 if (!windows || !num_windows) in pci_epc_multi_mem_init()
65 epc->windows = kcalloc(num_windows, sizeof(*epc->windows), GFP_KERNEL); in pci_epc_multi_mem_init()
66 if (!epc->windows) in pci_epc_multi_mem_init()
70 page_size = windows[i].page_size; in pci_epc_multi_mem_init()
74 pages = windows[i].size >> page_shift; in pci_epc_multi_mem_init()
92 mem->window.phys_base = windows[i].phys_base; in pci_epc_multi_mem_init()
93 mem->window.size = windows[i].size; in pci_epc_multi_mem_init()
[all …]
/kernel/linux/linux-4.19/drivers/acpi/acpica/
Dutosi.c27 * the latest version of Windows, which would respond to the latest/newest
28 * _OSI string. Not responding TRUE to the latest version of Windows will
46 * for this string. Basically, the only safe OS strings are windows-related
51 * Windows that the BIOS has requested.
56 {"Windows 2000", NULL, 0, ACPI_OSI_WIN_2000}, /* Windows 2000 */
57 {"Windows 2001", NULL, 0, ACPI_OSI_WIN_XP}, /* Windows XP */
58 {"Windows 2001 SP1", NULL, 0, ACPI_OSI_WIN_XP_SP1}, /* Windows XP SP1 */
59 {"Windows 2001.1", NULL, 0, ACPI_OSI_WINSRV_2003}, /* Windows Server 2003 */
60 {"Windows 2001 SP2", NULL, 0, ACPI_OSI_WIN_XP_SP2}, /* Windows XP SP2 */
61 …{"Windows 2001.1 SP1", NULL, 0, ACPI_OSI_WINSRV_2003_SP1}, /* Windows Server 2003 SP1 - Added 03/2…
[all …]
/kernel/linux/linux-4.19/Documentation/usb/
Dgadget_multi.txt37 ** Windows host drivers
39 For the gadget to work under Windows two conditions have to be met:
43 First of all, Windows need to detect the gadget as an USB composite
45 Windows lets USB Generic Parent Driver[5] handle the device which then
58 The other, trickier thing is making Windows install drivers for each
61 For mass storage it is trivial since Windows detect it's an interface
68 To make Windows select RNDIS drivers for the first function in the
96 things don't work as intended before realising Windows have cached
102 Provided INF files have been tested on Windows XP SP3, Windows Vista
103 and Windows 7, all 32-bit versions. It should work on 64-bit versions
[all …]
Dgadget_serial.txt39 Windows and know how to configure and build Linux kernels, run
67 | Windows) Driver USB Stack | |
92 the Windows usbser.sys ACM driver, and the Linux USB generic serial
146 either the Windows or Linux ACM driver on the host side. If gadget
152 Installing the Windows Host ACM Driver
154 To use the Windows ACM driver you must have the "linux-cdc-acm.inf"
156 of Windows.
159 to the Windows host with a USB cable, Windows should recognize the
160 gadget serial device and ask for a driver. Tell Windows to find the
163 For example, on Windows XP, when the gadget serial device is first
[all …]
/kernel/linux/linux-5.10/Documentation/usb/
Dgadget_multi.rst42 Windows host drivers
45 For the gadget to work under Windows two conditions have to be met:
50 First of all, Windows need to detect the gadget as an USB composite
52 Windows lets USB Generic Parent Driver[5] handle the device which then
66 The other, trickier thing is making Windows install drivers for each
69 For mass storage it is trivial since Windows detect it's an interface
77 To make Windows select RNDIS drivers for the first function in the
107 things don't work as intended before realising Windows have cached
114 Provided INF files have been tested on Windows XP SP3, Windows Vista
115 and Windows 7, all 32-bit versions. It should work on 64-bit versions
[all …]
Dgadget_serial.rst42 Windows and know how to configure and build Linux kernels, run
70 | Windows) Driver USB Stack | |
95 the Windows usbser.sys ACM driver, and the Linux USB generic serial
149 either the Windows or Linux ACM driver on the host side. If gadget
155 Installing the Windows Host ACM Driver
157 To use the Windows ACM driver you must have the "linux-cdc-acm.inf"
159 of Windows.
162 to the Windows host with a USB cable, Windows should recognize the
163 gadget serial device and ask for a driver. Tell Windows to find the
166 For example, on Windows XP, when the gadget serial device is first
[all …]
/kernel/linux/linux-5.10/fs/fat/
DKconfig7 VFAT (Windows 95) file systems), then you must say Y or M here
51 If you have Windows 95 or Windows NT installed on your MSDOS
54 generated by Windows 95 / Windows NT.
62 tristate "VFAT (Windows-95) fs support"
65 This option provides support for normal Windows file systems with
67 used by Windows 95, Windows 98, Windows NT 4.0, and the Unix
/kernel/linux/linux-4.19/fs/fat/
DKconfig6 VFAT (Windows 95) file systems), then you must say Y or M here
50 If you have Windows 95 or Windows NT installed on your MSDOS
53 generated by Windows 95 / Windows NT.
61 tristate "VFAT (Windows-95) fs support"
64 This option provides support for normal Windows file systems with
66 used by Windows 95, Windows 98, Windows NT 4.0, and the Unix
/kernel/linux/linux-4.19/arch/powerpc/platforms/powernv/
Dvas-window.c80 * be mapped cache-able and is only applicable to send windows.
280 * These registers are common to send/receive windows although they
281 * differ for user/kernel windows. As we resolve the TODOs we may
329 * TODO: Can we mfspr(AMR) even for user windows? in init_xlate_regs()
364 * Design note: For NX receive windows, NX allocates the FIFO buffer in OPAL
368 * write the per-chip RX FIFO addresses to the windows during boot-up
528 pr_err("Too many (%d) open windows\n", VAS_WINDOWS_PER_CHIP); in vas_assign_window_id()
589 * (so both send and receive windows are on the same VAS instance)
592 * NOTE: We access ->windows[] table and assume that vinst->mutex is held.
604 rxwin = vinst->windows[winid]; in get_user_rxwin()
[all …]
Dvas.h34 * VAS in each Power9 chip. Each instance of VAS has 64K windows or ports,
51 * The HVWCs for all windows on a specific instance of VAS are in a contiguous
53 * HVWC BAR for the instance. Similarly the UWCs for all windows on an instance
93 * credits? Its NA for NX but may be needed for other receive windows.
233 * to a paste command and hence applies only to receive windows.
275 * Local Notify Scope Control Register. (Receive windows only).
285 * Local DMA Cache Control Register (Receive windows only).
293 * Local Notify Scope Control Register. (Receive windows only).
294 * Not applicable to NX receive windows.
304 * receive windows, one per coprocessor type.
[all …]
/kernel/linux/linux-5.10/arch/powerpc/platforms/powernv/
Dvas-window.c68 * be mapped cache-able and is only applicable to send windows.
268 * These registers are common to send/receive windows although they
269 * differ for user/kernel windows. As we resolve the TODOs we may
317 * TODO: Can we mfspr(AMR) even for user windows? in init_xlate_regs()
352 * Design note: For NX receive windows, NX allocates the FIFO buffer in OPAL
356 * write the per-chip RX FIFO addresses to the windows during boot-up
515 pr_err("Too many (%d) open windows\n", VAS_WINDOWS_PER_CHIP); in vas_assign_window_id()
576 * (so both send and receive windows are on the same VAS instance)
579 * NOTE: We access ->windows[] table and assume that vinst->mutex is held.
591 rxwin = vinst->windows[winid]; in get_user_rxwin()
[all …]
Dvas.h30 * VAS in each Power9 chip. Each instance of VAS has 64K windows or ports,
47 * The HVWCs for all windows on a specific instance of VAS are in a contiguous
49 * HVWC BAR for the instance. Similarly the UWCs for all windows on an instance
89 * credits? Its NA for NX but may be needed for other receive windows.
227 * to a paste command and hence applies only to receive windows.
269 * Local Notify Scope Control Register. (Receive windows only).
279 * Local DMA Cache Control Register (Receive windows only).
287 * Local Notify Scope Control Register. (Receive windows only).
288 * Not applicable to NX receive windows.
314 * receive windows, one per coprocessor type.
[all …]
/kernel/linux/linux-5.10/Documentation/filesystems/
Dvfat.rst106 recent Windows don't update it correctly in some
129 emulate the Windows 95 rule for create.
131 **win95**: emulate the Windows 95 rule for display/create.
133 **winnt**: emulate the Windows NT rule for display/create.
135 **mixed**: emulate the Windows NT rule for display,
136 emulate the Windows 95 rule for create.
143 between local time (as used by Windows on FAT) and UTC
176 FAT has the ATTR_RO (read-only) attribute. On Windows,
268 knowledge of the extended FAT file system used in Windows NT 3.5 and
269 Windows 95. I don't guarantee that any of the following is correct,
[all …]
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/pci/
Ddesignware-pcie.txt22 - num-ib-windows: number of inbound address translation windows
23 - num-ob-windows: number of outbound address translation windows
67 num-ib-windows = <6>;
68 num-ob-windows = <2>;
/kernel/linux/linux-4.19/Documentation/filesystems/
Dvfat.txt85 recent Windows don't update it correctly in some
101 emulate the Windows 95 rule for create.
102 win95: emulate the Windows 95 rule for display/create.
103 winnt: emulate the Windows NT rule for display/create.
104 mixed: emulate the Windows NT rule for display,
105 emulate the Windows 95 rule for create.
110 between local time (as used by Windows on FAT) and UTC
137 rodir -- FAT has the ATTR_RO (read-only) attribute. On Windows,
232 knowledge of the extended FAT file system used in Windows NT 3.5 and
233 Windows 95. I don't guarantee that any of the following is correct,
[all …]
/kernel/linux/linux-4.19/fs/nls/
DKconfig46 DOS/Windows partitions correctly. This does apply to the filenames
58 DOS/Windows partitions correctly. This does apply to the filenames
70 DOS/Windows partitions correctly. This does apply to the filenames
83 DOS/Windows partitions correctly. This does apply to the filenames
99 DOS/Windows partitions correctly. This does apply to the filenames
114 DOS/Windows partitions correctly. This does apply to the filenames
125 DOS/Windows partitions correctly. This does apply to the filenames
136 DOS/Windows partitions correctly. This does apply to the filenames
147 DOS/Windows partitions correctly. This does apply to the filenames
158 DOS/Windows partitions correctly. This does apply to the filenames
[all …]
/kernel/linux/linux-5.10/fs/nls/
DKconfig47 DOS/Windows partitions correctly. This does apply to the filenames
59 DOS/Windows partitions correctly. This does apply to the filenames
71 DOS/Windows partitions correctly. This does apply to the filenames
84 DOS/Windows partitions correctly. This does apply to the filenames
100 DOS/Windows partitions correctly. This does apply to the filenames
115 DOS/Windows partitions correctly. This does apply to the filenames
126 DOS/Windows partitions correctly. This does apply to the filenames
137 DOS/Windows partitions correctly. This does apply to the filenames
148 DOS/Windows partitions correctly. This does apply to the filenames
159 DOS/Windows partitions correctly. This does apply to the filenames
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/pci/
Ddesignware-pcie.txt24 - num-ib-windows: number of inbound address translation windows
25 - num-ob-windows: number of outbound address translation windows
74 num-ib-windows = <6>;
75 num-ob-windows = <2>;
/kernel/linux/linux-4.19/drivers/misc/mic/scif/
Dscif_rma.h78 * @reg_list: List of registration windows for self
79 * @remote_reg_list: List of registration windows for peer
83 * @tc_lock: Synchronizes access to temporary cached windows list
87 * windows created by scif_vreadfrom/scif_vwriteto which have
89 * @tcw_refcount: Same as tw_refcount but for temporary cached windows
91 * @mmn_list: MMU notifier so that we can destroy the windows when required
142 * Specifies whether an RMA operation can span across partial windows, a single
143 * window or multiple contiguous windows. Mmaps can span across partial windows.
144 * Unregistration can span across complete windows. scif_get_pages() can span a
176 * windows across different end points.
[all …]
/kernel/linux/linux-5.10/Documentation/driver-api/
Dvme.rst59 The driver can request ownership of one or more master windows
60 (:c:func:`vme_master_request`), slave windows (:c:func:`vme_slave_request`)
64 attributes of the driver in question. For slave windows these attributes are
66 bus cycle types required in 'cycle'. Master windows add a further set of
84 Master windows
87 Master windows provide access from the local processor[s] out onto the VME bus.
88 The number of windows available and the available access modes is dependent on
106 :c:func:`vme_master_write` used to write to configured master windows.
113 Slave windows
116 Slave windows provide devices on the VME bus access into mapped portions of the
[all …]

12345678910>>...67