linux-kernel - Aw: Re: mt7988 usb broken on 6.10

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <trinity-3bc6fc80-e245-4691-9a57-f021b080d070-1722082134917@3c-app-gmx-bs28>
Date: Sat, 27 Jul 2024 14:08:54 +0200
From: Frank Wunderlich <frank-w@...lic-files.de>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Mathias Nyman <mathias.nyman@...el.com>, Chunfeng Yun
 <chunfeng.yun@...iatek.com>, Matthias Brugger <matthias.bgg@...il.com>,
 AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>,
 Daniel Golle <daniel@...rotopia.org>, John Crispin <john@...ozen.org>,
 linux-usb@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
 linux-mediatek@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Aw: Re: mt7988 usb broken on 6.10

Hi

> Gesendet: Samstag, 27. Juli 2024 um 06:57 Uhr
> Von: "Greg Kroah-Hartman" <gregkh@...uxfoundation.org>
> An: "Frank Wunderlich" <frank-w@...lic-files.de>
> Cc: "Mathias Nyman" <mathias.nyman@...el.com>, "Chunfeng Yun" <chunfeng.yun@...iatek.com>, "Matthias Brugger" <matthias.bgg@...il.com>, "AngeloGioacchino Del Regno" <angelogioacchino.delregno@...labora.com>, "Daniel Golle" <daniel@...rotopia.org>, "John Crispin" <john@...ozen.org>, linux-usb@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, linux-mediatek@...ts.infradead.org, linux-kernel@...r.kernel.org
> Betreff: Re: mt7988 usb broken on 6.10
>
> On Fri, Jul 26, 2024 at 07:13:19PM +0200, Frank Wunderlich wrote:
> > Hi,
> >
> > i've noticed that usb on mt7988 is broken in 6.10, was working on 6.9 (with some additional patches like
> > for pinctrl and dts as this chipset is not completely supported by mainline yet).
>
> Any chance you can use 'git bisect' to track down the offending commit?

because in mainline there is much missing for this SoC/board bisect is a bit tricky, so i tried to find someone which can say this error can be caused by a limited set of changes so i could simply revert some suspicious commits.

But i found out that we had some major differences in the usb devicetree nodes i have not expected (and to be honest not checked prior to posting). After using same dts like in 6.9 all is good, sorry for the noise.

> thanks,
>
> greg k-h


regards Frank