From owner-freebsd-wireless@FreeBSD.ORG  Tue Jun 24 18:50:58 2014
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
Delivered-To: freebsd-wireless@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 646C713B;
 Tue, 24 Jun 2014 18:50:58 +0000 (UTC)
Received: from mail-qc0-x230.google.com (mail-qc0-x230.google.com
 [IPv6:2607:f8b0:400d:c01::230])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 13D202BCA;
 Tue, 24 Jun 2014 18:50:58 +0000 (UTC)
Received: by mail-qc0-f176.google.com with SMTP id w7so710783qcr.7
 for <multiple recipients>; Tue, 24 Jun 2014 11:50:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:sender:in-reply-to:references:date:message-id:subject
 :from:to:cc:content-type;
 bh=ZpUp6InR4WztmmrH5cPce3bEL3tZrWd5P3yrB+FCmoU=;
 b=b3xHIzEpbrLu40edbfU9dMezz+V5nDACbES/YP/iDr2G/dw72fw58841qW2Lj5wa1n
 La/G6RUa+lBM1vNtY2ajuJTgdvHjY8fA2cm3c9PfpY+ciamP8GXPT2WU+/Xkg3Iu4UyX
 neKu7Zb/iIk5RgJfYWebPndXwZlg1uBAE3QkMzk/04ySibHybVuBEAzR0Dl2bMT71GYR
 wQyJ6n/uZTiII6LWpgtl/yVNstSYfq1+GvK2Wz9v3UTFXFdTCivbjNgRPZJ1J3hgn0T3
 7q5mDj+t+0KsUXx7iJPCqUU+Vir4Rs5ZbChs4fodFiVQQQvDyfOD7tVamB7w/Of2IJhb
 ipbQ==
MIME-Version: 1.0
X-Received: by 10.224.130.201 with SMTP id u9mr4729489qas.98.1403635857125;
 Tue, 24 Jun 2014 11:50:57 -0700 (PDT)
Sender: adrian.chadd@gmail.com
Received: by 10.224.43.134 with HTTP; Tue, 24 Jun 2014 11:50:57 -0700 (PDT)
In-Reply-To: <alpine.BSF.2.11.1406241153050.86197@wonkity.com>
References: <1403366123.39384.10.camel@bruno>
 <CAJ-Vmo=1ZstSanGP5zK8tnnOrE_sO4MKNFRcGvCJPJ8MZZL0yA@mail.gmail.com>
 <1403623187.7781.6.camel@bruno>
 <alpine.BSF.2.11.1406241153050.86197@wonkity.com>
Date: Tue, 24 Jun 2014 11:50:57 -0700
X-Google-Sender-Auth: rXh2KvPiu_sgE_7fN2KQlcEbf0E
Message-ID: <CAJ-Vmomezj=PW5T4q57zuzJRMOahPu8s7Gp8bVfHhGF51oUK-Q@mail.gmail.com>
Subject: Re: wireless mcast updates, ic->ic_update_mcast
From: Adrian Chadd <adrian@freebsd.org>
To: Warren Block <wblock@wonkity.com>
Content-Type: text/plain; charset=UTF-8
Cc: "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org>
X-BeenThere: freebsd-wireless@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: "Discussions of 802.11 stack,
 tools device driver development." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-wireless>, 
 <mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless/>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>, 
 <mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jun 2014 18:50:58 -0000

Cool. Wrap it up in bootverbose. Hm, or what about a print_once kind of thing?


As far as I can briefly tell, the drivers -should- work with multicast
as long as they're treating it like broadcast traffic and not
requiring that you program a multicast filter for specific link-local
things. The problem is that noone has gone through and verified that
is indeed the case.


-a


On 24 June 2014 11:01, Warren Block <wblock@wonkity.com> wrote:
> 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.