Received-SPF: pass (google.com: best guess record for domain of linux-bluetooth-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   "Gix, Brian" <brian.gix@intel.com>
To:     =?windows-1250?Q?Micha=B3_Lowas-Rzechonek?= 
        <michal.lowas-rzechonek@silvair.com>
CC:     "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH BlueZ 0/1] mesh: Move HCI handling to mesh-io-generic
Thread-Topic: [PATCH BlueZ 0/1] mesh: Move HCI handling to mesh-io-generic
Thread-Index: AQHVJcjDSjBUtBqdoUSLgirFfevJ66ah1QzBgAABaTY=
Date:   Tue, 18 Jun 2019 20:04:19 +0000
Message-ID: <F5913AD6-9050-422D-8BED-AB6CD2B434D3@intel.com>
References: <20190618112655.19963-1-michal.lowas-rzechonek@silvair.com>,<34B4A752-E039-4CAD-A8A7-E8CC137DC8A4@intel.com>
In-Reply-To: <34B4A752-E039-4CAD-A8A7-E8CC137DC8A4@intel.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="windows-1250"
Content-Transfer-Encoding: 8BIT
MIME-Version: 1.0
Sender: linux-bluetooth-owner@vger.kernel.org
Precedence: bulk

Hi Micha? (again)

> On Jun 18, 2019, at 12:59 PM, Gix, Brian <brian.gix@intel.com> wrote:
> 
> Hi Micha?,
> 
>> On Jun 18, 2019, at 4:27 AM, Micha? Lowas-Rzechonek <michal.lowas-rzechonek@silvair.com> wrote:
>> 
>> This patch enables us to implement more I/O layers, particularly non-HCI
>> ones.
>> 
>> As of Bluetooth 5.1, standard HCI commands don't allow precise control
>> over mesh-related advertising, making this I/O layer very inefficient.
>> Therefore, it is desirable to have an option to use a non-HCI transport
>> to talk to radio transceiver, at least until Bluetooth extends HCI so
>> that standard BLE Controllers achieve good performance.
> 
> The intent if the architecture was to allow for finer control with future controllers, and thus a mesh-io.c which doesn?t assume anything about underlying controllers, and then an *initial* mesh-io-generic.c which is what gets used by 4.x controllers... as more controllers are supported with finer tuning available, then mesh-io-<bt5+>.c can be added to the abstracted list.

We are also talking about how to share controllers between bluetoothd and meshd...   one idea is using the MGMT interface to send and receive specific advertisements...   that would necessitate a mesh-io-mgmt.c. However, it will also require support in the kernel.


> 
>> 
>> Another use case would be a non-local radio: the mesh stack can run on a
>> secure device, but due to physical constraints it might need to use
>> radio transceiver located at a distance, connected e.g. via LAN.
>> 
>> Micha? Lowas-Rzechonek (1):
>> mesh: Move HCI handling to mesh-io-generic
>> 
>> mesh/main.c            |   4 +-
>> mesh/mesh-io-api.h     |   3 +-
>> mesh/mesh-io-generic.c | 203 ++++++++++++++++++++++++++++++++++++-----
>> mesh/mesh-io.c         |  17 ++--
>> mesh/mesh-io.h         |   2 +-
>> mesh/mesh.c            | 189 +++-----------------------------------
>> mesh/mesh.h            |   4 +-
>> 7 files changed, 209 insertions(+), 213 deletions(-)
>> 
>> -- 
>> 2.19.1
>>