From owner-freebsd-net@FreeBSD.ORG Thu Sep 23 17:50:44 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 CB4FF106566C for ; Thu, 23 Sep 2010 17:50:44 +0000 (UTC) (envelope-from davidch@broadcom.com) Received: from MMS3.broadcom.com (mms3.broadcom.com [216.31.210.19]) by mx1.freebsd.org (Postfix) with ESMTP id A9B7B8FC1C for ; Thu, 23 Sep 2010 17:50:44 +0000 (UTC) Received: from [10.9.200.131] by MMS3.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Thu, 23 Sep 2010 10:43:54 -0700 X-Server-Uuid: B55A25B1-5D7D-41F8-BC53-C57E7AD3C201 Received: from IRVEXCHCCR01.corp.ad.broadcom.com ([10.252.49.30]) by IRVEXCHHUB01.corp.ad.broadcom.com ([10.9.200.131]) with mapi; Thu, 23 Sep 2010 10:43:54 -0700 From: "David Christensen" To: "Tom Judge" , "freebsd-net@freebsd.org" , "pyunyh@gmail.com" Date: Thu, 23 Sep 2010 10:43:52 -0700 Thread-Topic: bce(4) un hiding adapter info Thread-Index: ActbQnXh18rnYxMKRLeN2bfpYPo7zQAA5b3A Message-ID: <5D267A3F22FD854F8F48B3D2B52381933B5A78B444@IRVEXCHCCR01.corp.ad.broadcom.com> References: <4C9B8A50.9060602@tomjudge.com> In-Reply-To: <4C9B8A50.9060602@tomjudge.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 X-WSS-ID: 60854E503KC115153894-01-01 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Cc: Subject: RE: bce(4) un hiding adapter info 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, 23 Sep 2010 17:50:44 -0000 > Would it be possible to unhide the output of bce_print_adapter_info() > from under boot verbose? >=20 > This information is useful for comparing firmware and card versions > between machines. >=20 > Alternatively what about adding a sysctl under dev.bce.X for this info? I have no problem doing that, just not sure that everyone would appreciate the spew. I like it for exactly the same reason, troubleshooting remote systems. =20 What I'd really like to do is revamp the debug code so that it=20 can be enabled/disabled on the fly rather than requiring that=20 the driver be compiled. Adding some performance stuff would=20 be awesome as well. Dave=20