[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231126142634.3a100e2c@kernel.org>
Date: Sun, 26 Nov 2023 14:26:34 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: cristian_ci <cristian_ci@...tonmail.com>
Cc: "kvalo@...nel.org" <kvalo@...nel.org>,
"matthias.bgg@...il.com" <matthias.bgg@...il.com>,
"angelogioacchino.delregno@...labora.com"
<angelogioacchino.delregno@...labora.com>,
"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-mediatek@...ts.infradead.org"
<linux-mediatek@...ts.infradead.org>,
Lorenzo Bianconi <lorenzo@...nel.org>,
Felix Fietkau <nbd@....name>
Subject: Re: [BUG] wireless: mt7601u: probe failed with error -110
On Sat, 25 Nov 2023 13:03:45 +0000 cristian_ci wrote:
> I'm not the only one to have experienced this bug. I've been
> suggested to report that to kernel mailing list by linux support
> channels.
>
> I've tested this bug against upstream 6.6.2 kernel tarball from the
> latest stable branch [1].
>
> To solve this issue. I've also tried to patch mt7601u driver
> disabling mcu calibration. Which doesn't seem a wise idea because
> apparently it fixes probing but also hangs completely the machine
> after some seconds (so, it needs a hard/forced shutdown).
Does it work with the vendor driver? The upstream driver is just
a rewrite of the vendor driver, I don't know much about the device
internals.
Maybe Lorenzo or Felix have some ideas.
Powered by blists - more mailing lists