Home
last modified time | relevance | path

Searched refs:own (Results 1 – 25 of 1497) sorted by relevance

12345678910>>...60

/openbmc/linux/tools/testing/selftests/drivers/net/mlxsw/
H A Ddevlink_trap_control.sh222 $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 …]
H A Ddevlink_trap_l2_drops.sh131 $MZ $h1 "$opt" -c 0 -p 100 -a own -b $dmac -t ip -d 1msec -q &
191 $MZ $h1 -Q $vid -c 0 -p 100 -a own -b $dmac -t ip -d 1msec -q &
234 $MZ $h1 -Q $vid -c 0 -p 100 -a own -b $dmac -t ip -d 1msec -q &
304 $MZ $h1 -c 0 -p 100 -a own -b $dmac -t ip -d 1msec -q &
349 $MZ $h1 -c 0 -p 100 -a own -b $dmac -t ip -B $dip -d 1msec -q &
395 $MZ $h1 -c 0 -p 100 -a own -b $dmac -t ip -d 1msec -q &
/openbmc/linux/drivers/net/fddi/
H A Ddefza.c449 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/openbmc/poky/documentation/
H A Dtransitioning-to-a-custom-environment.rst14 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/testing/selftests/net/forwarding/
H A Dtc_flower_l2_miss.sh89 $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
H A Dsch_red.sh187 $MZ $h2 -p $PKTSZ -a own -b $h3_mac -A 192.0.2.2 -B 192.0.2.3 -t $proto -q -c $pkts "$@"
289 -a own -b $h3_mac -t tcp -q tos=0x01 &
312 -a own -b $h3_mac -t tcp -q tos=0x01 &
338 -a own -b $h3_mac -t tcp -q tos=0x01 &
371 -a own -b $h3_mac -t udp -q &
412 -a own -b $h3_mac -t tcp -q tos=0x01 &
H A Dbridge_mdb.sh839 $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 Dhw_stats_l3.sh171 -a own -b $rp1mac -A 192.0.2.1 -B 192.0.2.18 \
178 -a own -b $rp1mac -A 2001:db8:1::1 -B 2001:db8:2::1 \
185 -a own -b $rp2mac -A 192.0.2.18 -B 192.0.2.1 \
192 -a own -b $rp2mac -A 2001:db8:2::1 -B 2001:db8:1::1 \
H A Dtc_police.sh136 mausezahn $h1 -a own -b $(mac_get $rp1) -A 192.0.2.1 -B 198.51.100.1 \
186 mausezahn $h1 -a own -b $(mac_get $rp1) -A 192.0.2.1 -B 198.51.100.1 \
256 mausezahn $h1 -a own -b $(mac_get $rp1) -A 192.0.2.1 -B 198.51.100.1 \
308 mausezahn $h1 -a own -b $(mac_get $rp1) -A 192.0.2.1 -B 198.51.100.1 \
367 mausezahn $h1 -a own -b $(mac_get $rp1) -A 192.0.2.1 -B 198.51.100.1 \
370 mausezahn $h1 -a own -b $(mac_get $rp1) -A 192.0.2.1 -B 198.51.100.1 \
/openbmc/linux/Documentation/hwmon/
H A Dadm1031.rst33 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/tools/testing/selftests/drivers/net/dsa/
H A Dbridge_mdb.sh839 $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/openbmc/poky/documentation/dev-manual/
H A Dcustom-distribution.rst16 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/linux/Documentation/arch/mips/
H A Dingenic-tcu.rst18 - 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/userspace-api/media/v4l/
H A Dext-ctrls-detect.rst37 - 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/openbmc/poky/meta/files/common-licenses/
H A Dpython-ldap6 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-ipmi-flash/
H A Dbmc_json_config.md14 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 DKconfig50 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/openbmc/poky/documentation/kernel-dev/
H A Dfaq.rst12 How do I use my own Linux kernel ``.config`` file?
26 How do I use my own Linux kernel sources?
30 ":ref:`kernel-dev/common:working with your own sources`"
/openbmc/linux/drivers/i2c/busses/
H A Di2c-elektor.c42 static int own = 0x55; variable
86 return (own); in pcf_isa_getown()
319 module_param(own, int, 0);
/openbmc/qemu/tests/
H A Ddbus-vmstate-daemon.sh34 <deny own="*"/>
65 <allow own="org.qemu.VMState1"/>
/openbmc/linux/drivers/isdn/mISDN/
H A Dstack.c388 dev->teimgr->peer = &newst->own; in create_stack()
393 dev->D.peer = &newst->own; in create_stack()
394 newst->own.st = newst; in create_stack()
395 newst->own.ctrl = st_own_ctrl; in create_stack()
396 newst->own.send = mISDN_queue_message; in create_stack()
397 newst->own.recv = mISDN_queue_message; in create_stack()
435 ch->peer = &dev->D.st->own; in connect_layer1()
534 ch->peer = &dev->D.st->own; in create_l2entity()
551 rq.ch->peer = &dev->D.st->own; in create_l2entity()
/openbmc/linux/Documentation/tools/rv/
H A Drv-mon.rst21 has its own set of options. The **rv list** command shows all available
37 Each monitor has its own set of options. See man **rv-mon**-*monitor_name*
/openbmc/openbmc/poky/documentation/migration-guides/
H A Dmigration-3.3.rst133 - ``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/admin-guide/
H A Dedid.rst19 - 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/Documentation/networking/
H A Dtc-actions-env-rules.rst18 someone else is referencing the skb. After that you "own" the skb.
20 3) Dropping packets you don't own is a no-no. You simply return

12345678910>>...60