Print this page
11641 spelling mistakes in section 7d of the manual

Split Close
Expand all
Collapse all
          --- old/usr/src/man/man7d/pchtemp.7d.man.txt
          +++ new/usr/src/man/man7d/pchtemp.7d.man.txt
↓ open down ↓ 2 lines elided ↑ open up ↑
   3    3  NAME
   4    4       pchtemp - Intel platform controller hub temperature sensor driver
   5    5  
   6    6  SYNOPSIS
   7    7       /dev/sensors/temperature/pch/*
   8    8  
   9    9  DESCRIPTION
  10   10       The pchtemp driver provides the system the ability to read the digital
  11   11       temperature sensor found on several Intel platform controller hub (PCH)
  12   12       chipsets.  The following chipsets are supported which cover most Intel
  13      -     Core familiy (non-Atom) CPUs starting with the Haswell generation:
       13 +     Core family (non-Atom) CPUs starting with the Haswell generation:
  14   14  
  15   15       -   Intel 8 Series / C220 Series Chipset Platform Controller Hub
  16   16  
  17   17       -   Intel 9 Series Chipset Family Platform Controller Hub
  18   18  
  19   19       -   Intel C610 Series Chipset and X99 Chipset Platform Controller Hub
  20   20  
  21   21       -   Intel 100 Series Chipset Family Platform Controller Hub
  22   22  
  23   23       -   Intel C620 Series Chipset Platform Controller Hub
↓ open down ↓ 12 lines elided ↑ open up ↑
  36   36       information can be dumped through the FMA developer utility fmtopo.
  37   37  
  38   38  SEE ALSO
  39   39       fmadm(1M)
  40   40  
  41   41       Intel Corporation, Intel 300 Series and Intel C240 Series Chipset Family
  42   42       Platform Controller Hub, 1,
  43   43       https://www.intel.com/content/dam/www/public/us/en/documents/datasheets/300-series-chipset-pch-datasheet-vol-1.pdf,
  44   44       March 2019, Document Number 337347-005.
  45   45  
  46      -illumos                         April 26, 2019                         illumos
       46 +illumos                        January 10, 2020                        illumos
    
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX