Searched refs:collisions (Results 1 – 14 of 14) sorted by relevance
62 TX errors 0 dropped 0 overruns 0 carrier 0 collisions 071 TX errors 0 dropped 0 overruns 0 carrier 0 collisions 080 TX errors 8 dropped 8 overruns 0 carrier 8 collisions 089 TX errors 7 dropped 0 overruns 0 carrier 0 collisions 098 TX errors 7 dropped 7 overruns 0 carrier 0 collisions 0
451 net_stats_t collisions; member
84 at 0x10000. Even given collisions, this is probably tolerable, as we
171 `STM32H7B3I_DK board schematics`_ for possible collisions if using that connector.
108 To avoid collisions with user defined descriptors, the standard descriptors were alloted
138 collisions:0 txqueuelen:1000
167 tags (e.g. 2^64) to finally be able to look for collisions and benefit
88 arbitration phase. During the arbitration phase, write collisions are allowed.
1259 Rule A.3: Macro name collisions1271 not be modified or protected to avoid name collisions with other1284 Finally, this rule applies to inter-module name collisions as well: in that case1298 to avoid collisions.
109 * Makefile: Changed outdir into board-specific directory to avoid build collisions.
202 * Added full virtual addresses support with the collisions resolution. The
5 # before using them to avoid name-space collisions.
1042 be used in resolving collisions.
899 PR("Collisions : %u\n", data->collisions); in print_eth_stats()
