Linux wireless drivers development
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: linux-wireless <linux-wireless@vger.kernel.org>,
	Takashi Iwai <tiwai@suse.de>
Subject: Firmware Organization
Date: Mon, 19 Aug 2019 11:25:55 -0500	[thread overview]
Message-ID: <53ebd786-7966-1998-951e-b0a0ee7ff39e@lwfinger.net> (raw)

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

                 reply	other threads:[~2019-08-19 16:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53ebd786-7966-1998-951e-b0a0ee7ff39e@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=tiwai@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox