Home
last modified time | relevance | path

Searched refs:TPID (Results 1 – 5 of 5) sorted by relevance

/Linux-v5.4/Documentation/bpf/
Dprog_flow_dissector.rst63 | DMAC | SMAC | TPID | TCI |ETHER_TYPE | L3_HEADER |
73 flow_keys->n_proto = TPID
75 Please note that TPID can be 802.1AD and, hence, BPF program would
82 | DMAC | SMAC | TPID | TCI |ETHER_TYPE | L3_HEADER |
/Linux-v5.4/Documentation/networking/dsa/
Dsja1105.rst70 customizing the TPID by which VLAN traffic is identified as such. The switch
72 VLANs (with a custom TPID of ``ETH_P_EDSA`` instead of ``ETH_P_8021Q``) are
75 because the switch does no longer parse those packets as VLAN after the TPID
77 The TPID is restored when ``vlan_filtering`` is requested by the user through
116 by changing what TPID the switch searches 802.1Q tags for, the semantics of a
/Linux-v5.4/drivers/platform/x86/
Dthinkpad_acpi.c443 #define TPID(__c1, __c2) (((__c1) << 8) | (__c2)) macro
445 #define TPVER TPID
449 .bios = TPID(__id1, __id2), \
455 .bios = TPID(__id1, __id2), \
468 .ec = TPID(__id1, __id2), \
474 .ec = TPID(__id1, __id2), \
1648 .bios = TPID(__id1, __id2), \
1656 .bios = TPID(__bid1, __bid2), \
1667 __bv1, __bv2, TPID(__id1, __id2), \
1677 __bv1, __bv2, TPID(__eid1, __eid2), \
[all …]
/Linux-v5.4/Documentation/networking/
Dopenvswitch.txt165 the 802.1Q TPID (0x8100) as the Ethertype then stopped parsing the
Dpacket_mmap.txt546 indicates that the tp_vlan_tpid field has valid VLAN TPID value