Searched hist:cbac9a36 (Results 1 – 2 of 2) sorted by relevance
/freebsd/sys/dev/enetc/ |
H A D | enetc.h | cbac9a36 Mon Nov 29 11:57:24 GMT 2021 Kornel Duleba <mindal@semihalf.com> enetc: Serialize MDIO transactions
In theory we can have multiple concurrent accesses to the MDIO bus, e.g. link status check tick and ifconfig request. In that case we need to make sure that all MDIO transaction are serialized.
Obtained from: Semihalf Sponsored by: Alstom Group cbac9a36 Mon Nov 29 11:57:24 GMT 2021 Kornel Duleba <mindal@semihalf.com> enetc: Serialize MDIO transactions
In theory we can have multiple concurrent accesses to the MDIO bus, e.g. link status check tick and ifconfig request. In that case we need to make sure that all MDIO transaction are serialized.
Obtained from: Semihalf Sponsored by: Alstom Group cbac9a36 Mon Nov 29 11:57:24 GMT 2021 Kornel Duleba <mindal@semihalf.com> enetc: Serialize MDIO transactions
In theory we can have multiple concurrent accesses to the MDIO bus, e.g. link status check tick and ifconfig request. In that case we need to make sure that all MDIO transaction are serialized.
Obtained from: Semihalf Sponsored by: Alstom Group cbac9a36 Mon Nov 29 11:57:24 GMT 2021 Kornel Duleba <mindal@semihalf.com> enetc: Serialize MDIO transactions
In theory we can have multiple concurrent accesses to the MDIO bus, e.g. link status check tick and ifconfig request. In that case we need to make sure that all MDIO transaction are serialized.
Obtained from: Semihalf Sponsored by: Alstom Group cbac9a36 Mon Nov 29 11:57:24 GMT 2021 Kornel Duleba <mindal@semihalf.com> enetc: Serialize MDIO transactions
In theory we can have multiple concurrent accesses to the MDIO bus, e.g. link status check tick and ifconfig request. In that case we need to make sure that all MDIO transaction are serialized.
Obtained from: Semihalf Sponsored by: Alstom Group cbac9a36 Mon Nov 29 11:57:24 GMT 2021 Kornel Duleba <mindal@semihalf.com> enetc: Serialize MDIO transactions
In theory we can have multiple concurrent accesses to the MDIO bus, e.g. link status check tick and ifconfig request. In that case we need to make sure that all MDIO transaction are serialized.
Obtained from: Semihalf Sponsored by: Alstom Group cbac9a36 Mon Nov 29 11:57:24 GMT 2021 Kornel Duleba <mindal@semihalf.com> enetc: Serialize MDIO transactions
In theory we can have multiple concurrent accesses to the MDIO bus, e.g. link status check tick and ifconfig request. In that case we need to make sure that all MDIO transaction are serialized.
Obtained from: Semihalf Sponsored by: Alstom Group
|
H A D | if_enetc.c | cbac9a36 Mon Nov 29 11:57:24 GMT 2021 Kornel Duleba <mindal@semihalf.com> enetc: Serialize MDIO transactions
In theory we can have multiple concurrent accesses to the MDIO bus, e.g. link status check tick and ifconfig request. In that case we need to make sure that all MDIO transaction are serialized.
Obtained from: Semihalf Sponsored by: Alstom Group cbac9a36 Mon Nov 29 11:57:24 GMT 2021 Kornel Duleba <mindal@semihalf.com> enetc: Serialize MDIO transactions
In theory we can have multiple concurrent accesses to the MDIO bus, e.g. link status check tick and ifconfig request. In that case we need to make sure that all MDIO transaction are serialized.
Obtained from: Semihalf Sponsored by: Alstom Group cbac9a36 Mon Nov 29 11:57:24 GMT 2021 Kornel Duleba <mindal@semihalf.com> enetc: Serialize MDIO transactions
In theory we can have multiple concurrent accesses to the MDIO bus, e.g. link status check tick and ifconfig request. In that case we need to make sure that all MDIO transaction are serialized.
Obtained from: Semihalf Sponsored by: Alstom Group cbac9a36 Mon Nov 29 11:57:24 GMT 2021 Kornel Duleba <mindal@semihalf.com> enetc: Serialize MDIO transactions
In theory we can have multiple concurrent accesses to the MDIO bus, e.g. link status check tick and ifconfig request. In that case we need to make sure that all MDIO transaction are serialized.
Obtained from: Semihalf Sponsored by: Alstom Group cbac9a36 Mon Nov 29 11:57:24 GMT 2021 Kornel Duleba <mindal@semihalf.com> enetc: Serialize MDIO transactions
In theory we can have multiple concurrent accesses to the MDIO bus, e.g. link status check tick and ifconfig request. In that case we need to make sure that all MDIO transaction are serialized.
Obtained from: Semihalf Sponsored by: Alstom Group cbac9a36 Mon Nov 29 11:57:24 GMT 2021 Kornel Duleba <mindal@semihalf.com> enetc: Serialize MDIO transactions
In theory we can have multiple concurrent accesses to the MDIO bus, e.g. link status check tick and ifconfig request. In that case we need to make sure that all MDIO transaction are serialized.
Obtained from: Semihalf Sponsored by: Alstom Group cbac9a36 Mon Nov 29 11:57:24 GMT 2021 Kornel Duleba <mindal@semihalf.com> enetc: Serialize MDIO transactions
In theory we can have multiple concurrent accesses to the MDIO bus, e.g. link status check tick and ifconfig request. In that case we need to make sure that all MDIO transaction are serialized.
Obtained from: Semihalf Sponsored by: Alstom Group
|