Linux-Wireless Archive on
 help / color / Atom feed
From: Merlijn Wajer <>
To: Marcel Holtmann <>, Tony Lindgren <>
Cc: Sebastian Reichel <>,
	"Arthur D." <>,
	Bluez mailing list <>,,
Subject: Re: Droid 4 WiFi firmware loading error
Date: Tue, 18 Feb 2020 16:38:21 +0100
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1.1: Type: text/plain, Size: 1362 bytes --]

Hi Marcel,

On 14/02/2020 19:23, Marcel Holtmann wrote:
> Hi Tony,
>>> WTF :(
>>> Right now the BT driver and the WiFi driver are no aware of
>>> each other. Actually the kernel is not even aware, that both
>>> drivers are using the same chip. Unfortunately this will be
>>> tricky to solve properly. Since a system may have two WiLink
>>> devices, the only solution coming to my mind would be adding
>>> a link from the BT device to the WiFi device in device tree.
>>> Additionally we would need something in the WiLink driver to
>>> check if driver has been initialized properly for a given DT
>>> node.
>> Yeah exactly.. I think the best way would be to export something
>> like wlcore_register_bt/wlcore_unregister_bt.. And then have
>> wlcore_register_bt return -EAGAIN until wlcore is up.
> actually NO.
> We have rejected this many times for all hardware manufacturers. Please fix the firmware instead.

That could be a real challenge, given that we don't have access to the
firmware source. Are there other historic precedents besides "fix the
firmware" that could be relevant here?

Currently we're stuck with either blacklisting the bluetooth modules all
together, or potentially have out of tree patches -- neither are ideal
for (my/our) "Mainline GNU/Linux" on a smartphone goal.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      reply index

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <op.0fudjzcyhxa7s4@supervisor.net28>
     [not found] ` <>
     [not found]   ` <op.0fuie5cdhxa7s4@supervisor.net28>
     [not found]     ` <>
     [not found]       ` <op.0fu85owhhxa7s4@supervisor.net28>
     [not found]         ` <>
     [not found]           ` <>
     [not found]             ` <op.0fwkyxvihxa7s4@supervisor.net28>
     [not found]               ` <>
     [not found]                 ` <op.0fw0oas5hxa7s4@supervisor.net28>
     [not found]                   ` <>
2020-02-13 21:54                     ` Arthur D.
2020-02-14 16:11                       ` Sebastian Reichel
2020-02-14 17:45                         ` Tony Lindgren
2020-02-14 18:23                           ` Marcel Holtmann
2020-02-18 15:38                             ` Merlijn Wajer [this message]

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:

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

  git send-email \ \ \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-Wireless Archive on

Archives are clonable:
	git clone --mirror linux-wireless/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-wireless linux-wireless/ \
	public-inbox-index linux-wireless

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone