408703e8dd
We've already got GATT services in subsys/bluetooth/services so subsys/bluetooth/mesh is a more natural place. Aditionally this aims to fix the Kconfig dependencies to be able to use mesh together with BT_CUSTOM (i.e. a custom, potentially non-HCI, host stack). Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
18 lines
495 B
C
18 lines
495 B
C
/* Bluetooth Mesh */
|
|
|
|
/*
|
|
* Copyright (c) 2017 Intel Corporation
|
|
*
|
|
* SPDX-License-Identifier: Apache-2.0
|
|
*/
|
|
|
|
#define BT_MESH_KEY_PRIMARY 0x0000
|
|
#define BT_MESH_KEY_ANY 0xffff
|
|
|
|
#define BT_MESH_ADDR_IS_UNICAST(addr) ((addr) && (addr) < 0x8000)
|
|
#define BT_MESH_ADDR_IS_GROUP(addr) ((addr) >= 0xc000 && (addr) <= 0xff00)
|
|
#define BT_MESH_ADDR_IS_VIRTUAL(addr) ((addr) >= 0x8000 && (addr) < 0xc000)
|
|
#define BT_MESH_ADDR_IS_RFU(addr) ((addr) >= 0xff00 && (addr) <= 0xfffb)
|
|
|
|
struct bt_mesh_net;
|