Use <fqname> to avoid conflicts
The newer way of specifying the interface is using <fqname> and it also has the handy side-effect of not causing conflicts when we add the strongbox implementation to devices. Test: make # check $OUT for the correct manifest Change-Id: If8333814723261c4f3de375861ee19a6d922d55f
This commit is contained in:
parent
83208f0833
commit
15351dcf60
1 changed files with 1 additions and 5 deletions
|
@ -2,10 +2,6 @@
|
|||
<hal format="hidl">
|
||||
<name>android.hardware.keymaster</name>
|
||||
<transport>hwbinder</transport>
|
||||
<version>4.0</version>
|
||||
<interface>
|
||||
<name>IKeymasterDevice</name>
|
||||
<instance>default</instance>
|
||||
</interface>
|
||||
<fqname>@4.0::IKeymasterDevice/default</fqname>
|
||||
</hal>
|
||||
</manifest>
|
||||
|
|
Loading…
Reference in a new issue