From owner-freebsd-wireless@freebsd.org Sun Aug 9 15:38:07 2020 Return-Path: Delivered-To: freebsd-wireless@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 789A23B7C0F for ; Sun, 9 Aug 2020 15:38:07 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mx1.sbone.de (mx1.sbone.de [IPv6:2a01:4f8:13b:39f::9f:25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.sbone.de", Issuer "SBone.DE" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4BPjsp2c5Vz48lm for ; Sun, 9 Aug 2020 15:38:05 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id 0E7E48D4A38B for ; Sun, 9 Aug 2020 15:38:01 +0000 (UTC) Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id 8B2ABE70828 for ; Sun, 9 Aug 2020 15:38:01 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id m6xR8HmPoqOg for ; Sun, 9 Aug 2020 15:37:59 +0000 (UTC) Received: from [169.254.45.172] (unknown [IPv6:fde9:577b:c1a9:4902:5d5c:7ce:5339:2ffa]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id EEABEE707AC for ; Sun, 9 Aug 2020 15:37:58 +0000 (UTC) From: "Bjoern A. Zeeb" To: freebsd-wireless Subject: Re: regdomain.xml [was also: - Linux wireless-regdb] Date: Sun, 09 Aug 2020 15:37:58 +0000 X-Mailer: MailMate (2.0BETAr6146) Message-ID: <083B7D36-2175-46DC-9C9A-FEA8673482E8@lists.zabbadoz.net> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4BPjsp2c5Vz48lm X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of bzeeb-lists@lists.zabbadoz.net designates 2a01:4f8:13b:39f::9f:25 as permitted sender) smtp.mailfrom=bzeeb-lists@lists.zabbadoz.net X-Spamd-Result: default: False [-2.76 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_FIVE(0.00)[5]; NEURAL_HAM_MEDIUM(-0.99)[-0.987]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a01:4f8:13b:39f::9f:25]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-wireless@freebsd.org]; DMARC_NA(0.00)[zabbadoz.net]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-0.94)[-0.941]; TO_DN_ALL(0.00)[]; NEURAL_HAM_SHORT(-0.53)[-0.530]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:24940, ipnet:2a01:4f8::/29, country:DE]; RCVD_TLS_LAST(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.33 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: Sun, 09 Aug 2020 15:38:07 -0000 Hi, I’ll just join in on the last email in the thread not replying to anything specific. Having gone through some of the stuff lately myself in order to put [1] out (which is also includes a few things to discuss) I’ll try to summarise a few things I’ve learnt and thought of, which confused me over the time: - SKU - what does it actually stand for? Does it really belong into our regdomain? - why are the freqbands prefixes with “H”, “F”, .. and what do these magic letters stand for? - We have netbands, freqbands, and bands. None of these are actually describing the actual frequency ranges (as the linux-db does). - The freqbands seems to start and end on the center frequency of the first/last chansep spaced channel. In the old days that was less confusing I guess as to now with 4x20 for VHT80. - I am still unclear as to where we should map channels to frequency because we are half-hearted doing that partially for upper and lower bounds of freqbands currently. As such I have different freqbands for VHT20 vs. VHT40/80/160 as there are cases where there is an extra 20 channel not part of 80s. - I’d love to have the freqbands actually describe the frequency limits and have the mappings of channels within them elsewhere; I have no idea how/where Linux is doing that. - I’d love to have general freqbands and groups of them independent of the netbands. - I do not actually understand what netbands are for given we have the IEEE80211_CHAN_ set appropriately. It’s for simplicity later but there is a lot of duplication. That said, some of these IEEE80211_CHAN_* flags do not actually belong to the regulatory limits either but are an 802.11 channel description. - This all leads to confusion currently as to how we setup bands/channels/.. I made a mistake by accident and the list of combinations we checked in ifconfig exploded to 350.000 for whether a channel was valid. Clearly told me that the organisation does not seem to be right. - I was wondering if for clarity we can break up regdomain.xml into multiple files? - One thing I don’t like on the Linux version is that for, say ETSI, the information is basically copied per EU member state. I love our reference model there. I don’t mind having etsi, etsi1, etsi2 if I can then say 20 countries it’s etsi2 and be done. I think that is something essential and good we have. - I do like our more structured format a lot more than the Linux one. - We are lacking a few things, DFS and INDOORS and maxpower are not the only things which matter these days. You may notice “wmmrule=ETSI” in the Linux reg-db, for example. - I wonder if what we actually want is a multi-layer thingy inheriting one from another or if we want a pure-regdomain (not knowing about channels) and more logic elsewhere which deals with putting WiFi things into that)? - I think it’ll need a bit more than simply restructuring regdomain.xml; I think doing it will probably also need a bit more (a) documentation on what each bit means and tries to accomplish) and (b) a more clear separation between frequencies and restrictions and 802.11 channels and with that a bit more downward code changes. - I would really love to see some of these things sorted and I’d love if the thread would stay alive. Just my 5cts, Bjoern [1] https://reviews.freebsd.org/D25999 From owner-freebsd-wireless@freebsd.org Sun Aug 9 16:47:39 2020 Return-Path: Delivered-To: freebsd-wireless@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 979583B904B for ; Sun, 9 Aug 2020 16:47:39 +0000 (UTC) (envelope-from notjanedeere@gmail.com) Received: from mail-qt1-x830.google.com (mail-qt1-x830.google.com [IPv6:2607:f8b0:4864:20::830]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4BPlQ260YZz4CQm for ; Sun, 9 Aug 2020 16:47:38 +0000 (UTC) (envelope-from notjanedeere@gmail.com) Received: by mail-qt1-x830.google.com with SMTP id w9so5075881qts.6 for ; Sun, 09 Aug 2020 09:47:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=56dfcxnZk56Ey3DrTBlolvJuN54UqdqStlUTiBYEdzI=; b=LZrMcciPPlKDa2HOeAFqNm9EcysAEzPWcQKcyEmSbq3KKXZe9VcwMjwdO5kCNegB7W CidA2Aue1wrDPnupxJpkrMjNZjbYhdRMFx30uvVNWcmVzBTrDMHiN70YaFPugm947pEb LKyeICeNhcLCZtbr6pOepsD9MRncL54ZDCw2clUntGSF6rhx0TXnks5XRTQUWnNQBleb DOaMJQGKA8EXW5Z5LhwRZpENXdwGDIb3i+MZJK7DwhK3zKxWw/EFvRONkeVQV52VMTae x+cOq40CKf0ntA4IMDVTIwpIrLF2VKSqWtOU7JhQCntuueaUxRpr8Bn3E+bVCbQDVCpj 3HLw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=56dfcxnZk56Ey3DrTBlolvJuN54UqdqStlUTiBYEdzI=; b=cOCIYF/IdQY6q//pkFLER35vnhPANQUiug2JeyC/tWYP+JCmKkBsBntNNpwEpN3Ym1 k3bWT0RM5a66rop4lBNDze/S8x07/Lsi/VfdfaBYRCcIZ9Rv/DLBOWC+w1hjLuqvs0mk A6OK0Agp2tEWqUA7BwYC919mEwHgr+E7zVXdAtr56QyRUvfj3ZKEaGTM597I1DJvR/Pw M7VvKXyaihmIOM/6RKvnYS69Parrce80f4PaNpEyZLeyKuZGThmMajYqqWmUXu8ooxh0 nLY7M2iqyOkitUBviAxy4DS0co1p3vthkCYZRfG+u6N8WLQeoqEBGU8U5b0bDVfYWJQI DwGA== X-Gm-Message-State: AOAM533OsX+aKWSwr3bsFV3/7coH+DoAHGSqVmH0Cdu6y8LMmqATbKoZ qsxIAS3rmG+N3TSA3KObnVErB/Z1 X-Google-Smtp-Source: ABdhPJxgD1+a8BveVm/jwGRBERsIJsXiNRtdk6v4Wasu/B8/5PqKeW0IsySA/i6/i7RlJjRBCqmnYQ== X-Received: by 2002:ac8:73d9:: with SMTP id v25mr23795575qtp.82.1596991657622; Sun, 09 Aug 2020 09:47:37 -0700 (PDT) Received: from [10.8.0.7] ([66.115.145.34]) by smtp.gmail.com with ESMTPSA id x12sm15185963qta.67.2020.08.09.09.47.36 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 09 Aug 2020 09:47:37 -0700 (PDT) Subject: Re: regdomain.xml [was also: - Linux wireless-regdb] To: freebsd-wireless@freebsd.org References: <083B7D36-2175-46DC-9C9A-FEA8673482E8@lists.zabbadoz.net> From: Aaron Message-ID: Date: Sun, 9 Aug 2020 12:47:35 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.11.0 MIME-Version: 1.0 In-Reply-To: <083B7D36-2175-46DC-9C9A-FEA8673482E8@lists.zabbadoz.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Rspamd-Queue-Id: 4BPlQ260YZz4CQm X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=LZrMcciP; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of notjanedeere@gmail.com designates 2607:f8b0:4864:20::830 as permitted sender) smtp.mailfrom=notjanedeere@gmail.com X-Spamd-Result: default: False [-2.93 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; NEURAL_HAM_MEDIUM(-1.10)[-1.100]; FROM_HAS_DN(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-wireless@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-0.995]; RCVD_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::830:from]; NEURAL_SPAM_SHORT(0.17)[0.168]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_TLS_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.33 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: Sun, 09 Aug 2020 16:47:39 -0000 The documentation portion seems like the first step, is there a wiki for proposed changes where we could start? To get started, is there any existing documentation we can refer to?  I think the answer is no, and it's down to someone who understand it going through the code to find answers ... On 8/9/2020 11:37 AM, Bjoern A. Zeeb wrote: > Hi, > > I’ll just join in on the last email in the thread not replying to > anything specific. > > Having gone through some of the stuff lately myself in order to put > [1] out (which is also includes a few things to discuss) I’ll try to > summarise a few things I’ve learnt and thought of, which confused me > over the time: > > - SKU - what does it actually stand for?   Does it really belong into > our regdomain? > > - why are the freqbands prefixes with “H”, “F”, .. and what do these > magic letters stand for? > > - We have netbands, freqbands, and bands.  None of these are actually > describing the actual frequency ranges (as the linux-db does). > > - The freqbands seems to start and end on the center frequency of the > first/last chansep spaced channel.  In the old days that was less > confusing I guess as to now with 4x20 for VHT80. > > - I am still unclear as to where we should map channels to frequency > because we are half-hearted doing that partially for upper and lower > bounds of freqbands currently.  As such I have different freqbands for > VHT20 vs. VHT40/80/160 as there are cases where there is an extra 20 > channel not part of 80s. > > - I’d love to have the freqbands actually describe the frequency > limits and have the mappings of channels within them elsewhere;  I > have no idea how/where Linux is doing that. > > - I’d love to have general freqbands and groups of them independent of > the netbands. > > - I do not actually understand what netbands are for given we have the > IEEE80211_CHAN_ set appropriately.   It’s for simplicity later but > there is a lot of duplication.  That said, some of these > IEEE80211_CHAN_* flags do not actually belong to the regulatory limits > either but are an 802.11 channel description. > > - This all leads to confusion currently as to how we setup > bands/channels/..  I made a mistake by accident and the list of > combinations we checked in ifconfig exploded to 350.000 for whether a > channel was valid.  Clearly told me that the organisation does not > seem to be right. > > - I was wondering if for clarity we can break up regdomain.xml into > multiple files? > > - One thing I don’t like on the Linux version is that for, say ETSI, > the information is basically copied per EU member state.  I love our > reference model there.  I don’t mind having etsi, etsi1, etsi2 if I > can then say 20 countries it’s etsi2 and be done.   I think that is > something essential and good we have. > > > - I do like our more structured format a lot more than the Linux one. > > - We are lacking a few things, DFS and INDOORS and maxpower are not > the only things which matter these days.  You may notice > “wmmrule=ETSI” in the Linux reg-db, for example. > > - I wonder if what we actually want is a multi-layer thingy inheriting > one from another or if we want a pure-regdomain (not knowing about > channels) and more logic elsewhere which deals with putting WiFi > things into that)? > > > - I think it’ll need a bit more than simply restructuring > regdomain.xml;  I think doing it will probably also need a bit more > (a) documentation on what each bit means and tries to accomplish) and > (b) a more clear separation between frequencies and restrictions and > 802.11 channels and with that a bit more downward code changes. > > - I would really love to see some of these things sorted and I’d love > if the thread would stay alive. > > Just my 5cts, > Bjoern > > > [1] https://reviews.freebsd.org/D25999 > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to > "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@freebsd.org Sun Aug 9 16:55:36 2020 Return-Path: Delivered-To: freebsd-wireless@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4088D3B9F91 for ; Sun, 9 Aug 2020 16:55:36 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qk1-f174.google.com (mail-qk1-f174.google.com [209.85.222.174]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4BPlbC2JYGz4DJ7 for ; Sun, 9 Aug 2020 16:55:35 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-qk1-f174.google.com with SMTP id b79so6316084qkg.9 for ; Sun, 09 Aug 2020 09:55:35 -0700 (PDT) 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=eDRjIfgyQ3IhWnI+cLkL8zxju9u4txtG3FWgAk3B/5A=; b=DrQHhbW4GTFdEO59V6+a8745L7ppWpmyLBoKpNIu4X+fcSKBlV+pa+PbLwVIof1jzD Pf7ccFxPcei9unoAkiy4TYUt++8aw7LKz/IiJ9Wg3I57NmQoC08HZMkcdp3J+Tu1sFjn iOBgs89UYfmlxtipu26l17BaF0utWLVdB00EjOLtLY2mNANrUMfyBiDKD1HlLhJbpZUG 17eRhz18k8tyZC/6iDnEnq2pschgY6EX+doD4IpGVbwe4r8MFQZFpwsAbPLi7sJ4HasD tMPIt37nyvw25TvYOqaiiX61M9ujOfAEi6N0+Z/AMKNgUeEABD47Fa01/ZYKVAnLCc63 gXlQ== X-Gm-Message-State: AOAM530xiO7NXP3u885qdNEd6uScqxRslHWfdf5GeIG+cUQLBIECVam1 L8KvOoXVQ3FqPfE/Az7y5fRM+tYXxg/bf5n0aMnpbw== X-Google-Smtp-Source: ABdhPJzvghkvXKgn8JwKPEFyWOxKeeapCb0emTDPv4cyPtMYemlGtIPqkftxcDOH181CZKI04e9Wc6vw8kbp5e1ltUE= X-Received: by 2002:a05:620a:1a:: with SMTP id j26mr23294330qki.183.1596992134358; Sun, 09 Aug 2020 09:55:34 -0700 (PDT) MIME-Version: 1.0 References: <083B7D36-2175-46DC-9C9A-FEA8673482E8@lists.zabbadoz.net> In-Reply-To: <083B7D36-2175-46DC-9C9A-FEA8673482E8@lists.zabbadoz.net> From: Adrian Chadd Date: Sun, 9 Aug 2020 09:55:22 -0700 Message-ID: Subject: Re: regdomain.xml [was also: - Linux wireless-regdb] To: "Bjoern A. Zeeb" Cc: freebsd-wireless X-Rspamd-Queue-Id: 4BPlbC2JYGz4DJ7 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of adrianchadd@gmail.com designates 209.85.222.174 as permitted sender) smtp.mailfrom=adrianchadd@gmail.com X-Spamd-Result: default: False [-2.15 / 15.00]; ARC_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17:c]; NEURAL_HAM_LONG(-0.99)[-0.993]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-wireless@freebsd.org]; DMARC_NA(0.00)[freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; NEURAL_HAM_SHORT(-0.21)[-0.208]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[209.85.222.174:from]; NEURAL_HAM_MEDIUM(-0.95)[-0.946]; FORGED_SENDER(0.30)[adrian@freebsd.org,adrianchadd@gmail.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.222.174:from]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; TAGGED_FROM(0.00)[]; FROM_NEQ_ENVFROM(0.00)[adrian@freebsd.org,adrianchadd@gmail.com]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.33 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.33 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: Sun, 09 Aug 2020 16:55:36 -0000 On Sun, 9 Aug 2020 at 08:38, Bjoern A. Zeeb wrote: > Hi, > > I=E2=80=99ll just join in on the last email in the thread not replying to > anything specific. > > Having gone through some of the stuff lately myself in order to put [1] > out (which is also includes a few things to discuss) I=E2=80=99ll try to > summarise a few things I=E2=80=99ve learnt and thought of, which confused= me > over the time: > The best way to start is by realising Sam started this by taking the ath regulatory code and breaking bits of it out into net80211. Look at sys/dev/ath/ath_hal/ath_regdomain/ or wherever I moved it. > > - SKU - what does it actually stand for? Does it really belong into > our regdomain? > It's the stock keeping unit code - it's based on the notion that NICs are sold into different markets for different purposes (country, sta/ap, laptop, etc) and so it's oriented around stockig. > > - why are the freqbands prefixes with =E2=80=9CH=E2=80=9D, =E2=80=9CF=E2= =80=9D, .. and what do > these magic letters stand for? > The amusingly line up well with what's in the ath_hal regdomain code. :-) > > - We have netbands, freqbands, and bands. None of these are actually > describing the actual frequency ranges (as the linux-db does). > Yup. Look at the ath_hal regdomain code. :-) > > - The freqbands seems to start and end on the center frequency of the > first/last chansep spaced channel. In the old days that was less > confusing I guess as to now with 4x20 for VHT80. > Yup - again, look at the ath_hal regdomain code :-) > > - I am still unclear as to where we should map channels to frequency > because we are half-hearted doing that partially for upper and lower > bounds of freqbands currently. As such I have different freqbands for > VHT20 vs. VHT40/80/160 as there are cases where there is an extra 20 > channel not part of 80s. > That's partly why I didn't wanna start VHT80+80 and VHT160 - this needs to be made less insane. > > - I=E2=80=99d love to have the freqbands actually describe the frequency > limits and have the mappings of channels within them elsewhere; I have > no idea how/where Linux is doing that. > The regdb code in linux is doing that in nl80211 somewhere. - I=E2=80=99d love to have general freqbands and groups of them independent= of > the netbands. > Same. > > - I do not actually understand what netbands are for given we have the > IEEE80211_CHAN_ set appropriately. It=E2=80=99s for simplicity later bu= t > there is a lot of duplication. That said, some of these > IEEE80211_CHAN_* flags do not actually belong to the regulatory limits > either but are an 802.11 channel description. > Again, see ath_regdomain :-) > > - This all leads to confusion currently as to how we setup > bands/channels/.. I made a mistake by accident and the list of > combinations we checked in ifconfig exploded to 350.000 for whether a > channel was valid. Clearly told me that the organisation does not seem > to be right. > Yup. ath_regdomain. :-) I argued for redoing how the atheros driver did channel representation at QCA when we were doing the 11ac work and .. well, the way I did it in net80211 to at least get something going? THat's very similar to how it's done in the QCA reference driver for earlier chips. > - I was wondering if for clarity we can break up regdomain.xml into > multiple files? > > - One thing I don=E2=80=99t like on the Linux version is that for, say ET= SI, > the information is basically copied per EU member state. I love our > reference model there. I don=E2=80=99t mind having etsi, etsi1, etsi2 if= I > can then say 20 countries it=E2=80=99s etsi2 and be done. I think that = is > something essential and good we have. > I like it, as long as the abstraction is that and we can add some per country overrides. I think there are some country differences in things. > > - I do like our more structured format a lot more than the Linux one. > > - We are lacking a few things, DFS and INDOORS and maxpower are not the > only things which matter these days. You may notice =E2=80=9Cwmmrule=3DE= TSI=E2=80=9D > in the Linux reg-db, for example. > Yeah, that, and the upcoming SAR (specific absorption rate) rules. > > - I wonder if what we actually want is a multi-layer thingy inheriting > one from another or if we want a pure-regdomain (not knowing about > channels) and more logic elsewhere which deals with putting WiFi things > into that)? > I think we should aim for a pure regdomain thing; I wouldn't mind it including things as well, and also assembling the channel list to push up to the hardware. > > > - I think it=E2=80=99ll need a bit more than simply restructuring > regdomain.xml; I think doing it will probably also need a bit more (a) > documentation on what each bit means and tries to accomplish) and (b) a > more clear separation between frequencies and restrictions and 802.11 > channels and with that a bit more downward code changes. > > - I would really love to see some of these things sorted and I=E2=80=99d = love > if the thread would stay alive. > > Just my 5cts, > Bjoern > > > [1] https://reviews.freebsd.org/D25999 > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.or= g > " > From owner-freebsd-wireless@freebsd.org Sun Aug 9 21:01:00 2020 Return-Path: Delivered-To: freebsd-wireless@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 464093BD8EA for ; Sun, 9 Aug 2020 21:01:00 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4BPs2M308rz4P6M for ; Sun, 9 Aug 2020 21:00:59 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: by mailman.nyi.freebsd.org (Postfix) id 275CB3BDA8F; Sun, 9 Aug 2020 21:00:59 +0000 (UTC) Delivered-To: wireless@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2654D3BDA8E for ; Sun, 9 Aug 2020 21:00:59 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4BPs2L5d8dz4PKR for ; Sun, 9 Aug 2020 21:00:58 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 41F261F1F9 for ; Sun, 9 Aug 2020 21:00:58 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 079L0wMo064995 for ; Sun, 9 Aug 2020 21:00:58 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 079L0wV5064987 for wireless@FreeBSD.org; Sun, 9 Aug 2020 21:00:58 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <202008092100.079L0wV5064987@kenobi.freebsd.org> X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@FreeBSD.org using -f From: bugzilla-noreply@FreeBSD.org To: wireless@FreeBSD.org Subject: Problem reports for wireless@FreeBSD.org that need special attention Date: Sun, 9 Aug 2020 21:00:58 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.33 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.33 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: Sun, 09 Aug 2020 21:01:00 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- New | 237921 | wpi: Memory leak in function wpi_free_tx_ring of Open | 154598 | [ath] Atheros 5424/2424 can't connect to WPA netw Open | 236918 | Crash: in iwn_ampdu_tx_stop (or ieee80211_ht_node Open | 238636 | ath: Fix kernel addresses printed in if_ath_sysct Open | 240776 | iwm: Can't find wifi networks after short time si 5 problems total for which you should take action. From owner-freebsd-wireless@freebsd.org Tue Aug 11 06:50:40 2020 Return-Path: Delivered-To: freebsd-wireless@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 1D44937C751 for ; Tue, 11 Aug 2020 06:50:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4BQk4J01C0z46cG for ; Tue, 11 Aug 2020 06:50:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id F2B1537C750; Tue, 11 Aug 2020 06:50:39 +0000 (UTC) Delivered-To: wireless@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id F274737C8D2 for ; Tue, 11 Aug 2020 06:50:39 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4BQk4H6DcVz46X0 for ; Tue, 11 Aug 2020 06:50:39 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id B96D61722D for ; Tue, 11 Aug 2020 06:50:39 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 07B6odCX063279 for ; Tue, 11 Aug 2020 06:50:39 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 07B6odqq063278 for wireless@FreeBSD.org; Tue, 11 Aug 2020 06:50:39 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: wireless@FreeBSD.org Subject: [Bug 248584] usr.sbin/bluetooth/btpand: rc script to start btpand Date: Tue, 11 Aug 2020 06:50:39 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: conf X-Bugzilla-Version: Unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.33 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: Tue, 11 Aug 2020 06:50:40 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D248584 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bugs@FreeBSD.org |wireless@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Tue Aug 11 07:15:10 2020 Return-Path: Delivered-To: freebsd-wireless@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5332837D334 for ; Tue, 11 Aug 2020 07:15:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4BQkcZ1YCFz485m for ; Tue, 11 Aug 2020 07:15:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 34FF737D2FF; Tue, 11 Aug 2020 07:15:10 +0000 (UTC) Delivered-To: wireless@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 34C1237D2FE for ; Tue, 11 Aug 2020 07:15:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4BQkcZ0gbvz47s3 for ; Tue, 11 Aug 2020 07:15:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id EFCAE1716C for ; Tue, 11 Aug 2020 07:15:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 07B7F9KS091346 for ; Tue, 11 Aug 2020 07:15:09 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 07B7F9LM091345 for wireless@FreeBSD.org; Tue, 11 Aug 2020 07:15:09 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: wireless@FreeBSD.org Subject: [Bug 248584] usr.sbin/bluetooth/btpand: rc script to start btpand Date: Tue, 11 Aug 2020 07:15:09 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: conf X-Bugzilla-Version: Unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: tatsuki_makino@hotmail.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.isobsolete attachments.created Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.33 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: Tue, 11 Aug 2020 07:15:10 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D248584 Tatsuki Makino changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #217143|0 |1 is obsolete| | --- Comment #3 from Tatsuki Makino --- Created attachment 217146 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D217146&action= =3Dedit patch to head/libexec/rc/rc.d/btpand Removed useless bt_devaddr(3) emulation :) --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Tue Aug 11 17:55:04 2020 Return-Path: Delivered-To: freebsd-wireless@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id B75EB3B3DBB for ; Tue, 11 Aug 2020 17:55:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4BR0pw4Xpmz3bJ6 for ; Tue, 11 Aug 2020 17:55:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 9B1D23B396D; Tue, 11 Aug 2020 17:55:04 +0000 (UTC) Delivered-To: wireless@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 9AE0E3B3F92 for ; Tue, 11 Aug 2020 17:55:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4BR0pw3hZhz3b50 for ; Tue, 11 Aug 2020 17:55:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 639E11EB6C for ; Tue, 11 Aug 2020 17:55:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 07BHt4MG006950 for ; Tue, 11 Aug 2020 17:55:04 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 07BHt4No006949 for wireless@FreeBSD.org; Tue, 11 Aug 2020 17:55:04 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: wireless@FreeBSD.org Subject: [Bug 239795] rtwn(4): Add PCI Device ID's for Realtek RTL8192CE. Date: Tue, 11 Aug 2020 17:55:04 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: commit-hook@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: avos@freebsd.org X-Bugzilla-Flags: mfc-stable12? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.33 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: Tue, 11 Aug 2020 17:55:04 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D239795 --- Comment #4 from commit-hook@FreeBSD.org --- A commit references this bug: Author: markj Date: Tue Aug 11 17:54:10 UTC 2020 New revision: 364128 URL: https://svnweb.freebsd.org/changeset/base/364128 Log: MFC r350885 (by avos): rtwn_pci: add device ID for RTL8192CE. PR: 239795 Changes: _U stable/12/ stable/12/sys/dev/rtwn/pci/rtwn_pci_attach.h --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-wireless@freebsd.org Tue Aug 11 17:55:33 2020 Return-Path: Delivered-To: freebsd-wireless@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 3F9453B3C6A for ; Tue, 11 Aug 2020 17:55:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4BR0qT0sp0z3bGN for ; Tue, 11 Aug 2020 17:55:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 1D9B33B3F4B; Tue, 11 Aug 2020 17:55:33 +0000 (UTC) Delivered-To: wireless@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 1D56E3B3FBF for ; Tue, 11 Aug 2020 17:55:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4BR0qT014Sz3bCf for ; Tue, 11 Aug 2020 17:55:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id D7BB41ECEC for ; Tue, 11 Aug 2020 17:55:32 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 07BHtWWr007315 for ; Tue, 11 Aug 2020 17:55:32 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 07BHtWJu007314 for wireless@FreeBSD.org; Tue, 11 Aug 2020 17:55:32 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: wireless@FreeBSD.org Subject: [Bug 239795] rtwn(4): Add PCI Device ID's for Realtek RTL8192CE. Date: Tue, 11 Aug 2020 17:55:32 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: markj@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: avos@freebsd.org X-Bugzilla-Flags: mfc-stable12+ X-Bugzilla-Changed-Fields: cc flagtypes.name bug_status resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.33 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: Tue, 11 Aug 2020 17:55:33 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D239795 Mark Johnston changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |markj@FreeBSD.org Flags|mfc-stable12? |mfc-stable12+ Status|In Progress |Closed Resolution|--- |FIXED --=20 You are receiving this mail because: You are on the CC list for the bug.=