Am 20.09.2022 um 01:42 schrieb Sergey Ryazanov:
Hello,
I would like to add my 2c.
On Mon, Sep 19, 2022 at 8:25 PM Tim Harvey wrote:
I'm not clear if
there are many other cards that have this same issue.
The list of cards with unprogrammed regdomain can be extended with
several relatively
Hello,
I would like to add my 2c.
On Mon, Sep 19, 2022 at 8:25 PM Tim Harvey wrote:
> I'm not clear if
> there are many other cards that have this same issue.
The list of cards with unprogrammed regdomain can be extended with
several relatively modern models:
* MikroTik R11e-5HacD (QCA9882
On Tue, Aug 30, 2022 at 2:57 PM Brian Norris wrote:
>
> Hi Cale,
>
> I meant to respond a while back, but didn't get around to it, sorry.
> In case it's still helpful:
>
> On Wed, May 11, 2022 at 3:52 PM Cale Collins wrote:
> > On Mon, May 9, 2022 at 11:16 AM Cale Collins wrote:
> > > I'm
Hi Cale,
I meant to respond a while back, but didn't get around to it, sorry.
In case it's still helpful:
On Wed, May 11, 2022 at 3:52 PM Cale Collins wrote:
> On Mon, May 9, 2022 at 11:16 AM Cale Collins wrote:
> > I'm experiencing an issue very similar to this. The regulatory domain
> >
Adding Kalle, I got his address wrong the first time.
On Mon, May 9, 2022 at 11:16 AM Cale Collins wrote:
>
> Hello Brian and Kalle,
>
> I'm experiencing an issue very similar to this. The regulatory domain
> settings wouldn't allow me to create an AP on 5ghz bands on kernels
> newer than 5.10
Hello Brian and Kalle,
I'm experiencing an issue very similar to this. The regulatory domain
settings wouldn't allow me to create an AP on 5ghz bands on kernels
newer than 5.10 when using a WLE900VX (QCA9984) radio. I bisected the
kernel and ultimately landed on the regression that Brian
Hi Patrick,
On Sat, Apr 23, 2022 at 3:52 AM Patrick Steinhardt wrote:
> This revert is in fact causing problems on my machine. I have a QCA9984,
> which exports two network interfaces. While I was able to still use one
> of both NICs for 2.4GHz, I couldn't really use the other card to set up
> a
On Wed, May 27, 2020 at 09:57:18AM -0700, Brian Norris wrote:
> This reverts commit 2dc016599cfa9672a147528ca26d70c3654a5423.
>
> Users are reporting regressions in regulatory domain detection and
> channel availability.
>
> The problem this was trying to resolve was fixed in firmware anyway:
>
Brian Norris wrote:
> This reverts commit 2dc016599cfa9672a147528ca26d70c3654a5423.
>
> Users are reporting regressions in regulatory domain detection and
> channel availability.
>
> The problem this was trying to resolve was fixed in firmware anyway:
>
> QCA6174 hw3.0: sdio-4.4.1: add
Am 30.10.20 um 14:23 schrieb Alvin Sipraga:
Hi,
On 10/30/20 8:20 AM, Jouni Malinen wrote:
So the issue is in not being able to operate an AP on the 5 GHz band?
That sounds like the expected behavior for any device that has not
been calibrated and provisioned for a specific country where
On 10/30/20 8:20 AM, Jouni Malinen wrote:
> So the issue is in not being able to operate an AP on the 5 GHz band? > That
sounds like the expected behavior for any device that has not
> been calibrated and provisioned for a specific country where >
regulatory rules allow operation on the 5 GHz
://lists.infradead.org/pipermail/ath10k/2020-October/012049.html .
Kind regards,
Julian
From: ath10k on behalf of Félix Sipma
Sent: October 30, 2020 8:51 AM
To: Jouni Malinen
Cc: ath10k@lists.infradead.org
Subject: Re: [PATCH] Revert "ath: add support for special 0x0 regulatory
domain"
Hi,
On 10/30/20 8:20 AM, Jouni Malinen wrote:
> So the issue is in not being able to operate an AP on the 5 GHz band?
> That sounds like the expected behavior for any device that has not
> been calibrated and provisioned for a specific country where
> regulatory rules allow operation on the 5 GHz
On 2020-10-30 09:20+0200, Jouni Malinen wrote:
On Thu, Oct 29, 2020 at 4:06 PM Félix Sipma wrote:
I made a detailed report, with dmesg outputs of different
kernel/firmware-atheros and wireless-regdb combinations at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970679
So the issue is in
On Thu, Oct 29, 2020 at 4:06 PM Félix Sipma wrote:
> I made a detailed report, with dmesg outputs of different
> kernel/firmware-atheros and wireless-regdb combinations at
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970679
So the issue is in not being able to operate an AP on the 5 GHz
Hi,
Thanks for your detailed answer.
I made a detailed report, with dmesg outputs of different
kernel/firmware-atheros and wireless-regdb combinations at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970679
Massimo Maggi pointed me to this ath10k issue on the last message.
Regards,
On
Hello,
Sorry if I break the thread, I'm not subscribed and do not have access
to the message-id.
I noticed the last message about this issue was on August:
https://lists.infradead.org/pipermail/ath10k/2020-August/011785.html
I got caught by this bug, too. I use a Compex wle900vx (qca988x).
On 8/27/20 12:12 PM, Kalle Valo wrote:
Alvin Šipraga writes:
Hi Kalle,
On 7/30/20 2:49 PM, Alvin Šipraga wrote:
This reverts commit 2dc016599cfa9672a147528ca26d70c3654a5423.
Per Atheros documentation to manufacturers, the EEPROM regulatory domain
code 0x0 must always map to "US". In
Hi Kalle,
On 7/30/20 2:49 PM, Alvin Šipraga wrote:
This reverts commit 2dc016599cfa9672a147528ca26d70c3654a5423.
Per Atheros documentation to manufacturers, the EEPROM regulatory domain
code 0x0 must always map to "US". In particular, it should not map to a
custom world regulatory domain. For
This reverts commit 2dc016599cfa9672a147528ca26d70c3654a5423.
Per Atheros documentation to manufacturers, the EEPROM regulatory domain
code 0x0 must always map to "US". In particular, it should not map to a
custom world regulatory domain. For references, see [1] and [2] below.
Furthermore,
On Thu, May 28, 2020 at 8:42 AM Adrian Chadd wrote:
> On Thu, 28 May 2020 at 05:02, Julian Calaby wrote:
> > On Thu, May 28, 2020 at 5:18 AM Brian Norris
> > wrote:
> > >
> > > This reverts commit 2dc016599cfa9672a147528ca26d70c3654a5423.
> > >
> > > Users are reporting regressions in
Hi Brian,
On Thu, May 28, 2020 at 5:18 AM Brian Norris wrote:
>
> This reverts commit 2dc016599cfa9672a147528ca26d70c3654a5423.
>
> Users are reporting regressions in regulatory domain detection and
> channel availability.
>
> The problem this was trying to resolve was fixed in firmware anyway:
This reverts commit 2dc016599cfa9672a147528ca26d70c3654a5423.
Users are reporting regressions in regulatory domain detection and
channel availability.
The problem this was trying to resolve was fixed in firmware anyway:
QCA6174 hw3.0: sdio-4.4.1: add firmware.bin_WLAN.RMH.4.4.1-00042
23 matches
Mail list logo
