4a Only hal listed in the json file should be loaded and activated
Won't Fix
Description
The HAL to be used listed in the json file /usr/agl-service-audio-4a/ahl-agl-service-audio-4a-config.json
BUT all hal present in the 4a hal directory are loaded /usr/agl-service-audio-4a/ahl-agl-service-audio-4a-config.json
This creates :
- systematic error in some cases (e.g. some intel config) - slow down the boot process - can induce errors on non tested, non needed configurations
4a should only load the hal which are listed in the json file.
Environment
None
Activity
Show:
Jan-Simon Moeller
June 22, 2019 at 2:41 PM
Closing as won't fix.
Stephane Desneux
May 15, 2019 at 8:45 PM
(edited)
Is there a specific bug open for Vayu support? If not, it would be good to create one. This is not in the topic of this current issue and BTW I think this issue should be closed as what is described doesn't apply to current 4A version AFAICS.
or in our team can provide "blind support" to help in writing a HAL for Vayu but we can't write nor test the HAL as we don't have any Vayu board at hand.
Documentation on how to write a HAL is available in the sources:
The HAL to be used listed in the json file
/usr/agl-service-audio-4a/ahl-agl-service-audio-4a-config.json
BUT all hal present in the 4a hal directory are loaded
/usr/agl-service-audio-4a/ahl-agl-service-audio-4a-config.json
This creates :
- systematic error in some cases (e.g. some intel config)
- slow down the boot process
- can induce errors on non tested, non needed configurations
4a should only load the hal which are listed in the json file.