| /openbmc/linux/tools/testing/selftests/drivers/net/mlxsw/ |
| H A D | devlink_trap_control.sh | 222 $MZ $h1 -c 1 -a own -b 01:00:5E:00:00:01 \
230 "igmp_v1_report" $MZ $h1 -c 1 -a own -b 01:00:5E:00:00:01 \
238 "igmp_v2_report" $MZ $h1 -c 1 -a own -b 01:00:5E:00:00:01 \
246 "igmp_v3_report" $MZ $h1 -c 1 -a own -b 01:00:5E:00:00:01 \
254 "igmp_v2_leave" $MZ $h1 -c 1 -a own -b 01:00:5E:00:00:02 \
310 $MZ $h1 -c 1 -a own -b bcast -A 0.0.0.0 -B 255.255.255.255 \
314 $MZ $h1 -c 1 -a own -b $(mac_get $rp1) -A 192.0.2.1 \
332 $MZ $h1 -c 1 -a own -b bcast -t arp request -p 100 -q
338 $MZ $h1 -c 1 -a own -b $(mac_get $rp1) -t arp reply -p 100 -q
366 "ipv6_neigh_advert" $MZ $h1 -6 -c 1 -a own -b $(mac_get $rp1) \
[all …]
|
| /openbmc/openbmc/poky/documentation/ |
| H A D | transitioning-to-a-custom-environment.rst | 14 now, as you are starting your own project, it isn't exactly straightforward what
64 #. **Create your own layer for the BSP you're going to use**.
67 BSP, :ref:`create your own layer for the BSP <bsp-guide/bsp:creating a new
75 #. **Write your own recipe to build additional software support that isn't
77 Creating your own recipe is especially important for custom application
87 that you have your own image recipe --- don't try appending to existing image
96 #. **Consider creating your own distribution**.
97 When you get to a certain level of customization, consider creating your own
102 your own distribution in a new layer inheriting from Poky but overriding what
105 local settings, it's time to :ref:`consider creating your own distribution
[all …]
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/knightslanding/ |
| H A D | cache.json | 165 …and prefetch code read requests that accounts for responses which hit its own tile's L2 with data…
174 …and prefetch code read requests that accounts for responses which hit its own tile's L2 with data…
183 …and prefetch code read requests that accounts for responses which hit its own tile's L2 with data…
192 …and prefetch code read requests that accounts for responses which hit its own tile's L2 with data…
273 … L1 prefetch data read requests that accounts for responses which hit its own tile's L2 with data…
282 … L1 prefetch data read requests that accounts for responses which hit its own tile's L2 with data…
291 … L1 prefetch data read requests that accounts for responses which hit its own tile's L2 with data…
300 … L1 prefetch data read requests that accounts for responses which hit its own tile's L2 with data…
381 …": "Counts any Prefetch requests that accounts for responses which hit its own tile's L2 with data…
390 …": "Counts any Prefetch requests that accounts for responses which hit its own tile's L2 with data…
[all …]
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | custom-distribution.rst | 3 Creating Your Own Distribution
16 your own distribution.
18 To create your own distribution, the basic steps consist of creating
19 your own distribution layer, creating your own distribution
25 separate. It is strongly recommended that you create and use your own
26 layer for configuration and code. Using your own layer as compared to
101 ":ref:`dev-manual/layers:creating your own layer`" and
|
| /openbmc/phosphor-ipmi-flash/ |
| H A D | bmc_json_config.md | 14 write your own. It's helpful to start here.
182 ## Writing your own json Configuration
184 If you wish to write your own json configuration, you simply create a legal json
191 default-provided configuration files, and also add your own to add additional
246 ### Installing your own json configuration
248 To install your own configuration(s) you can add your own bbappend file that
252 ## Adding your own handler type
270 ## Adding your own action type
|
| /openbmc/linux/drivers/video/fbdev/core/ |
| H A D | Kconfig | 50 filling. This is used by drivers that don't provide their own
58 This is used by drivers that don't provide their own (accelerated)
66 blitting. This is used by drivers that don't provide their own
82 filling. This is used by drivers that don't provide their own
90 This is used by drivers that don't provide their own (accelerated)
98 blitting. This is used by drivers that don't provide their own
|
| /openbmc/linux/drivers/net/fddi/ |
| H A D | defza.c | 449 u32 own, rmc; in fza_do_xmit() local
461 own = FZA_RING_TX_OWN_HOST; in fza_do_xmit()
485 writel_o(own, &fp->ring_rmc_tx[i].own); in fza_do_xmit()
492 own = FZA_RING_TX_OWN_RMC; in fza_do_xmit()
503 writel_o(FZA_RING_TX_OWN_RMC, &fp->ring_rmc_tx[first].own); in fza_do_xmit()
516 u32 own; in fza_do_recv_smt() local
520 own = readl_o(&fp->ring_smt_rx[i].own); in fza_do_recv_smt()
521 if ((own & FZA_RING_OWN_MASK) == FZA_RING_OWN_FZA) in fza_do_recv_smt()
530 writel_o(FZA_RING_OWN_FZA, &fp->ring_smt_rx[i].own); in fza_do_recv_smt()
544 u32 own, rmc; in fza_tx() local
[all …]
|
| /openbmc/linux/Documentation/hwmon/ |
| H A D | adm1031.rst | 33 They sense their own temperature as well as the temperature of up to one
39 Each temperature channel has its own high and low limits, plus a critical
43 two. Each fan channel has its own low speed limit.
|
| /openbmc/linux/Documentation/arch/mips/ |
| H A D | ingenic-tcu.rst | 18 - Each one of the TCU channels has its own clock, which can be reparented to three
45 own interrupt line; channels 2-7 share the last interrupt line.
46 - On JZ4725B, channel 0 has its own interrupt; channels 1-5 share one
48 - on newer SoCs (JZ4750 and above), channel 5 has its own interrupt;
|
| /openbmc/linux/Documentation/driver-api/usb/ |
| H A D | typec.rst | 30 Every port will be presented as its own device under /sys/class/typec/. The
33 When connected, the partner will be presented also as its own device under
39 The cable and the two plugs on it may also be optionally presented as their own
47 Alternate Mode SVID will have their own device describing them. Note that the
51 Every mode that is supported will have its own group under the Alternate Mode
110 The plugs are represented as their own devices. The cable is registered first,
172 own functions, but the registration will always return a handle to struct
201 own logical components: "mux" for the mode and "switch" for the orientation.
|
| /openbmc/openbmc/poky/documentation/migration-guides/ |
| H A D | migration-3.3.rst | 133 - ``iproute2``: split ``ip`` binary to its own package
134 - ``net-tools``: split ``mii-tool`` into its own package
135 - ``procps``: split ``ps`` and ``sysctl`` into their own packages
139 - ``util-linux``: ``libuuid`` has been split out to its own
153 of course specify your own :term:`DISTRO_VERSION` value as desired
154 (particularly if you create your own custom distro configuration).
|
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A D | ext-ctrls-detect.rst | 37 - The image is divided into a grid, each cell with its own motion
41 - The image is divided into a grid, each cell with its own region
43 should be used. Each region has its own thresholds. How these
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | edid.rst | 19 - A KVM sends its own EDID data instead of querying the connected monitor.
39 If you want to create your own EDID file, copy the file 1024x768.S,
40 replace the settings with your own data and add a new target to the
|
| /openbmc/linux/drivers/media/pci/ttpci/ |
| H A D | Kconfig | 33 Say Y if you own such a card and want to use it.
60 Say Y if you own such a card and want to use it.
83 Say Y if you own such a card and want to use it.
|
| /openbmc/linux/tools/testing/selftests/net/forwarding/ |
| H A D | bridge_mdb.sh | 839 $MZ $mode $h1.10 -a own -b $dmac -c 1 -p 128 -A $src -B $grp -t udp -q
846 $MZ $mode $h1.10 -a own -b $dmac -c 1 -p 128 -A $src -B $grp -t udp -q
852 $MZ $mode $h1.10 -a own -b $dmac -c 1 -p 128 -A $src -B $grp -t udp -q
859 $MZ $mode $h1.10 -a own -b $dmac -c 1 -p 128 -A $src -B $grp -t udp -q
887 $MZ $h1.10 -c 1 -p 128 -a own -b $dmac -q
894 $MZ $h1.10 -c 1 -p 128 -a own -b $dmac -q
900 $MZ $h1.10 -c 1 -p 128 -a own -b $dmac -q
907 $MZ $h1.10 -c 1 -p 128 -a own -b $dmac -q
967 $MZ $mode $h1.10 -a own -b $dmac -c 1 -p 128 -A $valid_src -B $grp -t udp -q
971 $MZ $mode $h1.10 -a own -b $dmac -c 1 -p 128 -A $invalid_src -B $grp -t udp -q
[all …]
|
| H A D | tc_flower_l2_miss.sh | 89 $MZ $h1 -a own -b $dmac -t ip -A $sip -B $dip -c 1 -p 100 -q
100 $MZ $h1 -a own -b $dmac -t ip -A $sip -B $dip -c 1 -p 100 -q
111 $MZ $h1 -a own -b $dmac -t ip -A $sip -B $dip -c 1 -p 100 -q
146 $MZ $mode $h1 -a own -b $dmac -t ip -A $sip -B $dip -c 1 -p 100 -q
157 $MZ $mode $h1 -a own -b $dmac -t ip -A $sip -B $dip -c 1 -p 100 -q
168 $MZ $mode $h1 -a own -b $dmac -t ip -A $sip -B $dip -c 1 -p 100 -q
258 $MZ $mode $h1 -a own -b $dmac -t ip -A $sip -B $dip -c 1 -p 100 -q
|
| /openbmc/linux/tools/testing/selftests/drivers/net/dsa/ |
| H A D | bridge_mdb.sh | 839 $MZ $mode $h1.10 -a own -b $dmac -c 1 -p 128 -A $src -B $grp -t udp -q
846 $MZ $mode $h1.10 -a own -b $dmac -c 1 -p 128 -A $src -B $grp -t udp -q
852 $MZ $mode $h1.10 -a own -b $dmac -c 1 -p 128 -A $src -B $grp -t udp -q
859 $MZ $mode $h1.10 -a own -b $dmac -c 1 -p 128 -A $src -B $grp -t udp -q
887 $MZ $h1.10 -c 1 -p 128 -a own -b $dmac -q
894 $MZ $h1.10 -c 1 -p 128 -a own -b $dmac -q
900 $MZ $h1.10 -c 1 -p 128 -a own -b $dmac -q
907 $MZ $h1.10 -c 1 -p 128 -a own -b $dmac -q
967 $MZ $mode $h1.10 -a own -b $dmac -c 1 -p 128 -A $valid_src -B $grp -t udp -q
971 $MZ $mode $h1.10 -a own -b $dmac -c 1 -p 128 -A $invalid_src -B $grp -t udp -q
[all …]
|
| /openbmc/linux/Documentation/process/ |
| H A D | 6.Followthrough.rst | 7 addition of your own engineering skills, have posted a perfect series of
48 agendas at the expense of your own. Kernel developers often expect to
63 making. Do not let their form of expression or your own pride keep that
76 be easy to become blinded by your own solution to a problem to the point
117 subsystem to the next; each maintainer has his or her own way of doing
149 Merging into the mainline brings its own challenges.
200 your own), or send an Acked-by: response back and let the original poster
|
| /openbmc/linux/Documentation/riscv/ |
| H A D | patch-acceptance.rst | 44 ECR. (Developers may, of course, maintain their own Linux kernel trees
48 their own custom extensions. These custom extensions aren't required
58 (Implementers, may, of course, maintain their own Linux kernel trees containing
|
| /openbmc/linux/drivers/media/usb/dvb-usb/ |
| H A D | Kconfig | 16 Say Y if you own a USB DVB device.
66 Say Y if you own such a device and want to use it.
135 Say Y if you own such a device and want to use it. You should build it as
162 Say Y if you own such a device and want to use it. You should build it as
183 Say Y if you own such a device and want to use it. You should build it as
288 Say Y if you own such a device and want to use it.
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | python-ldap | 6 responsible for their own choice and use of this software for their
7 own purposes. By using this software, each user agrees that the
|
| /openbmc/phosphor-fan-presence/ |
| H A D | dbus_paths.hpp | 6 // Control Application's D-Bus busname to own
13 // Thermal Application's D-Bus busname to own
|
| /openbmc/linux/Documentation/driver-api/serial/ |
| H A D | driver.rst | 34 their own version.
88 allow low level drivers to register their own individual uart_port's with
90 structure containing both the uart_port entry with their own extensions,
|
| /openbmc/linux/tools/testing/selftests/net/ |
| H A D | test_vxlan_mdb.sh | 1006 …run_cmd "ip netns exec $ns1 $mz br0.10 -a own -b $grp_dmac -A $src -B $grp -t udp sp=12345,dp=5432…
1010 …run_cmd "ip netns exec $ns1 $mz br0.20 -a own -b $grp_dmac -A $src -B $grp -t udp sp=12345,dp=5432…
1023 …run_cmd "ip netns exec $ns1 $mz br0.10 -a own -b $grp_dmac -A $src -B $grp -t udp sp=12345,dp=5432…
1027 …run_cmd "ip netns exec $ns1 $mz br0.20 -a own -b $grp_dmac -A $src -B $grp -t udp sp=12345,dp=5432…
1032 …run_cmd "ip netns exec $ns1 $mz br0.20 -a own -b $grp_dmac -A $src -B $grp -t udp sp=12345,dp=5432…
1036 …run_cmd "ip netns exec $ns1 $mz br0.10 -a own -b $grp_dmac -A $src -B $grp -t udp sp=12345,dp=5432…
1049 …run_cmd "ip netns exec $ns1 $mz br0.10 -a own -b $grp_dmac -A $src -B $grp -t udp sp=12345,dp=5432…
1053 …run_cmd "ip netns exec $ns1 $mz br0.20 -a own -b $grp_dmac -A $src -B $grp -t udp sp=12345,dp=5432…
1061 …run_cmd "ip netns exec $ns1 $mz br0.10 -a own -b $grp_dmac -A $src -B $grp -t udp sp=12345,dp=5432…
1065 …run_cmd "ip netns exec $ns1 $mz br0.20 -a own -b $grp_dmac -A $src -B $grp -t udp sp=12345,dp=5432…
[all …]
|
| /openbmc/linux/tools/testing/selftests/tc-testing/ |
| H A D | tdc_config.py | 11 # Substitute your own tc path here
13 # Substitute your own ip path here
|