ftop 0.2.4

• GPU frequency on chips that list more states than their table has values. On an M6 the system reports 15 GPU states (P1–P15) while the GPU's frequency table has 13 values, and ftop showed no GPU frequency at all. It now reads the n-th state at the n-th table value as long as the states past the end of the table were not used in the interval. Part of #8.
• Nothing is guessed for a state the table does not cover. If the GPU does run in such a state, the frequency reads as unavailable for that interval and ftop doctor names the state, for example "the GPU ran in P14, which its frequency table of 13 values does not cover".
• The table's length comes from the chip. The GPU's node says how many states it has (perf-state-count); ftop uses that instead of assuming. On chips where the counts already matched, the figures are computed as before.
• ftop doctor --states prints more for the GPU: the number of states the node declares, every value of the frequency table in order, and which states lie past the table and whether the sample used them.

Not verified on an M6. That the system's n-th state is the table's n-th value is inferred from two samples of one machine. If you have an M6, the output of ftop doctor --states while the GPU is busy is what confirms it.

Install: 0.1.1 and later update themselves. Otherwise download Ftop-0.2.4-arm64.zip, unpack, move Ftop.app to ~/Applications, then follow the two commands in the README. Requires Apple Silicon and macOS 15 or later. The app is ad-hoc signed and not notarized.