1. 24 Jun, 2020 1 commit
    • Sandrine Bailleux's avatar
      Redirect security incident report to TrustedFirmware.org · 1367cc19
      Sandrine Bailleux authored
      
      
      All projects under the TrustedFirmware.org project now use the same
      security incident process, therefore update the disclosure/vulnerability
      reporting information in the TF-A documentation.
      
      ------------------------------------------------------------------------
      /!\ IMPORTANT /!\
      
      Please note that the email address to send these reports to has changed.
      Please do *not* use trusted-firmware-security@arm.com anymore.
      
      Similarly, the PGP key provided to encrypt emails to the security email
      alias has changed as well. Please do *not* use the former one provided
      in the TF-A source tree. It is recommended to remove it from your
      keyring to avoid any mistake. Please use the new key provided on
      TrustedFirmware.org from now on.
      ------------------------------------------------------------------------
      
      Change-Id: I14eb61017ab99182f1c45d1e156b96d5764934c1
      Signed-off-by: default avatarSandrine Bailleux <sandrine.bailleux@arm.com>
      1367cc19
  2. 08 Oct, 2019 1 commit
    • Paul Beesley's avatar
      doc: Convert internal links to RST format · 34760951
      Paul Beesley authored
      
      
      Currently links between documents are using the format:
      
      <path/to/><filename>.rst
      
      This was required for services like GitHub because they render each
      document in isolation - linking to another document is like linking
      to any other file, just provide the full path.
      
      However, with the new approach, the .rst files are only the raw
      source for the documents. Once the documents have been rendered
      the output is now in another format (HTML in our case) and so,
      when linking to another document, the link must point to the
      rendered version and not the .rst file.
      
      The RST spec provides a few methods for linking between content.
      The parent of this patch enabled the automatic creation of anchors
      for document titles - we will use these anchors as the targets for
      our links. Additional anchors can be added by hand if needed, on
      section and sub-section titles, for example.
      
      An example of this new format, for a document with the title
      "Firmware Design" is :ref:`Firmware Design`.
      
      One big advantage of this is that anchors are not dependent on
      paths. We can then move documents around, even between directories,
      without breaking any links between documents. Links will need to be
      updated only if the title of a document changes.
      
      Change-Id: I9e2340a61dd424cbd8fd1ecc2dc166f460d81703
      Signed-off-by: default avatarPaul Beesley <paul.beesley@arm.com>
      34760951
  3. 24 Jun, 2019 1 commit
  4. 24 May, 2019 1 commit
  5. 22 May, 2019 1 commit
    • Paul Beesley's avatar
      doc: Reword document titles · 8aa05055
      Paul Beesley authored
      
      
      This patch attempts to standardise the document titles as well as
      adding titles to documents that were missing one. The aim is to
      remove needless references to "TF-A" or "Trusted Firmware" in the
      title of every document and to make sure that the title matches
      with the document content.
      
      Change-Id: I9b93ccf43b5d57e8dc793a5311b8ed7c4dd245cc
      Signed-off-by: default avatarPaul Beesley <paul.beesley@arm.com>
      8aa05055
  6. 21 May, 2019 1 commit
    • Paul Beesley's avatar
      doc: Move documents into subdirectories · 40d553cf
      Paul Beesley authored
      
      
      This change creates the following directories under docs/
      in order to provide a grouping for the content:
      
      - components
      - design
      - getting_started
      - perf
      - process
      
      In each of these directories an index.rst file is created
      and this serves as an index / landing page for each of the
      groups when the pages are compiled. Proper layout of the
      top-level table of contents relies on this directory/index
      structure.
      
      Without this patch it is possible to build the documents
      correctly with Sphinx but the output looks messy because
      there is no overall hierarchy.
      
      Change-Id: I3c9f4443ec98571a56a6edf775f2c8d74d7f429f
      Signed-off-by: default avatarPaul Beesley <paul.beesley@arm.com>
      40d553cf
  7. 07 Mar, 2019 3 commits