Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <c9dc82bc-71ea-3047-9021-688008376e83@shiphrah.com>
Date:   Mon, 14 Aug 2023 11:06:49 +0200
MIME-Version: 1.0
Subject: Re: Firmware for MT7922 missing in initrd; bluetooth disabled after
 update
Content-Language: de-DE
To:     Paul Menzel <pmenzel@molgen.mpg.de>, Qu Wenruo <wqu@suse.com>
Cc:     linux-bluetooth@vger.kernel.org, Takashi Iwai <tiwai@suse.com>,
        Chris Lu <chris.lu@mediatek.com>, Takashi Iwai <tiwai@suse.de>
References: <8ddaee26-b4d7-f694-ac8b-2aaf4d3c5f8e@shiphrah.com>
 <c69edd3b-bace-42a0-91e5-d8606a443853@molgen.mpg.de>
 <874jl4r30d.wl-tiwai@suse.de>
From:   =?UTF-8?Q?J=c3=bcrgen_Hofmann?= <hofmann@shiphrah.com>
Organization: shiphrah GmbH
In-Reply-To: <874jl4r30d.wl-tiwai@suse.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Precedence: bulk

Dear Paul, dear Qu,

>>  From Qu’s answer in the thread *[PATCH v3 1/2] Bluetooth: btusb: Add
>> new VID/PID 0489/e102 for MT7922* [1] it sounds to me, support for
>> chip was only added recently, and is going to be in Linux v6.6.
> 
> The problem is rather the lack of MODULE_FIRMWARE() declarations for
> the corresponding device.  The device itself already works fine as is
> with the current upstream kernel as long as the firmware file is
> present on the system.  But as dracut puts only the firmware file
> listed in MODULE_FIRMWARE() into initrd, it starts failing once when
> you build an initrd containing the BT.

from all I can tell (and understand), the analysis from Takashi about 
the missing MODULE_FIRMWARE() declarations is correct.

Thanks,

Jürgen