Received-SPF: pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
To:     linux-wireless <linux-wireless@vger.kernel.org>,
        Takashi Iwai <tiwai@suse.de>
From:   Larry Finger <Larry.Finger@lwfinger.net>
Subject: Firmware Organization
Message-ID: <53ebd786-7966-1998-951e-b0a0ee7ff39e@lwfinger.net>
Date:   Mon, 19 Aug 2019 11:25:55 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.8.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: linux-wireless-owner@vger.kernel.org
Precedence: bulk

Hi,

Prior to now, openSUSE has been packaging kernel firmware as a single entity; 
however, that package has reached a size that has a negative impact on small 
systems. Takashi Iwai has undertaken to split the firmware into a number of 
sub-packages. In a discussion on the developer's mailing list, we identified a 
major issue related to wireless, namely how to ensure that a given user will 
have network access in case their primary PCI device is not workable. To satisfy 
this situation, the following actions have been instituted. Takashi's comments 
are as follows:
------------------------------------------------------------------------------

In short:

- atheros subpackage is split to ath10k and atheros; USB-devices
   belong to the latter

- marvell subpackage is split to marvell and mwifiex; this is just for
   size, as both contain USB-capable WiFi

- realtek and mediatek subpackages aren't changed, as they are already
   small enough

- a new usb-network subpackage is created to contain the rest USB WiFi
   and Ethernet drivers

So, for the USB hotpluggable networks, we have the following packages:
- atheros
- bluetooth
- marvell
- mediatek
- mwifiex
- realtek
- usb-network

------------------------------------------------------------------------------

My questions to the wireless community are (1) Did we miss any issues that would 
hinder network access? (2) Does the above split handle the case of hardware or 
driver failure?

Thanks,

Larry