Searched refs:oem (Results 1 – 25 of 59) sorted by relevance
123
6 /cache/overlay/oem/upper u:object_r:vendor_file:s09 /mnt/scratch/overlay/oem/upper u:object_r:vendor_file:s0
142 #### `<oem>` Element143 Vendors can extend the fastboot protocol with oem commands. This allows vendors145 Fuzzy Fastboot allows testing these oem commands as well.153 | value | The oem command name | Ex: if value="foo", the oem command will start with "oem foo…158 <oem>160 <!-- This will test that "oem self_destruct now" returns 'okay' -->162 <!-- This will test that "oem self_destruct yesterday" returns 'fail' -->167 <!-- FF will first stage test_image.img before running 'oem foobar use_staged' -->169 …<!-- FF will run 'oem foobar send_response', upload data from device, then run the validator scrip…172 <oem/>[all …]
123 std::unordered_map<std::string, OemCommand> oem; member
31 ln -sf /oem/$(OSRELEASED_DIRECTORY)/product_id $(TARGET_OUT_ETC)/$(OSRELEASED_DIRECTORY)62 ln -sf /oem/$(OSRELEASED_DIRECTORY)/product_version $(TARGET_OUT_ETC)/$(OSRELEASED_DIRECTORY)
17 # /oem access
48 # /oem access
101 # /oem access
47 # /oem access
92 # /oem access
16 # /oem access
98 # /oem access
91 # /oem access
35 namespace.default.permitted.paths += /oem/app88 namespace.default.asan.permitted.paths += /data/asan/oem/app89 namespace.default.asan.permitted.paths += /oem/app
80 dev proc sys system data data_mirror odm oem acct config storage mnt apex debug_ramdisk \