netbsd@precedence.co.uk writes:
> The problem is with the driver for the EtherB ethernet card (eb0 device).
> The problem started on or around 4th June after some changes were made to
> the driver by cgd. The drivers for the Ether1 (ie0) and Ether3 (ea0) were
> also altered, but these have not been tested.

Err, uh, as far as I can tell i've _never_ hacked on that driver, or
even committed anything to it.  (i.e. not even pullup requests for
release branches!)

The only recent ("within the last year") changes to that driver I see
are:

revision 1.22
date: 1999/05/18 23:52:52;  author: thorpej;  state: Exp;  lines: +3 -8
Rework layer 2 protocol input routines.  Instead of calling e.g. ether_input()
directly, call the function pointer (*if_input)(ifp, m).  The input routine
expects the packet header to be at the head of the packet, and will adjust
as necessary.  Privatize the layer 2 input and output routines, allowing
*_ifattach() to set them up as appropriate.
----------------------------
revision 1.21
date: 1999/03/25 23:11:52;  author: thorpej;  state: Exp;  lines: +3 -7
branches:  1.21.4;
Use ETHER_*_LEN constants from <net/if_ether.h> instead of defining them
ourselves.


Is one of those the change you mean?



cgd
-- 
Chris Demetriou - cgd@netbsd.org - http://www.netbsd.org/People/Pages/cgd.html
Disclaimer: Not speaking for NetBSD, just expressing my own opinion.