Age | Commit message (Collapse) | Author | Files | Lines |
|
The configuration files should not be shipped with the sources.
Therefore we created a 4a-hal-configs repository as the central place for configs.
Move the configs there but leave and example in 4a-hal-cfg-example.
Bug-AGL: SPEC-2011
Change-Id: If3bed9a05955b9c6458656fabbe3ee12d1c5015b
Signed-off-by: Jan-Simon Möller <jsmoeller@linuxfoundation.org>
|
|
Enrich 'halmixer' section with bluetooth specific 'source' and 'stream'
during hal-bt plugin initialization.
Some parameters must be passed to plugin using 'params' key in controller
json plugin section.
This allows to get rid of must of the additional configuration when using
bluetooth in a hal.
Change-Id: I5820e75307a3394eca80cf783e7bc4c31c2d7659
Signed-off-by: Jonathan Aillet <jonathan.aillet@iot.bzh>
|
|
Added the 'radio_stream' to all the HALs. This makes the radio role
work in HighLevelAPI.
Change-Id: I8f34224ec3dbbb1312b65642d89e672716414ac9
Signed-off-by: Thierry Bultel <thierry.bultel@iot.bzh>
|
|
All hal that shouldn't be enable for the target will be disable using
a recipe in yocto.
4a-hal-generic shouldn't take care of enabling/disabling hals.
Change-Id: I38363fb7933ed73d7a4e855949ae9dd521db2862
Signed-off-by: Jonathan Aillet <jonathan.aillet@iot.bzh>
|