From: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH] references: Drop references without any spec reference
Date: Wed, 4 Mar 2020 18:36:40 -0600 [thread overview]
Message-ID: <20200305003640.4263-1-robh@kernel.org> (raw)
A bunch of the references to external docs are never referenced in the
spec. Let's just remove them.
Signed-off-by: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
---
source/references.rst | 62 -------------------------------------------
1 file changed, 62 deletions(-)
diff --git a/source/references.rst b/source/references.rst
index ff5b1a08b02e..a37ded9ccade 100644
--- a/source/references.rst
+++ b/source/references.rst
@@ -1,87 +1,25 @@
-.. [b1] *Power ISAâ„¢*, Version 2.06 Revision B, July 23, 2010. It is
- available from power.org (http://power.org)
.. [IEEE1275] *Boot (Initialization Configuration) Firmware: Core Requirements
and Practices*, 1994, This is the core standard (also known as IEEE
1275) that defines the devicetree concept adopted by the |spec| and
|epapr|. It is available from Global Engineering (http://global.ihs.com/).
-.. [b3] *PowerPC Processor Binding to IEEE 1275-1994 Standard for Boot
- (Initialization, Configuration) Firmware*, Version 2.1, Open Firmware
- Working Group,
- (http://playground.sun.com/1275/bindings/ppc/release/ppc-2_1.html),
- 1996, This document specifies the PowerPC processor specific binding
- to the base standard.
-
-.. [b4] *booting-without-of.txt*, Ben Herrenschmidt, Becky Bruce, et
- al., From the Linux kernel source tree (http://www.kernel.org/),
- Describes the devicetree as used by the Linux kernel.
-
-.. [b5] *Device Trees Everywhere*, David Gibson and Ben Herrenschmidt
- (http://ozlabs.org/~dgibson/home/papers/dtc-paper.pdf), An overview
- of the concept of the devicetree and devicetree compiler.
-
-.. [b6] *PCI Bus Binding to: IEEE Std 1275-1994 Standard for Boot
- (Initialization Configuration) Firmware*, Revision 2.1, Open Firmware
- Working Group, 1998
- (http://playground.sun.com/1275/bindings/pci/pci2_1.pdf)
-
.. [b7] *Open Firmware Recommended Practice: Interrupt Mapping*, Version
0.9, Open Firmware Working Group, 1996
(http://playground.sun.com/1275/practice/imap/imap0_9d.pdf)
-.. [b8] *Open Firmware Recommended Practice: Device Support Extensions*,
- Version 1.0, Open Firmware Working Group, 1997,
- (http://playground.sun.com/1275/practice/devicex/dse1_0a.html) This
- document describes the binding for various device types such as
- network, RTC, keyboard, sound, etc.
-
-.. [b9] *Open Firmware Recommended Practice: Universal Serial Bus
- Binding to IEEE 1275*, Version 1, Open Firmware Working Group, 1998
- (http://playground.sun.com/1275/bindings/usb/usb-1_0.ps)
-
.. [CHRP] *PowerPC Microprocessor Common Hardware Reference Platform
(CHRP) Binding*, Version 1.8, Open Firmware Working Group, 1998
(http://playground.sun.com/1275/bindings/chrp/chrp1_8a.ps). This
document specifies the properties for Open PIC-compatible interrupt
controllers.
-.. [b11] *CHRP ISA Interrupt Controller Device Binding*, Unapproved
- Draft version 1.1, Open Firmware Working Group, Aug 19, 1996
- (http://playground.sun.com/1275/bindings/devices/postscript/isa-pic-1_1d.ps)
-
-.. [b12] *The Open Programmable Interrupt Controller (PIC) Register
- Interface Specification*, Revision 1.2, Advanced Micro Devices and
- Cyrix Corporation, October 1995
-
-.. [b13] *PCI Local Bus Specification*, Revision 2.2, PCI Special
- Interest Group
-
-.. [b14] *PCI Express Base Specification*, Revision 1.0a, PCI Special
- Interest Group
-
-.. [b15] *PCI-Express Binding to OF*, P1275 Openboot Working Group
- Proposal, 18 August 2004
-
.. [PAPR] *Power.org Standard for Power Architecture Platform
Requirements*, power.org
-.. [b17] *System V Application Binary Interface, Edition 4.1*, Published
- by The Santa Cruz Operation, Inc., 1997
-
.. [b18] *The Open Programmable Interrupt Controller (PIC) Register
Interface Specification Revision 1.2*, AMD and Cyrix, October 1995
-.. [b19] *RFC 2119, Key words for use in RFCs to Indicate Requirement
- Levels*, http://www.ietf.org/rfc/rfc2119.txt
-
-.. [b20] *64-bit PowerPC ELF Application Binary Interface Supplement
- 1.9*, Ian Lance Taylor, 2004
-
.. [EPAPR] *Power.org Standard for Embedded Power Architecture
Platform Requirements*, power.org, 2011,
https://www.power.org/documentation/power-org-standard-for-embedded-power-architecture-platform-requirements-epapr-v1-1-2/
-
-.. [ARMv8] *ARM DDI 0487 ARM(c) Architecture Reference Manual,
- ARMv8 for ARMv8-A architecture profile*, ARM,
- http://infocenter.arm.com/help/topic/com.arm.doc.ddi0487a.h/index.html
--
2.20.1
reply other threads:[~2020-03-05 0:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200305003640.4263-1-robh@kernel.org \
--to=robh-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.