Given that Array BIST portion of IFS test suite (in [1]) can be run without any images, can I suggest the following edits On 1/2/2025 11:43 AM, Anisse Astier wrote: > Firmware images necessary for the In-field scan[1] functionality are not Firmware images necessary for certain tests in In Field Scan[1] test suite are not > available at the moment[2], and require having access to at least an > Intel customer account[3]. > > Update documentation to match current state, it can be updated again > when the images are finally published. > > [1] https://www.intel.com/content/www/us/en/support/articles/000099537/processors/intel-xeon-processors.html > [2] https://cdrdv2.intel.com/v1/dl/getContent/826383?explicitVersion=true > [3] https://www.intel.com/content/www/us/en/secure/design/confidential/software-kits/kit-details.html?kitId=815180 > > Signed-off-by: Anisse Astier <anisse@xxxxxxxxx> > --- > I realize Intel had a few troubled years, and that having this feature > in the kernel must be quite helpful to some users. But right now, it > cannot be used unless one has a commercial relationship with Intel. > > I am not advocating for the removal of this driver; this is just an > update of the documentation to show that the publication of the firmware > images necessary to use the driver might have fallen through the cracks, > and might not happen soon. > > Kind regards, > > Anisse > --- > drivers/platform/x86/intel/ifs/ifs.h | 11 +++++++---- > 1 file changed, 7 insertions(+), 4 deletions(-) > > diff --git a/drivers/platform/x86/intel/ifs/ifs.h b/drivers/platform/x86/intel/ifs/ifs.h > index 5c3c0dfa1bf8..9a7ad9cc9d08 100644 > --- a/drivers/platform/x86/intel/ifs/ifs.h > +++ b/drivers/platform/x86/intel/ifs/ifs.h > @@ -23,9 +23,11 @@ > * IFS Image > * --------- > * > - * Intel provides a firmware file containing the scan tests via > - * github [#f1]_. Similar to microcode there is a separate file for each > - * family-model-stepping. IFS Images are not applicable for some test types. > + * As of early 2025, Intel provides the firmware files containing the scan tests > + * to select customers [#f1]_. When this driver was merged in 2022, it was > + * announced that firmware files would be available via github [#f2]_. Similar > + * to microcode there is a separate file for each family-model-stepping. IFS > + * Images are not applicable for some test types. > * Wherever applicable the sysfs directory would provide a "current_batch" file > * (see below) for loading the image. > * > @@ -125,7 +127,8 @@ > * 2) Hardware allows for some number of cores to be tested in parallel. > * The driver does not make use of this, it only tests one core at a time. > * > - * .. [#f1] https://github.com/intel/TBD > + * .. [#f1] https://www.intel.com/content/www/us/en/support/articles/000099537/processors/intel-xeon-processors.html > + * .. [#f2] https://github.com/intel/TBD > * > * > * Structural Based Functional Test at Field (SBAF): Thanks Jithu
