From: Marcel Holtmann <marcel@holtmann.org>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Kalle Valo <kvalo@codeaurora.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
Troy Tan <troy_tan@realsil.com.cn>,
netdev@vger.kernel.org, linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH V2 5/6] rtlwifi: btcoexist: Add routines for RTL8812AE kernel socket communications
Date: Fri, 30 Jan 2015 10:05:24 -0800 [thread overview]
Message-ID: <B814EF26-CBC9-43E4-A6C9-761A013F85C1@holtmann.org> (raw)
In-Reply-To: <54CBA0CE.8030800@lwfinger.net>
Hi Larry,
>>> I'm adding bluetooth list to the discussion. Full patch is available
>>> here:
>>>
>>> https://patchwork.kernel.org/patch/5712591/
<snip>
>>> So the wireless driver communicates with the bluetooth driver (which is
>>> not in upstream) via a localhost UDP connection?
>>
>> I think the first order of business should be to get the Bluetooth driver upstream. Until that has happened this is all kinda pointless discussion.
>
> I agree with this; however, the last time I tried to submit a BT driver for Realtek, I was told that this driver should use some (as yet included) feature. I have watched the driver development, and if that feature was ever included, it was in a form that I did not recognize. I'm sorry that this is vague, but this happened a long time ago.
if the Bluetooth side is running over USB, then it should be driven from the existing btusb.ko module with a vendor specific ->setup() callback. However nothing materialized that I could merge it.
>>> I know there's a general need for something similar like this, but it
>>> needs to properly discussed and designed.
>>
>> This is just insane. Clear NAK.
>>
>> Two kernel modules will not use UDP ports over the loopback interface to communicate with each other.
>
> I will work on combining the latest BT drivers from Realtek with btusb to see if I can achieve a patch that will both work with the Realtek hardware, and get approval from the reviewers.
>
> What would be an approved method of communicating between two kernel modules? Is there some example in the kernel that I could study?
We need a btcoex subsystem that both WiFi and Bluetooth can register to and communicate with.
Regards
Marcel
next prev parent reply other threads:[~2015-01-30 18:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-26 20:42 [PATCH 0/6 V2] Some changes for rtlwifi Larry Finger
2015-01-26 20:42 ` [PATCH V2 1/6] rtlwifi: Change logging level for key change Larry Finger
2015-01-30 15:47 ` Larry Finger
2015-02-03 13:01 ` Kalle Valo
2015-01-26 20:42 ` [PATCH V2 2/6] rtlwifi: btcoexist: Remove typedef statements Larry Finger
2015-01-26 20:42 ` [PATCH V2 3/6] rtlwifi: btcoexist: Add routines for RTL8812AE with single antenna Larry Finger
2015-01-26 20:42 ` [PATCH V2 4/6] rtlwifi: btcoexist: Add routines for RTL8812AE with dual antennae Larry Finger
2015-01-26 20:42 ` [PATCH V2 5/6] rtlwifi: btcoexist: Add routines for RTL8812AE kernel socket communications Larry Finger
2015-01-30 9:19 ` Kalle Valo
2015-01-30 9:57 ` Marcel Holtmann
2015-01-30 15:18 ` Larry Finger
2015-01-30 18:05 ` Marcel Holtmann [this message]
2015-02-03 12:29 ` btcoex subsystem Kalle Valo
2015-02-12 20:28 ` Marcel Holtmann
2015-01-26 20:42 ` [PATCH V2 6/6] rtlwifi: btcoexist: Enable new routines for RTL8812AE Larry Finger
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=B814EF26-CBC9-43E4-A6C9-761A013F85C1@holtmann.org \
--to=marcel@holtmann.org \
--cc=Larry.Finger@lwfinger.net \
--cc=kvalo@codeaurora.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=troy_tan@realsil.com.cn \
/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;
as well as URLs for NNTP newsgroup(s).