| /OK3568_Linux_fs/kernel/arch/arm/mach-s3c/ |
| H A D | Kconfig | 80 # device definitions to compile in 85 Compile in platform device definitions for HSMMC code 90 Compile in platform device definitions for HSMMC channel 1 95 Compile in platform device definitions for HSMMC channel 2 100 Compile in platform device definitions for HSMMC channel 3 105 Compile in platform device definitions for HWMON 110 Compile in platform device definitions for I2C channel 1 115 Compile in platform device definitions for I2C channel 2 186 Compile in platform device definitions for IDE 191 Compile in platform device definitions for S3C64XX's type [all …]
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-networking/recipes-daemons/ncftp/ncftp/ |
| H A D | unistd.patch | 1 This patch is needed to avoid double definitions of functions 3 definitions causes the sed.sh script in configure to fail since it 11 removing this include causes only one definitions to be emitted into 14 Other solution would to fix sed.sh to ignore double definitions
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/recipes-support/sharutils/sharutils/ |
| H A D | 0001-Fix-building-with-GCC-10.patch | 10 global variable definitions: 16 This patch fixes it by changing the definitions in header files into extern 36 * global exported definitions 75 * global exported definitions 88 * global exported definitions
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/recipes-devtools/breakpad/breakpad/ |
| H A D | 0001-lss-Match-syscalls-to-match-musl.patch | 28 /* End of i386 definitions */ 41 /* End of x86-64 definitions */ 54 /* End of MIPS (64bit API) definitions */
|
| H A D | mips_asm_sgidefs.patch | 6 /* Include definitions of the ABI currently in use. */ 9 - * which has the definitions we need.
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-python/recipes-devtools/python/python3-grpcio/ |
| H A D | 0001-absl-always-use-asm-sgidefs.h.patch | 7 but on linux asm/sgidefs.h is there and contains same definitions, using 22 // Include definitions of the ABI currently in use. 26 // definitions we need.
|
| /OK3568_Linux_fs/yocto/poky/meta/recipes-extended/minicom/minicom/ |
| H A D | 0001-Drop-superfluous-global-variable-definitions.patch | 4 Subject: [PATCH 1/3] Drop superfluous global variable definitions 8 minicom.o is always linked to dial.o. Thus the definitions in dial.c 12 disallowing multiple global variable definitions.
|
| H A D | 0003-Drop-superfluous-global-variable-definitions.patch | 4 Subject: [PATCH 3/3] Drop superfluous global variable definitions 11 to minicom.o. Thus it is safe to drop the definitions from minicom.c 15 disallowing multiple global variable definitions.
|
| H A D | 0002-Drop-superfluous-global-variable-definitions.patch | 4 Subject: [PATCH 2/3] Drop superfluous global variable definitions 14 disallowing multiple global variable definitions.
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/recipes-devtools/abseil-cpp/abseil-cpp/ |
| H A D | 0001-absl-always-use-asm-sgidefs.h.patch | 7 but on linux asm/sgidefs.h is there and contains same definitions, using 24 // Include definitions of the ABI currently in use. 28 // definitions we need.
|
| /OK3568_Linux_fs/kernel/Documentation/arm/pxa/ |
| H A D | mfp.rst | 88 because pin configuration definitions may conflict in these file (i.e. 128 some simplified definitions can be used, e.g. GPIOxx_TFT_LCD_16BPP on 158 The MFPR has the following bit definitions (for PXA300/PXA310/PXA320):: 194 The basic idea of this design is to introduce definitions for all possible pin 195 configurations, these definitions are processor and platform independent, and 196 the actual API invoked to convert these definitions into register settings and 205 1. Unified pin definitions - enum constants for all configurable pins 206 2. processor-neutral bit definitions for a possible MFP configuration 210 for PXA3xx specific MFPR register bit definitions and PXA3xx common pin 215 for PXA2xx specific definitions and PXA25x/PXA27x common pin configurations [all …]
|
| /OK3568_Linux_fs/buildroot/dl/qt5location/git/src/3rdparty/mapbox-gl-native/src/mbgl/style/expression/ |
| H A D | is_expression.cpp | 23 …(CompoundExpressionRegistry::definitions.find(*name) != CompoundExpressionRegistry::definitions.en… in isExpression()
|
| /OK3568_Linux_fs/kernel/Documentation/userspace-api/media/v4l/ |
| H A D | selections-common.rst | 5 Common selection definitions 15 This section defines the common definitions of the selection interfaces
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/recipes-connectivity/wifi-test-suite/files/ |
| H A D | fno-common.patch | 3 This ensures that compilers with -fno-common does not generate multiple definitions 12 /* Since the two definitions are used all over the CA function */
|
| /OK3568_Linux_fs/kernel/Documentation/ABI/stable/ |
| H A D | sysfs-bus-firewire | 8 See IEEE 1212 for semantic definitions. 27 See IEEE 1212 for semantic definitions. 61 See IEEE 1212 for semantic definitions. 80 See IEEE 1212 for semantic definitions.
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/recipes-devtools/ctags/ |
| H A D | ctags_5.9.20220410.0.bb | 7 definitions which is used by numerous editors and utilities \ 8 to instantly locate the definitions."
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/recipes-support/inotify-tools/inotify-tools/ |
| H A D | 0002-libinotifytools-Bridge-differences-between-musl-glib.patch | 7 System detects to use sys/fnotify.h and then assumes glibc's definitions 8 but musl has definitions of its own. perhaps portable thing would be to
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/recipes-extended/libgxim/libgxim/ |
| H A D | 0001-Use-AM_CPPFLAGS-instead-of-INCLUDES.patch | 31 # Global definitions 44 # Global definitions
|
| /OK3568_Linux_fs/buildroot/package/netperf/ |
| H A D | 0001-src-nettest_omni.c-fix-compilation-with-GCC10.patch | 7 multiple definitions of implicit "extern" variables. Remove the extra 8 definitions.
|
| /OK3568_Linux_fs/u-boot/board/hisilicon/poplar/ |
| H A D | README | 50 l-loader: use external memory region definitions 53 all the definitions for the memory regions used for its boot stages. 54 Include that file where needed, and use the definitions found therein 67 Separate the definitions for memory regions used for the BL stage 70 include this (external) header to get these definitions, rather than 73 The new file has a complete set of definitions (more than may be
|
| /OK3568_Linux_fs/yocto/poky/meta/recipes-devtools/docbook-xml/ |
| H A D | docbook-xml-dtd4_4.5.bb | 1 SUMMARY = "Document type definitions for verification of XML data files" 2 DESCRIPTION = "Document type definitions for verification of XML data \
|
| /OK3568_Linux_fs/buildroot/package/gdb/11.2/ |
| H A D | 0010-The-signal-definitions-of-musl-and-gdb-collide.patch | 4 Subject: [PATCH] The signal definitions of musl and gdb collide 8 Kernel 4.14 misses the definitions of struct user_sve_header so we still
|
| /OK3568_Linux_fs/buildroot/package/gdb/10.2/ |
| H A D | 0010-The-signal-definitions-of-musl-and-gdb-collide.patch | 4 Subject: [PATCH] The signal definitions of musl and gdb collide 8 Kernel 4.14 misses the definitions of struct user_sve_header so we still
|
| /OK3568_Linux_fs/yocto/poky/meta/conf/machine/include/arm/ |
| H A D | README | 4 The ARM architecture definitions are split among a number of files. 5 The primary definitions for the variables are handled by the core
|
| /OK3568_Linux_fs/buildroot/package/arptables/ |
| H A D | 0001-Fix-musl-build-issue.patch | 15 Since arptables only requires a few definitions from the Linux Kernel headers 16 we opt-out the clashing header files and define the needed definitions.
|