Date: Thu, 23 Sep 2010 11:20:33 -0700 From: Pyun YongHyeon <pyunyh@gmail.com> To: David Christensen <davidch@broadcom.com> Cc: Tom Judge <tom@tomjudge.com>, "freebsd-net@freebsd.org" <freebsd-net@freebsd.org> Subject: Re: bce(4) un hiding adapter info Message-ID: <20100923182033.GA15014@michelle.cdnetworks.com> In-Reply-To: <5D267A3F22FD854F8F48B3D2B52381933B5A78B444@IRVEXCHCCR01.corp.ad.broadcom.com> References: <4C9B8A50.9060602@tomjudge.com> <5D267A3F22FD854F8F48B3D2B52381933B5A78B444@IRVEXCHCCR01.corp.ad.broadcom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Sep 23, 2010 at 10:43:52AM -0700, David Christensen wrote: > > Would it be possible to unhide the output of bce_print_adapter_info() > > from under boot verbose? > > > > This information is useful for comparing firmware and card versions > > between machines. > > > > 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. > I also like to see that. It would just add one informational line and it wouldn't hurt. > What I'd really like to do is revamp the debug code so that it > can be enabled/disabled on the fly rather than requiring that > the driver be compiled. Adding some performance stuff would Couldn't it be implemented with sysctl? Users may set a variable something like dev.bce.0.diag_bitmap to activate debugging code. But it seems that requires a lot of code changes. > be awesome as well. > > Dave > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100923182033.GA15014>