/Linux-v6.1/drivers/usb/serial/ |
D | ipaq.c | 60 { 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 …]
|
/Linux-v6.1/Documentation/firmware-guide/acpi/ |
D | osi.rst | 24 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. 73 Windows 98, SE: "Microsoft Windows" [all …]
|
/Linux-v6.1/drivers/acpi/acpica/ |
D | utosi.c | 27 * 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 …]
|
/Linux-v6.1/drivers/pci/endpoint/ |
D | pci-epc-mem.c | 41 * @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 …]
|
/Linux-v6.1/drivers/mailbox/ |
D | arm_mhuv2.c | 8 * An MHUv2 mailbox controller can provide up to 124 channel windows (each 32 11 * windows. 19 * hardware - mainly the number of channel windows implemented by the platform, 38 /* Maximum number of channel windows */ 167 * @windows: Channel windows implemented by the platform. 182 unsigned int windows; member 222 * @windows: Total number of windows consumed by the channel, only relevant 233 u32 windows; member 329 int i = priv->ch_wn_idx + priv->windows - 1; in mhuv2_data_transfer_rx_startup() 343 int i = priv->ch_wn_idx + priv->windows - 1; in mhuv2_data_transfer_rx_shutdown() [all …]
|
/Linux-v6.1/Documentation/devicetree/bindings/mailbox/ |
D | arm,mhuv2.yaml | 15 between 1 and 124 channel windows (each 32-bit wide) to provide unidirectional 16 communication with remote processor(s), where the number of channel windows 34 channel windows. 86 The MHUv2 controller may contain up to 124 channel windows (each 32-bit 90 This property allows a platform to describe how these channel windows are 100 The second field of a tuple signifies the number of channel windows where 103 windows that implement the doorbell protocol. For data-transfer protocol, 104 this field signifies the number of 32-bit channel windows that implement 107 The total number of channel windows specified here shouldn't be more than 109 of windows here than what the platform implements. [all …]
|
/Linux-v6.1/Documentation/usb/ |
D | gadget_multi.rst | 42 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 …]
|
D | gadget_serial.rst | 42 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 …]
|
/Linux-v6.1/fs/fat/ |
D | Kconfig | 7 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
|
/Linux-v6.1/arch/powerpc/platforms/pseries/ |
D | vas.c | 410 * closed windows (means with lost credits), do not give new in vas_allocate_window() 411 * window to user space. New windows will be opened only in vas_allocate_window() 412 * after the existing windows are reopened when credits are in vas_allocate_window() 602 * VAS windows can be closed due to lost credits when the core is 619 * Nothing to do if there are no closed windows. in reconfig_open_windows() 626 * assigned to the LPAR and the kernel closes VAS windows in reconfig_open_windows() 628 * uses LIFO (the last windows that are opened will be closed in reconfig_open_windows() 631 * For example, 40 windows are closed when the LPAR lost 2 cores in reconfig_open_windows() 633 * credits. It means the kernel can reopen 20 windows. So move in reconfig_open_windows() 634 * 20 entries in the VAS windows lost and reopen next 20 windows. in reconfig_open_windows() [all …]
|
D | vas.h | 42 * Co-processor feature - GZIP QoS windows or GZIP default windows 89 * the list of open windows. 93 struct list_head list; /* List of open windows */ 94 int nr_close_wins; /* closed windows in the hypervisor for DLPAR */ 95 int nr_open_windows; /* Number of successful open windows */ 130 /* List of windows opened which is used for LPM */
|
/Linux-v6.1/arch/powerpc/platforms/powernv/ |
D | vas-window.c | 69 * be mapped cache-able and is only applicable to send windows. 269 * These registers are common to send/receive windows although they 270 * differ for user/kernel windows. As we resolve the TODOs we may 318 * TODO: Can we mfspr(AMR) even for user windows? in init_xlate_regs() 353 * Design note: For NX receive windows, NX allocates the FIFO buffer in OPAL 357 * write the per-chip RX FIFO addresses to the windows during boot-up 516 pr_err("Too many (%d) open windows\n", VAS_WINDOWS_PER_CHIP); in vas_assign_window_id() 577 * (so both send and receive windows are on the same VAS instance) 580 * NOTE: We access ->windows[] table and assume that vinst->mutex is held. 593 rxwin = vinst->windows[winid]; in get_user_rxwin() [all …]
|
D | vas.h | 30 * 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 …]
|
/Linux-v6.1/Documentation/filesystems/ |
D | vfat.rst | 106 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 …]
|
/Linux-v6.1/fs/ntfs3/ |
D | Kconfig | 6 Windows OS native file system (NTFS) support up to NTFS version 3.1. 19 Windows implementation of ntfs.sys uses 32 bits per clusters. 21 for 16T+ volumes. Windows will not be able to mount such volumes. 29 In Windows 10 one can use command "compact" to compress any files. 44 NOTE: this is linux only feature. Windows will ignore these ACLs.
|
/Linux-v6.1/fs/nls/ |
D | Kconfig | 47 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 …]
|
/Linux-v6.1/Documentation/driver-api/ |
D | vme.rst | 59 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 …]
|
/Linux-v6.1/Documentation/powerpc/ |
D | pci_iov_resource_on_powernv.rst | 58 contain two "windows", depending on the value of PCI address bit 59. 63 - For MSIs, we have two windows in the address space (one at the top of 74 Like other PCI host bridges, the Power8 IODA2 PHB supports "windows" 76 window and sixteen M64 windows. They have different characteristics. 101 SR-IOV). We basically use the trick of forcing the bridge MMIO windows 110 - The M64 windows: 123 * Support overlaps. If an address is covered by multiple windows, 155 We would like to investigate using additional M64 windows in "single 201 - Single segmented M64 windows: A segmented M64 window could be used just 207 - Multiple segmented M64 windows: As usual, each window is split into 256 [all …]
|
/Linux-v6.1/Documentation/devicetree/bindings/iio/chemical/ |
D | senseair,sunrise.yaml | 17 https://rmtplusstoragesenseair.blob.core.windows.net/docs/Dev/publicerat/PSP11704.pdf 18 https://rmtplusstoragesenseair.blob.core.windows.net/docs/Dev/publicerat/PSH11649.pdf 19 https://rmtplusstoragesenseair.blob.core.windows.net/docs/Dev/publicerat/TDE5531.pdf 20 https://rmtplusstoragesenseair.blob.core.windows.net/docs/Market/publicerat/TDE7318.pdf
|
/Linux-v6.1/fs/cifs/ |
D | Kconfig | 30 and NAS appliances (e.g. Samba, Windows 10, Windows Server 2016, 32 The older CIFS protocol was included in Windows NT4, 2000 and XP (and 36 This module also provides limited support for OS/2 and Windows ME 54 If you need to mount to Samba, Azure, Macs or Windows from this machine, say Y. 101 namespace prefix to SMB/CIFS EAs. EAs are stored on Windows 116 than Windows like) file behavior. It also enables
|
/Linux-v6.1/Documentation/devicetree/bindings/pci/ |
D | snps,dw-pcie-ep.yaml | 57 num-ib-windows: 60 description: number of inbound address translation windows 63 num-ob-windows: 66 description: number of outbound address translation windows
|
D | socionext,uniphier-pcie-ep.yaml | 67 num-ib-windows: 70 num-ob-windows: 103 num-ib-windows = <16>; 104 num-ob-windows = <16>;
|
D | mobiveil-pcie.txt | 4 has up to 8 outbound and inbound windows for the address translation. 21 - apio-wins : number of requested apio outbound windows 22 default 2 outbound windows are configured - 25 - ppio-wins : number of requested ppio inbound windows
|
/Linux-v6.1/drivers/gpu/drm/nouveau/dispnv50/ |
D | corec37d.c | 37 const u32 windows = 8; /*XXX*/ in corec37d_wndw_owner() local 40 if ((ret = PUSH_WAIT(push, windows * 2))) in corec37d_wndw_owner() 43 for (i = 0; i < windows; i++) { in corec37d_wndw_owner() 131 const u32 windows = 8; /*XXX*/ in corec37d_init() local 134 if ((ret = PUSH_WAIT(push, 2 + windows * 5))) in corec37d_init() 139 for (i = 0; i < windows; i++) { in corec37d_init()
|
/Linux-v6.1/Documentation/admin-guide/cifs/ |
D | usage.rst | 12 practical interoperability with Windows 2000, Windows XP, Samba and equivalent 15 standard for interoperating between Macs and Windows and major NAS appliances. 78 the new default. To use old dialects (e.g. to mount Windows XP) use "vers=1.0" 79 on mount (or vers=2.0 for Windows Vista). Note that the CIFS (vers=1.0) is 162 3.0.6 and later (also EA support works in all versions of Windows, at least to 186 open files (required for strict POSIX compliance). Windows Servers already 200 be invisible to Windows clients and typically will not affect local 208 Mac or Windows servers:: 259 Valid filenames differ between Windows and Linux. Windows typically restricts 261 which is used to delimit the beginning of a stream name by Windows), while [all …]
|