diff mbox

Documentation/devicetree: fix dead links to PCI/OF specs

Message ID 20170707004323.22550-1-briannorris@chromium.org (mailing list archive)
State New, archived
Delegated to: Bjorn Helgaas
Headers show

Commit Message

Brian Norris July 7, 2017, 12:43 a.m. UTC
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@chromium.org>
---
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(-)

Comments

Rob Herring (Arm) July 10, 2017, 2:33 p.m. UTC | #1
On Thu, Jul 06, 2017 at 05:43:23PM -0700, Brian Norris wrote:
> 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@chromium.org>
> ---
> 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.

This site doesn't seem to be complete. There was still a complete mirror 
(matching playground.sun.com) at one point, but I can't seem to find it 
now. Fortunately, I had archived off the whole mirror with the intention 
of putting it on devicetree.org. Let me get moving on that.

Rob
Brian Norris July 10, 2017, 5:43 p.m. UTC | #2
On Mon, Jul 10, 2017 at 09:33:13AM -0500, Rob Herring wrote:
> On Thu, Jul 06, 2017 at 05:43:23PM -0700, Brian Norris wrote:
> > 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@chromium.org>
> > ---
> > 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.
> 
> This site doesn't seem to be complete. There was still a complete mirror 
> (matching playground.sun.com) at one point, but I can't seem to find it 
> now. Fortunately, I had archived off the whole mirror with the intention 
> of putting it on devicetree.org. Let me get moving on that.

I don't really know what "complete" is; I just want my URLs to point
somewhere useful :) So whatever suits you best. At least these links
correctly have titles / reference numbers included alongside, so I can
search for the correct thing myself.

BTW, I think I missed some other bad links in the tree. v4.12 release
still points to these:

origin/master:Documentation/devicetree/bindings/usb/usb-device.txt:5:http://www.firmware.org/1275/bindings/usb/usb-1_0.ps
origin/master:Documentation/devicetree/booting-without-of.txt:1285:<http://www.openfirmware.org/ofwg/practice/>

Regards,
Brian
Rob Herring (Arm) July 11, 2017, 7:01 p.m. UTC | #3
On Mon, Jul 10, 2017 at 12:43 PM, Brian Norris <briannorris@chromium.org> wrote:
> On Mon, Jul 10, 2017 at 09:33:13AM -0500, Rob Herring wrote:
>> On Thu, Jul 06, 2017 at 05:43:23PM -0700, Brian Norris wrote:
>> > 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@chromium.org>
>> > ---
>> > 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.
>>
>> This site doesn't seem to be complete. There was still a complete mirror
>> (matching playground.sun.com) at one point, but I can't seem to find it
>> now. Fortunately, I had archived off the whole mirror with the intention
>> of putting it on devicetree.org. Let me get moving on that.
>
> I don't really know what "complete" is; I just want my URLs to point
> somewhere useful :) So whatever suits you best. At least these links
> correctly have titles / reference numbers included alongside, so I can
> search for the correct thing myself.

Here's what it looks like:

http://people.linaro.org/~rob.herring/openfirmware/1275/

There's a bunch of really ancient stuff that we don't care about with
FDT and non-PC style systems.

> BTW, I think I missed some other bad links in the tree. v4.12 release
> still points to these:
>
> origin/master:Documentation/devicetree/bindings/usb/usb-device.txt:5:http://www.firmware.org/1275/bindings/usb/usb-1_0.ps

This should be in the above.

> origin/master:Documentation/devicetree/booting-without-of.txt:1285:<http://www.openfirmware.org/ofwg/practice/>

That should be this I think:

http://people.linaro.org/~rob.herring/openfirmware/1275/practice/

But don't send me patches with the above urls.

Rob
diff mbox

Patch

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: