Originally, we use "gooftool probe" tool to probe the component, and then generate HWID. It works fine with most common components, but there are more and more components need special probing method. So the maintenance become more and more complicated.
To solve this issue, we implemented a new probe framework. (issue 667651) Now we should replace gooftool by the new one. The goal is:
- Split hardware and software in HWID.
Only verify software values, not encoded into HWID string.
- Integrate new probe framework with HWID generation
Replace the active probing "gooftool probe" by the passive probing.
- Integrate new probe framework with AVL
Generate the probe statement by selecting used component from AVL.
- Easy transfer from reference board to following device.
The document is here:
https://docs.google.com/document/d/1waGEK2DurNU2EwoauKd5KdlmsTpszOz_IBU8r0Vw4DA/edit#heading=h.4f2bfl5bnuef
Comment 1 by nsale@chromium.org
, Feb 8 2017