sync_up: Add meeting notes page for next week.

[libreriscv.git] / 22nm_PowerPI.mdwn

diff --git a/22nm_PowerPI.mdwn b/22nm_PowerPI.mdwn
index 561fc2feb8f7518cabcb44621af937766e93a589..e1fa7f0a8f36a743bd197d62fe7e4d1016965d46 100644 (file)
--- a/22nm_PowerPI.mdwn
+++ b/22nm_PowerPI.mdwn
@@ -30,7 +30,7 @@ available* for use in products on the general market.
 The *only reason*
 that it went into the Raspberry Pi at all (selling in far smaller quantities) was because Eben Upton was an employee of Broadcom and had access to NDA'd internal datasheets.  Crucially: on
 learning that it was to be deployed in an Educational market, Broadcom
-could not exactly say "no".
+could not exactly say "no."
 
 In eight years, 36 million "Pi" units have been sold.  However this is not
 all the same processor: there are four variants (Model A/B thru Pi 4). Thus
@@ -84,7 +84,7 @@ up to 12-14 different products.
   - dual 32-bit DDR3/4 interfaces.
   - Suitable for 4k HD resolution screens and Graphics Card capability.
 
-By re-packaging the same die in different FPGA packages it meets the
+By re-packaging the same die in different FBGA packages it meets the
 needs of different markets without significant NREs.  Texas Instruments
 and Freescale/NXP and many other companies follow this practice.
 
@@ -150,13 +150,13 @@ NREs are still required**
  - Standard "Pi / Arduino" SoC-style interfaces including UART, I2C,
    SPI, GPIO, PWM, EINT, AC97.
 
-The "PI / Arduino" style interfaces are provided so as to be pin-comoatibke with the existing "Shield" 3rd party producy markets.
+The "PI / Arduino" style interfaces are provided so as to be pin-compatible with the existing "Shield" 3rd party product markets.
 
 # Interfaces
 
-Much of the advanced section is "under consideration" because there are proprietary firmware issues involved as well as high power consumption and high costs involved.  OpenCAPI for example would, in 22nm, at 25 ghz, be an enormous power draw (IBM used 14nm for the POWER9 25ghz SERDES)
+Much of the advanced section is "under consideration" because there are proprietary firmware issues involved as well as high power consumption and high costs involved.  OpenCAPI for example would, in 22nm, at 25 GHz, be an enormous power draw (IBM used 14nm for the POWER9 25GHz SERDES)
 
-HDCP is present in HDMI, as well as being optional in eDP and by extension USB-C as well.  Licensing of any of these Controllers therefore introduces the risk of closed firmware which will be viewed unfavourably by the educational markets, libre/open supporters and advocates, as well as cause Customer Support issues and introduce security vulnerabilities that *cannot be fixed or evaluated*.
+HDCP is present in HDMI, as well as being optional in eDP and by extension USB-C as well.  Licensing of any of these Controllers therefore introduces the risk of closed firmware which will be viewed unfavorably by the educational markets, libre/open supporters and advocates, as well as cause Customer Support issues and introduce security vulnerabilities that *cannot be fixed or evaluated*.
 
 Great care therefore needs to be taken in selecting the advanced interfaces.