Date: Tue, 24 Jun 2014 12:01:29 -0600 (MDT) From: Warren Block <wblock@wonkity.com> To: sbruno@freebsd.org Cc: "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org> Subject: Re: wireless mcast updates, ic->ic_update_mcast Message-ID: <alpine.BSF.2.11.1406241153050.86197@wonkity.com> In-Reply-To: <1403623187.7781.6.camel@bruno> References: <1403366123.39384.10.camel@bruno> <CAJ-Vmo=1ZstSanGP5zK8tnnOrE_sO4MKNFRcGvCJPJ8MZZL0yA@mail.gmail.com> <1403623187.7781.6.camel@bruno>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 24 Jun 2014, Sean Bruno wrote: > On Sat, 2014-06-21 at 12:47 -0700, Adrian Chadd wrote: >> Well, it depends on what the hardware may want or desire to function >> correctly. I've no idea what theose chips require for multicast >> behaviour. > > I think that was kind of my point of bringing this up. Only a handful > of cards really implement the appropriate code. Most of the rest, > implement stub functions that hide a console print message indicating > missing functionality. > > I propose nuking most of these stub functions and wrapping the console > printf in a bootverbose. FWIW, I agree. That little error-that's-not-an-error is what new users see, and it obviously must be the problem. So not only is it not helping, it often distracts from real problems.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.11.1406241153050.86197>