Home
last modified time | relevance | path

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

1234567

/openbmc/linux/Documentation/devicetree/bindings/timer/
H A Dsnps,arc-timer.txt4 - Two identical copies TIMER0 and TIMER1 exist in ARC cores and historically
/openbmc/linux/include/linux/platform_data/
H A Dmtd-nand-pxa3xx.h10 * historically all platforms remaining on platform data used only one. Switch
/openbmc/linux/tools/arch/sh/include/asm/
H A Dbarrier.h22 * Historically we have only done this type of barrier for the MMUCR, but
/openbmc/linux/Documentation/virt/
H A Dparavirt_ops.rst8 Historically, different binary kernels would be required in order to support
/openbmc/qemu/gdb-xml/
H A Darm-core.xml28 the FPA registers historically were placed between the PC
/openbmc/linux/arch/x86/kernel/
H A Dprobe_roms.c218 /* 0 < length <= 0x7f * 512, historically */ in probe_roms()
256 /* 0 < length <= 0x7f * 512, historically */ in probe_roms()
/openbmc/linux/arch/sh/include/asm/
H A Dbarrier.h24 * Historically we have only done this type of barrier for the MMUCR, but
/openbmc/linux/arch/arm/include/uapi/asm/
H A Dsignal.h63 * SA_THIRTYTWO historically meant deliver the signal in 32-bit mode, even if
/openbmc/linux/arch/x86/include/asm/
H A Dstackprotector.h8 * and unfortunately gcc historically required it to be at a fixed offset
/openbmc/linux/arch/arc/mm/
H A Dhighmem.c22 * shortlived ala "temporary mappings" which historically were implemented as
/openbmc/linux/Documentation/bpf/
H A 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
/openbmc/linux/arch/x86/pci/
H A Dbus_numa.c63 * so fall back to the defaults historically used by pci_create_bus(). in x86_pci_root_bus_resources()
/openbmc/linux/drivers/gpu/drm/i915/
H A Di915_file_private.h38 * Historically, the context uAPI allowed for two methods of
/openbmc/linux/arch/arc/include/asm/
H A Dpage.h118 * These macros have historically been misnamed
/openbmc/linux/fs/xfs/libxfs/
H A Dxfs_trans_space.h21 * Note that we historically set m_rmap_maxlevels to 9 when reflink is enabled,
/openbmc/linux/arch/powerpc/include/asm/
H A Dvdso_datapage.h16 * This structure was historically called systemcfg and exposed to
/openbmc/linux/include/linux/
H A Dlcd.h23 * most drivers seem to need this and historically get it wrong.
/openbmc/linux/drivers/tty/
H A DKconfig156 Historically the kernel has allowed TIOCSTI, which will push
178 Historically the kernel has always automatically loaded any
/openbmc/linux/Documentation/devicetree/bindings/display/panel/
H A Dpanel-mipi-dbi-spi.yaml17 and logical interfaces for display controllers historically used in mobile
/openbmc/linux/Documentation/scheduler/
H A Dsched-nice-design.rst13 support was historically coupled to timeslice length, and timeslice
/openbmc/u-boot/include/configs/
H A Drpi.h28 * so 2708 has historically been used rather than a dedicated 2835 ID.
/openbmc/linux/include/uapi/linux/
H A 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
H A Dpmu.h138 /* no param, but historically was _IOR('B', 6, 0), meaning 4 bytes */
/openbmc/linux/tools/include/uapi/linux/
H A 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
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-connectivity/ufw/ufw/
H A D0002-add-an-option-to-specify-iptables-location.patch37 - # Historically iptables was in /sbin, then later also symlinked from

1234567