There are a few bugs with the iARK command (per my ignorancy), which include, and are sadly likely not limited to:
Using a query with the core/xeon name and a revision afterwards, for example e3 1505m v5 yields nothing.
This is because, we're meant to replace the space between e3 and 1505m with a -, which we currently cannot do.
However, what we can do is have the user supply that - always, and then the rest of the query can be formatted normally.
Using a query for 10th and 11th gen cores will fail, as it's required to query them as <brand modifier>-<generation indicator><SKU><Product Line> (i.e. i7-1065G7)
For the time being, there is no way around this. Later on, we will likely need to implement a hardcoded scheme for every naming scheme of Intel's processors, and update the user's query accordingly. This will take quite awhile.
There are a few bugs with the
iARKcommand (per my ignorancy), which include, and are sadly likely not limited to:Using a query with the core/xeon name and a revision afterwards, for example
e3 1505m v5yields nothing.This is because, we're meant to replace the space between
e3and1505mwith a-, which we currently cannot do.However, what we can do is have the user supply that
-always, and then the rest of the query can be formatted normally.Using a query for 10th and 11th gen cores will fail, as it's required to query them as
<brand modifier>-<generation indicator><SKU><Product Line>(i.e.i7-1065G7)