I believe I've explained this once before. The limitation code is put in explicitly because its what we support and all we support, we know that some hardware out there will not work, some may.
If you buy the hardware you would be wise to make sure you get what's supported, but please don't ask me how to hack around it or what it means when you have problems when you do. In the first place I dont have the time, second, I do not have the hardware or means to test that, and finally I need to abide by what my management tells me... you do all want me to keep my job yes? :) Cheers, Jack On Thu, Jun 10, 2010 at 10:14 AM, Alexander Sack <pisym...@gmail.com> wrote: > On Thu, Jun 10, 2010 at 1:03 PM, Jack Vogel <jfvo...@gmail.com> wrote: > > Well, em doesn't have a pluggable phy :) Hardware is different, that's > why > > there's > > a different driver.... > > Thanks Juli/Jack. I didn't know that! And knowing is half the battle... > > So, not to completely hijack Juli's thread (sorry), but what about > these SFP issues. What was the point of the code I mentioned? Am I > living that dangerously commenting it out? What's the real fix here? > > -aps > _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
