linux-kernel - Re: [PATCH 0/2] mmc: sdhci: add quirk to disable bounce buffer

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: <6294fb07-31b4-4c0e-9023-7c5ab604bbf1@intel.com>
Date: Mon, 6 Oct 2025 13:46:53 +0300
From: Adrian Hunter <adrian.hunter@...el.com>
To: Michael Garofalo <officialtechflashyt@...il.com>
CC: <linux-kernel@...r.kernel.org>, <linux-mmc@...r.kernel.org>,
	<ulf.hansson@...aro.org>
Subject: Re: [PATCH 0/2] mmc: sdhci: add quirk to disable bounce buffer

On 06/10/2025 12:28, Michael Garofalo wrote:
>> On 06/10/2025 10:35, Adrian Hunter wrote:
>>> On 06/10/2025 04:36, Michael Garofalo wrote:
>>>> This patch series adds a new bit to quirks2 for disabling the bounce
>>>> buffer.  On some hardware, this is required for proper operation.  An
>>>> example of such hardware is the SDHCI controller of the Nintendo Wii's
>>>> "Hollywood" chipset.  Without this patch, the onboard Broadcom 4318
>>>> Wi-Fi fails to connect to any networks.
>>>
>>> The bounce buffer should not make any difference, so it is likely
>>> a different problem that gets hidden when the bounce buffer is not
>>> used.
>>>
>>>> Could you enable dynamic debug messages and show the messages
>>>> for the failing case?
>>>
>>> Actually will also need to see the messages in the "fixed" case
>>> to compare.
> I'm afraid I won't be able to provide those easily, at least not with the
> commands you've provided.  Since the rootfs is _also_ running from SD,
> turning on full MMC logs like this produces an obscene amount of noise
> from the storage, unrelated to the SDIO wireless.  It gets even worse with
> my original intention, which was to save the logs to SD Card, (since my USB
> Gecko serial console is rather flakey, and introduces corruption now and then),
> since it's now logging the writes of it's own logs in a permanent loop.
> If there's a way to narrow down the logs to specifically whatever portions
> you're interested in, and filter out the noise, I would happily provide it.

Are there any error messages?