From owner-freebsd-wireless@freebsd.org Fri Jan 11 19:23:07 2019 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BCE041499EF9 for ; Fri, 11 Jan 2019 19:23:07 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 3C4E8824C8 for ; Fri, 11 Jan 2019 19:23:07 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id F0A271499EF8; Fri, 11 Jan 2019 19:23:06 +0000 (UTC) Delivered-To: wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C743E1499EF7 for ; Fri, 11 Jan 2019 19:23:06 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wr1-x436.google.com (mail-wr1-x436.google.com [IPv6:2a00:1450:4864:20::436]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1CA67824C4 for ; Fri, 11 Jan 2019 19:23:06 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-wr1-x436.google.com with SMTP id u4so16392532wrp.3 for ; Fri, 11 Jan 2019 11:23:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=dY/4EfxRZFxnLm1w8irS3wpUmQPlkYjHoyAcbbmjKkA=; b=lIiqJ4o8SHCeEobhVislUhZaHFQsbX+2KS3ioDoiRjgxaoJUKJC3dHtmJaaMb82KOC +PJBxPtjoqII080lmP0jBiZQFgJhCeVqRmocZY9qDaGH719VyWhs/uoBGG7uiRST8C/u 65GSZveqq3t6VpsiB9YHeEHxpsE4v0ELutQlYKEo0gKIxjH6d41G3+SKPIjZWP0ieUSq ig0iMD1KfJDj55hShJyx9GLBdbHj8H0El/8VXr19IFV8SeQ+DZq8oxLcUpfGWx04b5lR iZ5LHADvmoZQzkj+uMIYMVevAt/1b9bNfth1govgeeJ9yWRlWNgj3Ni84oRBGKe3tGvu kf7A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=dY/4EfxRZFxnLm1w8irS3wpUmQPlkYjHoyAcbbmjKkA=; b=EwdzrB9Lj1MAU0ab9u1BAP85dzc873JlZLWDEmSwg1MAvWw1gPgS5oJKTMkzjsg1uT 2U0wPy4v16OgiPFrLsQfwbnxiA02OAuWA2SIGSZcEOzq6Wyk262gIDO1ng5dyq+pGDmE xMyQO5X+QL90mqXN3OsaD35EOVOSdjcnyu4yUt+UDLEkqTmstStm+/UdubqjtLNgP0rw A0i15QOSdtWoSh6/4+YK+njcQbX8LjYK1TTXBgx02VD53PJS51zUG48dF8aR0h0RRgvN OBmhhI8hYc/yV25SoCxBJ8rUJ5aRKgtvw9k02t0GHUr4CB3IMD/cc5k2c+OT9OfNRdIy OkVQ== X-Gm-Message-State: AJcUukfLLZvDA4zVJblY/cXxFx3i/TCKttQ2w6W1JFhMBDT5k9BTTGvd W8btlw/ubFA+fH0FdXKJqXa60NzgQXFlSTPQFuE= X-Google-Smtp-Source: ALg8bN4XLOomcIkc+TAdfC8hv2C45eEmSg4t/4LIBCto3Ors9UfuG2O1ST6Mp4pZ2llX6ow7R799ezzeKLbSF4Ldyvc= X-Received: by 2002:adf:8323:: with SMTP id 32mr14189906wrd.176.1547234584701; Fri, 11 Jan 2019 11:23:04 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Adrian Chadd Date: Fri, 11 Jan 2019 11:22:51 -0800 Message-ID: Subject: Re: wireless coordination and who's working on what? To: waddlesplash Cc: "freebsd-wireless@freebsd.org" X-Rspamd-Queue-Id: 1CA67824C4 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.95 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.96)[-0.955,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jan 2019 19:23:08 -0000 > > Hi, > I'm .. mostly trying to help people. Geramy has been helping out hugely on the ath10k port and I'm updating my laptops (again!) to the latest head so I can continue rolling with that. I'd like to get ath10k ready to put into the tree but there are a couple of net80211 and driver holes that need patching for these newer firmware NICs. (Around node creation/deletion, crypto key updates, sending frames, etc - net80211 assumes they're all non-blocking operations but that's definitely not true for the majority of hardware now shipping.) -a