Home
last modified time | relevance | path

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

123456789

/kernel/linux/linux-5.10/Documentation/devicetree/bindings/timer/
Dsnps,arc-timer.txt4 - Two idential copies TIMER0 and TIMER1 exist in ARC cores and historically
/kernel/linux/linux-5.10/include/linux/platform_data/
Dmtd-nand-pxa3xx.h10 * historically all platforms remaining on platform data used only one. Switch
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/timer/
Dsnps,arc-timer.txt4 - Two identical copies TIMER0 and TIMER1 exist in ARC cores and historically
/kernel/linux/linux-6.6/include/linux/platform_data/
Dmtd-nand-pxa3xx.h10 * historically all platforms remaining on platform data used only one. Switch
/kernel/linux/linux-5.10/tools/arch/sh/include/asm/
Dbarrier.h22 * Historically we have only done this type of barrier for the MMUCR, but
/kernel/linux/linux-6.6/tools/arch/sh/include/asm/
Dbarrier.h22 * Historically we have only done this type of barrier for the MMUCR, but
/kernel/linux/linux-5.10/Documentation/virt/
Dparavirt_ops.rst8 Historically different binary kernels would be required in order to support
/kernel/linux/linux-6.6/Documentation/virt/
Dparavirt_ops.rst8 Historically, different binary kernels would be required in order to support
/kernel/linux/linux-6.6/arch/x86/kernel/
Dprobe_roms.c218 /* 0 < length <= 0x7f * 512, historically */ in probe_roms()
256 /* 0 < length <= 0x7f * 512, historically */ in probe_roms()
/kernel/linux/linux-5.10/arch/x86/kernel/
Dprobe_roms.c217 /* 0 < length <= 0x7f * 512, historically */ in probe_roms()
255 /* 0 < length <= 0x7f * 512, historically */ in probe_roms()
/kernel/linux/linux-6.6/arch/sh/include/asm/
Dbarrier.h24 * Historically we have only done this type of barrier for the MMUCR, but
/kernel/linux/linux-5.10/arch/sh/include/asm/
Dbarrier.h24 * Historically we have only done this type of barrier for the MMUCR, but
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/mtd/
Djedec,spi-nor.txt50 The following chip names have been used historically to
/kernel/linux/linux-6.6/arch/arm/include/uapi/asm/
Dsignal.h63 * SA_THIRTYTWO historically meant deliver the signal in 32-bit mode, even if
/kernel/linux/linux-6.6/arch/arc/mm/
Dhighmem.c22 * shortlived ala "temporary mappings" which historically were implemented as
/kernel/linux/linux-6.6/arch/x86/include/asm/
Dstackprotector.h8 * and unfortunately gcc historically required it to be at a fixed offset
/kernel/linux/linux-6.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
/kernel/linux/linux-6.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()
/kernel/linux/linux-5.10/arch/x86/pci/
Dbus_numa.c63 * so fall back to the defaults historically used by pci_create_bus(). in x86_pci_root_bus_resources()
/kernel/linux/linux-6.6/drivers/gpu/drm/i915/
Di915_file_private.h38 * Historically, the context uAPI allowed for two methods of
/kernel/linux/linux-5.10/arch/arc/include/asm/
Dpage.h107 * These macros have historically been misnamed
/kernel/linux/linux-6.6/arch/arc/include/asm/
Dpage.h118 * These macros have historically been misnamed
/kernel/linux/linux-5.10/arch/arc/mm/
Dhighmem.c22 * shortlived ala "temporary mappings" which historically were implemented as
/kernel/linux/linux-6.6/drivers/tty/
DKconfig156 Historically the kernel has allowed TIOCSTI, which will push
178 Historically the kernel has always automatically loaded any
/kernel/linux/linux-6.6/arch/powerpc/include/asm/
Dvdso_datapage.h16 * This structure was historically called systemcfg and exposed to

123456789