From owner-freebsd-net@FreeBSD.ORG Thu Jun 10 17:58:42 2010 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D64C910656BF; Thu, 10 Jun 2010 17:58:42 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 632938FC16; Thu, 10 Jun 2010 17:58:41 +0000 (UTC) Received: by vws1 with SMTP id 1so235536vws.13 for ; Thu, 10 Jun 2010 10:58:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=M7h9svc9klY9eJO++7Zff0m0ZCNmiRMhMotcTDRa73Y=; b=GSkeoKl4dF7OiuQpXpnRqwmFahXFoHe0NFZ+/+W11rWRr5X1lY/TQ99WBpmX8UUS0c dpKZ2n/fMZfrEM3JvY+pcR8sud8A1u0K8ZON8bbi6kCSN2J7cPCitERO7GnB0z4QQ7yk SWTsylRBjXu++8T9JXrXiLCqe6faJAS8KFkTE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=YkE+kEFci/nbhJYvKwkOSVmg6ZAzbI8t/Ab3T7tobvniwzQwGjEvoH1ZIoto6Ldup6 aux2ze5CE8BDOeJT1TUun1S//29zT22qXAr3Lv5lT0MP4LhGprgLU7s4sSXLUhDr9GmU wQyJz0jMXvtu4LsRgEiUdUX6mrb/vbjNlAvTw= MIME-Version: 1.0 Received: by 10.224.124.212 with SMTP id v20mr505083qar.278.1276192721137; Thu, 10 Jun 2010 10:58:41 -0700 (PDT) Received: by 10.229.238.199 with HTTP; Thu, 10 Jun 2010 10:58:41 -0700 (PDT) In-Reply-To: References: Date: Thu, 10 Jun 2010 10:58:41 -0700 Message-ID: From: Jack Vogel To: Alexander Sack Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Juli Mallett , freebsd-net@freebsd.org Subject: Re: Dual-rate transceivers with ixgbe? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jun 2010 17:58:42 -0000 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 wrote: > On Thu, Jun 10, 2010 at 1:03 PM, Jack Vogel 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 >