Linux wireless drivers development
 help / color / mirror / Atom feed
From: shayne.chen@mediatek.com
To: "nbd@nbd.name" <nbd@nbd.name>, "jwboyer@kernel.org" <jwboyer@kernel.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"linux-firmware@kernel.org" <linux-firmware@kernel.org>,
	"lorenzo@kernel.org" <lorenzo@kernel.org>,
	"Ryder Lee" <Ryder.Lee@mediatek.com>,
	"Evelyn Tsai (蔡珊鈺)" <Evelyn.Tsai@mediatek.com>
Subject: Re: [PATCH 2/2] linux-firmware: update firmware for MT7916
Date: Wed, 8 Feb 2023 16:13:28 +0000	[thread overview]
Message-ID: <c82307e02e6d2c29d2e30209c76fe8bb7c86616f.camel@mediatek.com> (raw)
In-Reply-To: <d6244fd6-62bd-ba07-fe18-dee559594ece@nbd.name>

On Wed, 2023-02-01 at 17:07 +0100, Felix Fietkau wrote:
> On 23.11.22 12:07, Shayne Chen wrote:
> > This patch updates firmware files v211120221031 for MT7916 WiFi
> > NIC.
> > 
> > Signed-off-by: Shayne Chen<shayne.chen@mediatek.com>
> 
> More and more users are complaining that this firmware update
> introduces 
> a regression of not being able to support 5 GHz and 6 GHz together 
> anymore. Apparently the EEPROM data needs to be patched to limit
> support 
> to one of the two bands, otherwise both don't work.
> Switching at runtime apparently doesn't work without a firmware
> restart.
> 
> Is there any chance we could get a firmware that fixes this bug?
> 
Hi Felix,

We've released new firmware which enables 5+6 GHz on mt7916 band1 to
mt76 community, and are collecting feedbacks from users.
I'll send the updated firmware after getting positive feedbacks.

Thanks,
Shayne

> Thanks,
> 
> - Felix

  reply	other threads:[~2023-02-08 16:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221123110743.22005-1-shayne.chen@mediatek.com>
     [not found] ` <20221123110743.22005-2-shayne.chen@mediatek.com>
2023-02-01 16:07   ` [PATCH 2/2] linux-firmware: update firmware for MT7916 Felix Fietkau
2023-02-08 16:13     ` shayne.chen [this message]
2023-02-08 16:32       ` Felix Fietkau

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=c82307e02e6d2c29d2e30209c76fe8bb7c86616f.camel@mediatek.com \
    --to=shayne.chen@mediatek.com \
    --cc=Evelyn.Tsai@mediatek.com \
    --cc=Ryder.Lee@mediatek.com \
    --cc=jwboyer@kernel.org \
    --cc=linux-firmware@kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lorenzo@kernel.org \
    --cc=nbd@nbd.name \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox