Porting the Communication Subsystem

The communication subsystem porting process involves Wi-Fi and Bluetooth adaptation. Vendors need to perform adaptation based on the chip conditions.

Procedure

To implement Wi-Fi adaptation, perform the following steps:

Path: foundation/communication/wifi_lite/BUILD.gn

group("wifi") {
  deps = [ "$ohos_board_adapter_dir/hals/communication/wifi_lite/wifiservice:wifiservice" ]
}

As shown above, the .c file of the vendor adaptation interfaces is stored in the $ohos_board_adapter_dir/hals/communication/wifi_lite/wifiservice directory, where the target in the BUILD.gn file is wifiservice. Table 1, Table 2, and Table 3 list the Wi-Fi interfaces that need to be adapted by vendors. Table 4 and Table 5 list the Bluetooth interfaces.

Table 1 wifi_device.h

Table 2 wifi_hotspot_config.h

Table 3 wifi_hotspot.h

Table 4 ohos_bt_gatt.h

Table 5 ohos_bt_gatt_server.h

NOTE

The APIs may vary according to the version. Adapt the APIs according to the specific file of the current version.

Example

1. Add the communication subsystem to the config.json file.

   Path: vendor/MyVendorCompany/MyProduct/config.json

   The sample code is as follows:

   { 
       "subsystem": "communication", 
       "components": [ 
           { "component": "wifi_lite", "features":[] }
       ] 
   },
   

2. Add an adaptation file.

   In the vendor/MyVendorCompany/MyProduct/config.json file, set ohos_board_adapter_dir to //vendor/MyVendorCompany/MyProduct/adapter.

   In the ohos_board_adapter_dir directory, adapt the Wi-Fi and Bluetooth APIs based on the aforementioned header files.