On 6/13/2016 9:54 AM, Gabriele Paoloni wrote:
As you can see here Liudongdong has replaced oem_revision with oem_table_id.
Now it seems that there are some platforms that have already shipped using a matching based on the oem_revision (right Jon?)
However I guess that if in FW they have defined oem_table_id properly they should be able to use this mechanism without needing to a FW update.
Can these vendors confirm this?
Tomasz do you think this can work for Cavium Thunder?
Thanks
Gab
Why not have all three of them?
The initial approach was OEM id and revision id.
Jeff Hugo indicated that addition (not removing any other fields) of table id would make more sense.