Re: HEADSUP: internal network interface changes

2005-06-10 Thread Brooks Davis
On Sat, Jun 11, 2005 at 10:01:33AM +1200, Andrew Thompson wrote: > On Fri, Jun 10, 2005 at 09:57:24AM -0700, Brooks Davis wrote: > > On Fri, Jun 10, 2005 at 09:26:00AM -0700, Brooks Davis wrote: > > > Look out! :-) > > > > > > This change is incoming sortly (pending final cvs updates). > > > > I'

Re: HEADSUP: internal network interface changes

2005-06-10 Thread Andrew Thompson
On Fri, Jun 10, 2005 at 09:57:24AM -0700, Brooks Davis wrote: > On Fri, Jun 10, 2005 at 09:26:00AM -0700, Brooks Davis wrote: > > Look out! :-) > > > > This change is incoming sortly (pending final cvs updates). > > I've committed the change bumping __FreeBSD_version. Hopefully the > ride won't

Re: HEADSUP: internal network interface changes

2005-06-10 Thread Brooks Davis
On Fri, Jun 10, 2005 at 09:26:00AM -0700, Brooks Davis wrote: > Look out! :-) > > This change is incoming sortly (pending final cvs updates). I've committed the change bumping __FreeBSD_version. Hopefully the ride won't be too bumpy. If you have any problems, please report them on -current as w

Re: HEADSUP: internal network interface changes

2005-06-10 Thread Brooks Davis
Look out! :-) This change is incoming sortly (pending final cvs updates). -- Brooks On Wed, Jun 08, 2005 at 11:44:52PM -0700, Brooks Davis wrote: > I plan to commit a major rework of network interface related storage > Friday morning PDT. This is a massive change touching every network > driver

Re: HEADSUP: internal network interface changes

2005-06-09 Thread Brooks Davis
On Thu, Jun 09, 2005 at 10:25:30AM +0200, Maxim Sobolev wrote: > Hi, > > I've noticed that in some cases you have removed bcopy() > into arpcom.ac_enaddr completely, while in some others > have modified it to use IFP2AC(). I wonder if it's a mistake > or if there is some logic behind that. Good c

Re: HEADSUP: internal network interface changes

2005-06-09 Thread Maxim Sobolev
On Thu, Jun 09, 2005 at 10:25:30AM +0200, Maxim Sobolev wrote: > Also, it looks like in cdce(4) driver you are referencing > if_softc before it's been assigned by if_alloc(): <- cdce_ifp -Maxim ___ freebsd-net@freebsd.org mailing list http://l

Re: HEADSUP: internal network interface changes

2005-06-09 Thread Maxim Sobolev
Hi, I've noticed that in some cases you have removed bcopy() into arpcom.ac_enaddr completely, while in some others have modified it to use IFP2AC(). I wonder if it's a mistake or if there is some logic behind that. Also, it looks like in cdce(4) driver you are referencing if_softc before it's be