Searched full:different (Results 1 – 25 of 6413) sorted by relevance
12345678910>>...257
| /kernel/linux/linux-4.19/drivers/isdn/hisax/ |
| D | Kconfig | 97 using the different cards, a different D-channel protocol, or
107 using the different cards, a different D-channel protocol, or
131 using the different cards, a different D-channel protocol, or
154 using the different cards, a different D-channel protocol, or
164 using the different cards, a different D-channel protocol, or
174 using the different cards, a different D-channel protocol, or
185 using the different cards, a different D-channel protocol, or
195 using the different cards, a different D-channel protocol, or
206 using the different cards, a different D-channel protocol, or
215 using the different cards, a different D-channel protocol, or
[all …]
|
| /kernel/linux/linux-5.10/Documentation/process/ |
| 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 …]
|
| /kernel/linux/linux-4.19/Documentation/process/ |
| 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 …]
|
| /kernel/linux/linux-5.10/tools/testing/selftests/net/forwarding/ |
| 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"
|
| /kernel/linux/linux-5.10/Documentation/powerpc/ |
| 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
|
| /kernel/linux/linux-4.19/Documentation/namespaces/ |
| D | compatibility-list.txt | 4 may have when creating tasks living in different namespaces.
8 in different other namespaces (the rows):
23 other task living in a different namespace via a shared filesystem
28 2. Intentionally, two equal user IDs in different user namespaces
35 from different user namespaces should not access the same IPC objects
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/namespaces/ |
| 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
|
| /kernel/linux/linux-5.10/include/uapi/linux/ |
| 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
|
| /kernel/linux/linux-4.19/include/uapi/linux/ |
| 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
|
| /kernel/linux/linux-4.19/Documentation/virtual/ |
| D | paravirt_ops.txt | 4 Linux provides support for different hypervisor virtualization technologies.
5 Historically different binary kernels would be required in order to support
6 different hypervisors, this restriction was removed with pv_ops.
7 Linux pv_ops is a virtualization API which enables support for different
|
| /kernel/linux/linux-4.19/drivers/gpu/drm/msm/ |
| 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.)
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/msm/ |
| 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.)
|
| /kernel/linux/linux-5.10/Documentation/virt/ |
| 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
|
| /kernel/linux/linux-4.19/Documentation/media/uapi/v4l/ |
| 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
|
| D | format.rst | 13 Different devices exchange different kinds of data with applications,
15 within one kind many different formats are possible, in particular an
44 example, when the new standard uses a different number of scan lines,
47 multiple file descriptors which grabbed different logical streams
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/ |
| 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
|
| 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
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/sound/ |
| D | rt5663.txt | 19 Based on the different PCB layout, add the manual offset value to
20 compensate the DC offset for each L and R channel, and they are different
34 should compensate different DC offset to avoid the pop sound, and it is
35 also different between headphone and headset. In the example, the
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/sound/ |
| 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
|
| /kernel/linux/linux-4.19/tools/memory-model/litmus-tests/ |
| D | README | 24 sufficient to cause two different reading processes to agree on
25 the order of a pair of writes, where each write is to a different
26 variable by a different process? This litmus test is forbidden
32 needed to cause two different reading processes to agree on the
33 order of a pair of writes, where each write is to a different
34 variable by a different process?
|
| /kernel/linux/linux-4.19/tools/testing/ktest/examples/ |
| 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.
|
| /kernel/linux/linux-5.10/tools/testing/ktest/examples/ |
| 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.
|
| /kernel/linux/linux-4.19/tools/perf/pmu-events/arch/powerpc/power8/ |
| 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 …
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/powerpc/power8/ |
| 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 …
|
| /kernel/linux/linux-4.19/Documentation/ABI/testing/ |
| D | sysfs-platform-dfl-port | 7 distinguish different ports under same FPGA device.
13 Description: Read-only. User can program different PR bitstreams to FPGA
14 Accelerator Function Unit (AFU) for different functions. It
|
12345678910>>...257