Home
last modified time | relevance | path

Searched full:historically (Results 1 – 25 of 126) sorted by relevance

123456

/Linux-v6.6/Documentation/devicetree/bindings/timer/
Dsnps,arc-timer.txt4 - Two identical copies TIMER0 and TIMER1 exist in ARC cores and historically
/Linux-v6.6/include/linux/platform_data/
Dmtd-nand-pxa3xx.h10 * historically all platforms remaining on platform data used only one. Switch
/Linux-v6.6/tools/arch/sh/include/asm/
Dbarrier.h22 * Historically we have only done this type of barrier for the MMUCR, but
/Linux-v6.6/Documentation/virt/
Dparavirt_ops.rst8 Historically, different binary kernels would be required in order to support
/Linux-v6.6/arch/x86/kernel/
Dprobe_roms.c228 /* 0 < length <= 0x7f * 512, historically */ in probe_roms()
266 /* 0 < length <= 0x7f * 512, historically */ in probe_roms()
/Linux-v6.6/arch/sh/include/asm/
Dbarrier.h24 * Historically we have only done this type of barrier for the MMUCR, but
/Linux-v6.6/arch/arm/include/uapi/asm/
Dsignal.h63 * SA_THIRTYTWO historically meant deliver the signal in 32-bit mode, even if
/Linux-v6.6/arch/arc/mm/
Dhighmem.c22 * shortlived ala "temporary mappings" which historically were implemented as
/Linux-v6.6/arch/x86/include/asm/
Dstackprotector.h8 * and unfortunately gcc historically required it to be at a fixed offset
/Linux-v6.6/Documentation/bpf/
Dgraph_ds_impl.rst24 The BPF map API has historically been the main way to expose data structures
46 Data structures implemented using the BPF map API have historically used BPF
/Linux-v6.6/arch/x86/pci/
Dbus_numa.c63 * so fall back to the defaults historically used by pci_create_bus(). in x86_pci_root_bus_resources()
/Linux-v6.6/arch/arc/include/asm/
Dpage.h118 * These macros have historically been misnamed
/Linux-v6.6/drivers/gpu/drm/i915/
Di915_file_private.h38 * Historically, the context uAPI allowed for two methods of
/Linux-v6.6/arch/powerpc/include/asm/
Dvdso_datapage.h16 * This structure was historically called systemcfg and exposed to
/Linux-v6.6/drivers/tty/
DKconfig156 Historically the kernel has allowed TIOCSTI, which will push
178 Historically the kernel has always automatically loaded any
/Linux-v6.6/include/linux/
Dlcd.h23 * most drivers seem to need this and historically get it wrong.
/Linux-v6.6/fs/xfs/libxfs/
Dxfs_trans_space.h21 * Note that we historically set m_rmap_maxlevels to 9 when reflink is enabled,
/Linux-v6.6/Documentation/devicetree/bindings/display/panel/
Dpanel-mipi-dbi-spi.yaml17 and logical interfaces for display controllers historically used in mobile
/Linux-v6.6/Documentation/scheduler/
Dsched-nice-design.rst13 support was historically coupled to timeslice length, and timeslice
/Linux-v6.6/tools/include/uapi/linux/
Dif_link.h109 * Historically the count of overflow events. Such events may be
120 * This statistics was historically used interchangeably with
142 * Historically the count of overflow events. Those events may be
/Linux-v6.6/include/uapi/linux/
Dif_link.h109 * Historically the count of overflow events. Such events may be
120 * This statistics was historically used interchangeably with
142 * Historically the count of overflow events. Those events may be
Dpmu.h138 /* no param, but historically was _IOR('B', 6, 0), meaning 4 bytes */
/Linux-v6.6/Documentation/devicetree/bindings/
Dxilinx.txt11 control how the core is synthesized. Historically, the EDK tool would
/Linux-v6.6/Documentation/arch/arm/
Dmicrochip.rst12 product line is historically named "AT91" or "at91" throughout the Linux kernel
/Linux-v6.6/fs/jfs/
Djfs_dinode.h62 * Historically, the inode was partitioned into 4 128-byte areas,

123456