www.firmware.org doesn't resolve for me. I found these equivalent URLs
by taking the redirects from the previous (openfirmware.org) URLs, as
seen before commit f517256a6867 ("Documentation/devicetree: Update PCI
Device Tree bindings") updated them.
Signed-off-by: Brian Norris <briannorris@xxxxxxxxxxxx>
---
This is my best attempt at a resolution. I'm not sure what firmware.org is or
if its owner is even legit. It does seem like openfirmware.info is a proper
successor to openfirmware.org, and it's registered to a coreboot dev.
Documentation/devicetree/bindings/pci/pci.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/pci/pci.txt b/Documentation/devicetree/bindings/pci/pci.txt
index 50f9e2ca5b13..13a73b423233 100644
--- a/Documentation/devicetree/bindings/pci/pci.txt
+++ b/Documentation/devicetree/bindings/pci/pci.txt
@@ -1,12 +1,12 @@
PCI bus bridges have standardized Device Tree bindings:
PCI Bus Binding to: IEEE Std 1275-1994
-http://www.firmware.org/1275/bindings/pci/pci2_1.pdf
+https://www.openfirmware.info/data/docs/bus.pci.pdf
And for the interrupt mapping part:
Open Firmware Recommended Practice: Interrupt Mapping
-http://www.firmware.org/1275/practice/imap/imap0_9d.pdf
+https://www.openfirmware.info/data/docs/rec.intmap.d09.pdf
Additionally to the properties specified in the above standards a host bridge
driver implementation may support the following properties:
--
2.13.2.725.g09c95d1e9-goog
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
