From: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
To: Mike Lothian <mike@fireburn.co.uk>
Cc: nbd@nbd.name,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-wireless@vger.kernel.org, lorenzo@kernel.org,
sujuan.chen@mediatek.com
Subject: Re: [6.2][regression] after commit cd372b8c99c5a5cf6a464acebb7e4a79af7ec8ae stopping working wifi mt7921e
Date: Tue, 17 Jan 2023 18:13:14 +0500 [thread overview]
Message-ID: <CABXGCsNDYNGVKHh50SneQwdd5A4oWT2=Fb1r5YsO=N9W5aGA_A@mail.gmail.com> (raw)
In-Reply-To: <CAHbf0-FzLyQeWN0ii2-2TqMg+5ptVsaoAjqrNe4ceXG_MtNeqA@mail.gmail.com>
On Tue, Jan 17, 2023 at 6:06 PM Mike Lothian <mike@fireburn.co.uk> wrote:
>
> I can confirm this fixes things for me, thanks
Sorry for offtop.
Maybe somebody knows, is it possible to extend channel width to 160MHz
on this chip?
❯ sudo iw wlp5s0 info
Interface wlp5s0
ifindex 3
wdev 0x1
addr 48:e7:da:57:9a:33
type managed
wiphy 0
channel 44 (5220 MHz), width: 80 MHz, center1: 5210 MHz
txpower 3.00 dBm
multicast TXQ:
qsz-byt qsz-pkt flows drops marks overlmt hashcol tx-bytes tx-packets
0 0 0 0 0 0 0 0 0
❯ sudo iw wlp5s0 set channel 36 160MHz
Usage: iw [options] dev <devname> set channel <channel>
[NOHT|HT20|HT40+|HT40-|5MHz|10MHz|80MHz]
Options:
--debug enable netlink debugging
--
Best Regards,
Mike Gavrilov.
next prev parent reply other threads:[~2023-01-17 13:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 0:33 [6.2][regression] after commit cd372b8c99c5a5cf6a464acebb7e4a79af7ec8ae stopping working wifi mt7921e Mike Lothian
2023-01-17 5:42 ` Mikhail Gavrilov
2023-01-17 6:42 ` Kalle Valo
2023-01-17 13:06 ` Mike Lothian
2023-01-17 13:13 ` Mikhail Gavrilov [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-21 1:10 Mikhail Gavrilov
2022-12-21 10:45 ` Felix Fietkau
2022-12-21 11:26 ` Lorenzo Bianconi
2022-12-21 13:10 ` Mikhail Gavrilov
2022-12-21 14:12 ` Felix Fietkau
2022-12-21 16:07 ` Lorenzo Bianconi
2022-12-21 16:46 ` Mikhail Gavrilov
2022-12-21 17:17 ` Felix Fietkau
2022-12-22 6:47 ` Mikhail Gavrilov
2022-12-24 7:55 ` Thorsten Leemhuis
2022-12-26 10:59 ` Thorsten Leemhuis
2023-01-04 14:20 ` Thorsten Leemhuis
2023-01-09 7:32 ` Linux kernel regression tracking (Thorsten Leemhuis)
2023-01-10 7:16 ` Linux kernel regression tracking (Thorsten Leemhuis)
2023-01-10 8:00 ` Felix Fietkau
2023-01-10 8:41 ` Linux kernel regression tracking (Thorsten Leemhuis)
2023-01-13 14:11 ` Kalle Valo
2023-01-10 21:52 ` Mikhail Gavrilov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABXGCsNDYNGVKHh50SneQwdd5A4oWT2=Fb1r5YsO=N9W5aGA_A@mail.gmail.com' \
--to=mikhail.v.gavrilov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=mike@fireburn.co.uk \
--cc=nbd@nbd.name \
--cc=sujuan.chen@mediatek.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.