Date: Tue, 15 May 2001 14:24:03 -0500 (CDT) From: Jonathan Lemon <jlemon@flugsvamp.com> To: holtor@yahoo.com, stable@freebsd.org Subject: Re: Recent fxp Driver Changes Message-ID: <200105151924.f4FJO3A05849@prism.flugsvamp.com> In-Reply-To: <local.mail.freebsd-stable/20010515171734.28209.qmail@web11604.mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <local.mail.freebsd-stable/20010515171734.28209.qmail@web11604.mail.yahoo.com> you write: >Hi All, > >First i'd like to say i've used the fxp driver for >years and years and its always worked flawlessly. > >Now, why in the world would we allow these commits >to include common code and other things that obviously >have broken things for many people. > >I like the suggestion someone else mentioned. fxp >should >be left alone. And a new driver created such as fxm >for the fxp with mibus and those things. If the new driver was dissimilar enough, this would be the approach that should be taken. However, the drivers are mostly similar except in their PHY handling, so doing this doesn't really make sense from a support perspective. >What happened to the old saying? > >If it aint broke, then don't fix it? Well, the problem is that the fxp driver was broke, in the sense that support for the newer fxp cards was lacking. I will admit that bringing the bits in from -current did not go as smoothly as I would have liked, but I think that everything is settled now, except possibly the VLAN and 815E issues. However, note that neither of these worked in the old driver, so this isn't a step backwards. I've already had reports from some users who are now able to use their newer 82559 boards which were not recognized by the older driver, so this is an improvement for them. >I'm a bit concerned over this. Our best driver has now >turned into one of the worst troublesome drivers like >the 3com xl0. I think that's stretching things a bit. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200105151924.f4FJO3A05849>