News: 0001601199

  ARM Give a man a fire and he's warm for a day, but set fire to him and he's warm for the rest of his life (Terry Pratchett, Jingo)

Intel Linux Driver Preps For Up To 13 Different Panther Lake H SoCs

([Intel] 4 Hours Ago Panther Lake H)


It looks like the upcoming Intel Panther Lake H SoCs for the next-gen premium/high-end performance laptop market there could be quite a few different SKUs. A new patch for an Intel open-source driver expands the Panther Lake H line-up from three to 13 different IDs.

Queued last week for the Intel IGEN6 Error Detection And Correction "EDAC" driver is adding support for more Panther Lake H SoCs. There were already three Panther Lake H device IDs in this driver but ten more were added to bring the total count of PTL-H device IDs to 13. The IGEN6 EDAC driver is used for in-band ECC (IBECC) on capable designs for dealing with memory controller error reporting. Each device ID is for a different compute die ID.

[1]This patch rounding out the Panther Lake H SoC device count to 13 is queued into the "edac-for-next" Git branch of the RAS.git tree. Thus it should be merged as part of the upcoming Linux 6.20~7.0 kernel cycle opening up in February.

Thirteen different compute die IDs is quite a lot considering between Arrow Lake U / H were just three different compute die IDs in the same EDAC driver. The next closest was Alder Lake N with 12 SKUs or going back to Elkhart Lake 15 different SKUs. Given the increased number with ADL-N and Elkart Lake also appearing in a number of thin form factor devices and other uses beyond traditional "-H" level laptops, perhaps Intel with Panther Lake H is also anticipating increased roles across different markets.



[1] https://git.kernel.org/pub/scm/linux/kernel/git/ras/ras.git/commit/?h=edac-for-next&id=4c36e6106997b6ad8f4a279b4bdbca3ed6f53c6c



THE STORY OF CREATION
or
THE MYTH OF URK

In the beginning there was data. The data was without form and null, and
darkness was upon the face of the console; and the Spirit of IBM was moving
over the face of the market. And DEC said, "Let there be registers;" and
there were registers. And DEC saw that they carried; and DEC separated the
data from the instructions. DEC called the data Stack, and the instructions
they called Code. And there was evening and there was morning, one interrupt
...
-- Rico Tudor