Orange Pi5 kernel

^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  1) =============================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  2) IBM s390 QDIO Ethernet Driver
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  3) =============================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  4) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  5) OSA and HiperSockets Bridge Port Support
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  6) ========================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  7) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  8) Uevents
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  9) -------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 10) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 11) To generate the events the device must be assigned a role of either
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 12) a primary or a secondary Bridge Port. For more information, see
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 13) "z/VM Connectivity, SC24-6174".
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 14) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 15) When run on an OSA or HiperSockets Bridge Capable Port hardware, and the state
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 16) of some configured Bridge Port device on the channel changes, a udev
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 17) event with ACTION=CHANGE is emitted on behalf of the corresponding
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 18) ccwgroup device. The event has the following attributes:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 19) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 20) BRIDGEPORT=statechange
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 21)   indicates that the Bridge Port device changed
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 22)   its state.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 23) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 24) ROLE={primary|secondary|none}
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 25)   the role assigned to the port.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 26) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 27) STATE={active|standby|inactive}
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 28)   the newly assumed state of the port.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 29) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 30) When run on HiperSockets Bridge Capable Port hardware with host address
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 31) notifications enabled, a udev event with ACTION=CHANGE is emitted.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 32) It is emitted on behalf of the corresponding ccwgroup device when a host
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 33) or a VLAN is registered or unregistered on the network served by the device.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 34) The event has the following attributes:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 35) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 36) BRIDGEDHOST={reset|register|deregister|abort}
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 37)   host address
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 38)   notifications are started afresh, a new host or VLAN is registered or
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 39)   deregistered on the Bridge Port HiperSockets channel, or address
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 40)   notifications are aborted.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 41) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 42) VLAN=numeric-vlan-id
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 43)   VLAN ID on which the event occurred. Not included
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 44)   if no VLAN is involved in the event.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 45) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 46) MAC=xx:xx:xx:xx:xx:xx
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 47)   MAC address of the host that is being registered
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 48)   or deregistered from the HiperSockets channel. Not reported if the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 49)   event reports the creation or destruction of a VLAN.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 50) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 51) NTOK_BUSID=x.y.zzzz
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 52)   device bus ID (CSSID, SSID and device number).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 53) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 54) NTOK_IID=xx
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 55)   device IID.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 56) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 57) NTOK_CHPID=xx
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 58)   device CHPID.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 59) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 60) NTOK_CHID=xxxx
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 61)   device channel ID.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 62) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 63) Note that the `NTOK_*` attributes refer to devices other than  the one
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 64) connected to the system on which the OS is running.