Patchwork [Documentation,09/14] RN: use "SoC hierarchy" instead of "SOC_FAMILY" or "SoC family"

login
register
mail settings
Submitter Mario Domenech Goulart
Date April 30, 2014, 12:56 p.m.
Message ID <1398862609-28655-9-git-send-email-mario@ossystems.com.br>
Download mbox | patch
Permalink /patch/71303/
State Accepted
Delegated to: Otavio Salvador
Headers show

Comments

Patch

diff --git a/release-notes/source/fsl-userspace-pkg.rst b/release-notes/source/fsl-userspace-pkg.rst
index e4e4420..1e2c09a 100644
--- a/release-notes/source/fsl-userspace-pkg.rst
+++ b/release-notes/source/fsl-userspace-pkg.rst
@@ -24,24 +24,24 @@  hardware optimization or some hardware test tools.
    imx boards. It can be cross-compiled for any other core, although
    it will only act as expect if executed on imx boards.
 
-The package version and variety varies on :ref:`soc-family`.
+The package version and variety varies on :ref:`soc-hierarchy`.
 For example, machines with i.MX28 SOC does not have VPU, the recipe imx-vpu is not needed.
 There are differences, as well, in GPU support recipes.
 
-------------------------------
-Version by :ref:`soc-family`
-------------------------------
+--------------------------------
+Version by :ref:`soc-hierarchy`
+--------------------------------
 
-The following table shows the version of each package depending on the :ref:`soc-family`.
+The following table shows the version of each package depending on the :ref:`soc-hierarchy`.
 
 .. include:: soc-pkg.inc
 
 
----------------------------------------
-Hardware relation by :ref:`soc-family`
----------------------------------------
+-----------------------------------------
+Hardware relation by :ref:`soc-hierarchy`
+-----------------------------------------
 
-The following table shows how packages interact with hardware depending on the :ref:`soc-family`
+The following table shows how packages interact with hardware depending on the :ref:`soc-hierarchy`
 
 .. include:: soc-pkg-optimization.inc
 
diff --git a/release-notes/source/index.rst b/release-notes/source/index.rst
index 2c42058..6a608a8 100644
--- a/release-notes/source/index.rst
+++ b/release-notes/source/index.rst
@@ -14,7 +14,7 @@  FSL Community BSP Release Notes
    introduction
    bsp-scope
    machines-maintainers
-   soc-family
+   soc-hierarchy
    kernel-linux
    u-boot
    barebox
diff --git a/release-notes/source/soc-family.rst b/release-notes/source/soc-family.rst
deleted file mode 100644
index 7ad9f44..0000000
--- a/release-notes/source/soc-family.rst
+++ /dev/null
@@ -1,10 +0,0 @@ 
-.. _soc-family:
-
-Soc Family
-============================
-
-SOC_FAMILY is a variable used to cluster the similar machines into families and allow a inheritance for similar hardware configuration.
-
-The current SOC_FAMILY tree can be see in the next graph:
-
-.. include:: soc-tree.inc
diff --git a/release-notes/source/soc-hierarchy.rst b/release-notes/source/soc-hierarchy.rst
new file mode 100644
index 0000000..7296eb2
--- /dev/null
+++ b/release-notes/source/soc-hierarchy.rst
@@ -0,0 +1,8 @@ 
+.. _soc-hierarchy:
+
+SoC Hierarchy
+============================
+
+The following tree shows the SoC hierarchy:
+
+.. include:: soc-tree.inc
diff --git a/release-notes/source/soc-tree.inc b/release-notes/source/soc-tree.inc
index 4afaf2d..51f8720 100644
--- a/release-notes/source/soc-tree.inc
+++ b/release-notes/source/soc-tree.inc
@@ -1,6 +1,6 @@ 
 .. code-block:: none
 
-  SOC_FAMILY
+  SoCs
   ??? mx3
   ?    ??? mx31
   ?    ??? mx35