| /OK3568_Linux_fs/kernel/Documentation/process/ |
| H A D | stable-api-nonsense.rst | 64 - Depending on the version of the C compiler you use, different kernel
65 data structures will contain different alignment of structures, and
66 possibly include different functions in different ways (putting
68 isn't that important, but the different data structure padding is
72 different things can be assumed by the kernel:
74 - different structures can contain different fields
77 - Memory within the kernel can be aligned in different ways,
80 - Linux runs on a wide range of different processor architectures.
89 different Linux distributions and the number of different supported
91 different build options on different releases. Also realize that each
[all …]
|
| /OK3568_Linux_fs/yocto/poky/meta/lib/oeqa/selftest/cases/ |
| H A D | reproducible.py | 29 DIFFERENT = 'DIFFERENT' variable
49 self.different = []
58 elif r.status == DIFFERENT:
64 self.different.append(r)
71 self.different.sort()
76 …return 'same=%i different=%i different_excluded=%i missing=%i total=%i\nunused_exclusions=%s' % (l…
93 result.status = DIFFERENT
118 # different
280 self.write_package_list(package_class, 'different', result.different)
285 for d in result.different:
[all …]
|
| /OK3568_Linux_fs/external/mpp/doc/design/ |
| H A D | 1.mpp_design.txt | 8 The design target of mpp is to connect different Rockchip hardware kernel driver
9 and different userspace application.
30 cmake to compile on different platform.
38 mpi (Media Process Interface) is easy to extend by different control function.
39 The input/output element packet/frame/buffer is easy to extend different
87 This module shutters the differences between different operation systems and
95 set to communicate with mpp. MppTask can carry different meta data and complete
100 provides a general call flow for different video format. Software process will
106 This layer provides the implement function call of different video format and
107 different hardware. For decoder parser provide the video stream parse function
[all …]
|
| H A D | 3.mpp_buffer.txt | 5 not use the buffer malloc by cpu. Then we design MppBuffer for different memory
6 allocator on different platform. Currently it is designed for ion buffer on
9 In order to manage buffer usage in different user mpp buffer module introduces
13 Different MppBufferGroup has different allocator. And besides normal malloc/free
|
| /OK3568_Linux_fs/kernel/tools/testing/selftests/net/forwarding/ |
| H A D | tc_vlan_modify.sh | 108 check_fail $? "ping between two different vlans passed when should not"
111 check_fail $? "ping6 between two different vlans passed when should not"
119 check_err $? "ping between two different vlans failed when should not"
122 check_err $? "ping6 between two different vlans failed when should not"
135 check_fail $? "ping between two different vlans passed when should not"
138 check_fail $? "ping6 between two different vlans passed when should not"
146 check_err $? "ping between two different vlans failed when should not"
149 check_err $? "ping6 between two different vlans failed when should not"
|
| H A D | ethtool.sh | 78 # Test that when we force different speeds, links are not up and ping
92 check_fail $? "ping with different speeds"
94 log_test "force of different speeds autoneg off"
262 # Test that when we configure links to advertise different speeds,
280 check_fail $? "ping with different speeds autoneg on"
283 log_test "advertise different speeds autoneg on"
|
| /OK3568_Linux_fs/kernel/Documentation/powerpc/ |
| H A D | vcpudispatch_stats.rst | 11 scenarios, vcpus may be dispatched on a different processor chip (away
33 3. number of times this vcpu was dispatched on a different processor core
35 4. number of times this vcpu was dispatched on a different chip
36 5. number of times this vcpu was dispatches on a different socket/drawer
43 7. number of times this vcpu was dispatched in a different node
69 physical cpu as the last time. 2683 were on a different core, but within
70 the same chip, while 30 dispatches were on a different chip compared to
|
| /OK3568_Linux_fs/u-boot/arch/mips/mach-bmips/ |
| H A D | Kconfig | 94 Between its different peripherals there's an integrated switch with 4
105 Between its different peripherals there's a BCM5325 switch with 4
116 Between its different peripherals there's an integrated switch with 4
127 Between its different peripherals there's a BCM5325 switch with 4
138 Between its different peripherals there's a BCM53115 switch with 4
149 Between its different peripherals there's a BCM5325 switch with 4
160 Between its different peripherals there's a BCM5325 switch with 4
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/aarch64-none-linux-gnu/libc/usr/include/linux/ |
| H A D | falloc.h | 19 * Different filesystems may implement different limitations on the
51 * Different filesystems may implement different limitations on the granularity
68 * Different filesystems may implement different limitations on the
|
| /OK3568_Linux_fs/kernel/include/uapi/linux/ |
| H A D | falloc.h | 19 * Different filesystems may implement different limitations on the
51 * Different filesystems may implement different limitations on the granularity
68 * Different filesystems may implement different limitations on the
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/arm-none-linux-gnueabihf/libc/usr/include/linux/ |
| H A D | falloc.h | 19 * Different filesystems may implement different limitations on the
51 * Different filesystems may implement different limitations on the granularity
68 * Different filesystems may implement different limitations on the
|
| /OK3568_Linux_fs/kernel/Documentation/admin-guide/namespaces/ |
| H A D | compatibility-list.rst | 6 may have when creating tasks living in different namespaces.
10 in different other namespaces (the rows):
28 other task living in a different namespace via a shared filesystem
33 2. Intentionally, two equal user IDs in different user namespaces
40 from different user namespaces should not access the same IPC objects
|
| /OK3568_Linux_fs/kernel/Documentation/userspace-api/media/v4l/ |
| H A D | colorspaces.rst | 20 the human eye has color receptors that are sensitive to three different
23 different wavelengths, so instead of RGB we would be using the
34 possible that different SPDs will result in the same stimulation of
36 of the light is different.
68 different wavelengths, the combination of which will stimulate the color
74 Different display devices will have different primaries and some
77 different display technologies or uses. To define a colorspace you need
150 mix of different standards also led to very confusing naming conventions
|
| H A D | format.rst | 13 Different devices exchange different kinds of data with applications,
15 within one kind many different formats are possible, in particular there is an
44 example, when the new standard uses a different number of scan lines,
47 multiple file descriptors which grabbed different logical streams
|
| /OK3568_Linux_fs/buildroot/dl/sox/git/scripts/ |
| H A D | testcd.sh | 30 # a different default volume
92 echo "\n--- different frequencies"
122 echo "\n--- different frequencies $FREQ"
167 # different volumes at a few frequencies
171 echo "\n--- different volumes $DB db at Frequencies $FREQ"
188 # volume sweep at different frequencies
212 # effects for different channels
214 # silence on one channel, full power on the other - different frequencies
|
| /OK3568_Linux_fs/kernel/drivers/gpu/drm/msm/ |
| H A D | NOTES | 3 In the current snapdragon SoC's, we have (at least) 3 different
20 with N different kms devices from xf86-video-freedreno. Plus, it
25 So, the approach is one drm driver, with some modularity. Different
27 And one or more 'struct msm_gpu' for the various different gpu sub-
57 than needing a different implementation for DTV, DSI, etc. (Ie. the
58 register interface is same, just different bases.)
|
| /OK3568_Linux_fs/kernel/Documentation/virt/ |
| H A D | paravirt_ops.rst | 7 Linux provides support for different hypervisor virtualization technologies.
8 Historically different binary kernels would be required in order to support
9 different hypervisors, this restriction was removed with pv_ops.
10 Linux pv_ops is a virtualization API which enables support for different
|
| /OK3568_Linux_fs/u-boot/doc/ |
| H A D | README.power-framework | 19 designers strive to cut down power consumption. Hence several different types of
27 One package can integrate PMIC and MUIC with different addresses on the I2C bus.
28 The same device - e.g. MAX8997 uses two different I2C busses and addresses.
31 different ICs use different endianess. For this reason struct pmic holds
59 be maintained for different classes of devices.
117 __Example for trats (this can be very different for other board):__
|
| /OK3568_Linux_fs/kernel/tools/perf/pmu-events/arch/powerpc/power8/ |
| H A D | cache.json | 5 …e was reloaded with Modified (M) data from another chip's L2 or L3 on a different Node or Group (D…
6 …e was reloaded with Modified (M) data from another chip's L2 or L3 on a different Node or Group (D…
11 …che was reloaded with Shared (S) data from another chip's L2 or L3 on a different Node or Group (D…
12 …che was reloaded with Shared (S) data from another chip's L2 or L3 on a different Node or Group (D…
17 …": "The processor's data cache was reloaded from another chip's L4 on a different Node or Group (D…
18 …": "The processor's data cache was reloaded from another chip's L4 on a different Node or Group (D…
107 … reloaded either shared or modified data from another core's L2/L3 on a different chip (remote or …
108 … reloaded either shared or modified data from another core's L2/L3 on a different chip (remote or …
|
| /OK3568_Linux_fs/u-boot/drivers/pinctrl/nxp/ |
| H A D | Kconfig | 14 configuration. This driver is different from the linux one,
28 configuration. This driver is different from the linux one,
42 configuration. This driver is different from the linux one,
56 is different from the linux one, this is a simple implementation,
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/mailbox/ |
| H A D | omap-mailbox.txt | 4 The OMAP mailbox hardware facilitates communication between different processors
17 and tx interrupt source per h/w fifo. Communication between different processors
23 instance. DRA7xx has multiple instances with different number of h/w fifo queues
24 and interrupt lines between different instances. The interrupt lines can also be
25 routed to different processor sub-systems on DRA7xx as they are routed through
29 all these clusters are multiplexed and routed to different processor subsystems
78 Each child node should have a unique node name across all the different
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/sound/ |
| H A D | rt5663.txt | 23 Based on the different PCB layout, add the manual offset value to
24 compensate the DC offset for each L and R channel, and they are different
38 should compensate different DC offset to avoid the pop sound, and it is
39 also different between headphone and headset. In the example, the
|
| /OK3568_Linux_fs/kernel/Documentation/admin-guide/mm/ |
| H A D | concepts.rst | 25 address ranges. Besides, different CPU architectures, and even
26 different implementations of the same architecture have different views
103 Often hardware poses restrictions on how different physical memory
115 architectures define all zones, and requirements for DMA are different
116 for different platforms.
123 different access latency depending on the "distance" from the
161 different types of data. It can be kernel internal data structures,
|
| /OK3568_Linux_fs/buildroot/dl/qt5location/git/tests/auto/qplacesearchrequest/ |
| H A D | tst_qplacesearchrequest.cpp | 194 QVERIFY2(testObj != testObj2, "Object should be different"); in operatorsTest()
207 //test that different boxes do not match in operatorsTest()
209 QVERIFY2(testObj != testObj2, "Different box areas identified as matching"); in operatorsTest()
220 //test that different circle don't match in operatorsTest()
222 QVERIFY2(testObj != testObj2, "Different circle areas identified as matching"); in operatorsTest()
238 //test that different scopes do not match in operatorsTest()
240 QVERIFY2(testObj != testObj2, "Different scopes identified as matching"); in operatorsTest()
242 //test that different search contexts do not match in operatorsTest()
|
| /OK3568_Linux_fs/kernel/tools/testing/ktest/examples/ |
| H A D | test.conf | 8 # BOX can be different than foo, if the machine BOX has
9 # multiple partitions with different systems installed. For example,
12 # machine, which may be different between which system the machine
55 # The following files each handle a different test case.
|