"d4e576c4" (history) in projects: freebsd

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched hist:d4e576c4 (Results 1 – 2 of 2) sorted by relevance

/freebsd/sys/dev/my/
H A D	if_myreg.h	d4e576c4 Thu Nov 19 18:43:43 GMT 2009 John Baldwin <jhb@FreeBSD.org> - This driver used the if_watchdog timer both as a watchdog on transmit and auto-negotiation. To make this simpler and easier to understand I have split this out into two separate timers. One just manages the auto-neg side of things and one is a transmit watchdog. Neither uses if_watchdog. - Call ether_ifdetach() at the start of detach. d4e576c4 Thu Nov 19 18:43:43 GMT 2009 John Baldwin <jhb@FreeBSD.org> - This driver used the if_watchdog timer both as a watchdog on transmit and auto-negotiation. To make this simpler and easier to understand I have split this out into two separate timers. One just manages the auto-neg side of things and one is a transmit watchdog. Neither uses if_watchdog. - Call ether_ifdetach() at the start of detach. d4e576c4 Thu Nov 19 18:43:43 GMT 2009 John Baldwin <jhb@FreeBSD.org> - This driver used the if_watchdog timer both as a watchdog on transmit and auto-negotiation. To make this simpler and easier to understand I have split this out into two separate timers. One just manages the auto-neg side of things and one is a transmit watchdog. Neither uses if_watchdog. - Call ether_ifdetach() at the start of detach. d4e576c4 Thu Nov 19 18:43:43 GMT 2009 John Baldwin <jhb@FreeBSD.org> - This driver used the if_watchdog timer both as a watchdog on transmit and auto-negotiation. To make this simpler and easier to understand I have split this out into two separate timers. One just manages the auto-neg side of things and one is a transmit watchdog. Neither uses if_watchdog. - Call ether_ifdetach() at the start of detach. d4e576c4 Thu Nov 19 18:43:43 GMT 2009 John Baldwin <jhb@FreeBSD.org> - This driver used the if_watchdog timer both as a watchdog on transmit and auto-negotiation. To make this simpler and easier to understand I have split this out into two separate timers. One just manages the auto-neg side of things and one is a transmit watchdog. Neither uses if_watchdog. - Call ether_ifdetach() at the start of detach. d4e576c4 Thu Nov 19 18:43:43 GMT 2009 John Baldwin <jhb@FreeBSD.org> - This driver used the if_watchdog timer both as a watchdog on transmit and auto-negotiation. To make this simpler and easier to understand I have split this out into two separate timers. One just manages the auto-neg side of things and one is a transmit watchdog. Neither uses if_watchdog. - Call ether_ifdetach() at the start of detach. d4e576c4 Thu Nov 19 18:43:43 GMT 2009 John Baldwin <jhb@FreeBSD.org> - This driver used the if_watchdog timer both as a watchdog on transmit and auto-negotiation. To make this simpler and easier to understand I have split this out into two separate timers. One just manages the auto-neg side of things and one is a transmit watchdog. Neither uses if_watchdog. - Call ether_ifdetach() at the start of detach.
H A D	if_my.c	d4e576c4 Thu Nov 19 18:43:43 GMT 2009 John Baldwin <jhb@FreeBSD.org> - This driver used the if_watchdog timer both as a watchdog on transmit and auto-negotiation. To make this simpler and easier to understand I have split this out into two separate timers. One just manages the auto-neg side of things and one is a transmit watchdog. Neither uses if_watchdog. - Call ether_ifdetach() at the start of detach. d4e576c4 Thu Nov 19 18:43:43 GMT 2009 John Baldwin <jhb@FreeBSD.org> - This driver used the if_watchdog timer both as a watchdog on transmit and auto-negotiation. To make this simpler and easier to understand I have split this out into two separate timers. One just manages the auto-neg side of things and one is a transmit watchdog. Neither uses if_watchdog. - Call ether_ifdetach() at the start of detach. d4e576c4 Thu Nov 19 18:43:43 GMT 2009 John Baldwin <jhb@FreeBSD.org> - This driver used the if_watchdog timer both as a watchdog on transmit and auto-negotiation. To make this simpler and easier to understand I have split this out into two separate timers. One just manages the auto-neg side of things and one is a transmit watchdog. Neither uses if_watchdog. - Call ether_ifdetach() at the start of detach. d4e576c4 Thu Nov 19 18:43:43 GMT 2009 John Baldwin <jhb@FreeBSD.org> - This driver used the if_watchdog timer both as a watchdog on transmit and auto-negotiation. To make this simpler and easier to understand I have split this out into two separate timers. One just manages the auto-neg side of things and one is a transmit watchdog. Neither uses if_watchdog. - Call ether_ifdetach() at the start of detach. d4e576c4 Thu Nov 19 18:43:43 GMT 2009 John Baldwin <jhb@FreeBSD.org> - This driver used the if_watchdog timer both as a watchdog on transmit and auto-negotiation. To make this simpler and easier to understand I have split this out into two separate timers. One just manages the auto-neg side of things and one is a transmit watchdog. Neither uses if_watchdog. - Call ether_ifdetach() at the start of detach. d4e576c4 Thu Nov 19 18:43:43 GMT 2009 John Baldwin <jhb@FreeBSD.org> - This driver used the if_watchdog timer both as a watchdog on transmit and auto-negotiation. To make this simpler and easier to understand I have split this out into two separate timers. One just manages the auto-neg side of things and one is a transmit watchdog. Neither uses if_watchdog. - Call ether_ifdetach() at the start of detach. d4e576c4 Thu Nov 19 18:43:43 GMT 2009 John Baldwin <jhb@FreeBSD.org> - This driver used the if_watchdog timer both as a watchdog on transmit and auto-negotiation. To make this simpler and easier to understand I have split this out into two separate timers. One just manages the auto-neg side of things and one is a transmit watchdog. Neither uses if_watchdog. - Call ether_ifdetach() at the start of detach.