devicetree-compiler.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
To: Frank Rowand <frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Thomas Huth <thuth-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Home Page of dtc is gone?
Date: Wed, 28 Sep 2016 11:29:55 +1000	[thread overview]
Message-ID: <20160928012955.GC14447@umbus.fritz.box> (raw)
In-Reply-To: <57EAD19F.2060404-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 2375 bytes --]

On Tue, Sep 27, 2016 at 01:07:59PM -0700, Frank Rowand wrote:
> On 09/26/16 22:25, David Gibson wrote:
> > On Mon, Sep 26, 2016 at 06:18:07PM +0200, Thomas Huth wrote:
> >>  Hi all,
> >>
> >> according to the README, the home page of dtc is:
> >>  http://devicetree.org/Device_Tree_Compiler
> >> However, when I open that URL in a browser, I only get a 404 error.
> >> Seems like the Wiki that used to be there is gone now and dtc needs a
> >> new home page?
> > 
> > Ah.. I'm not really sure who looks after the devicetree.org pages
> > nowadays.  I think it used to be Grant Likely, but I'm not sure if
> > it's still him.
> 
> The devicetree.org site has been re-purposed for the process of updating
> the device tree specification (previously known as ePAPR). The old
> contents of the root of devicetree.org has been relocated to
> elinux.org/Device_Tree_Usage
> 
> The most recent version of the Device_Tree_Compiler page (according to
> https://web.archive.org/web/20160326052957/http://www.devicetree.org/Device_Tree_Compiler)
> did not have much content. The contents of that page is:
> 
> 
>    Device Tree Compiler
>    Current revision (unreviewed)
> 
>    The Device Tree Compiler (DTC) is the toolchain for building device tree source files (*.dts)
>    into the binary format (*.dtb).
> 
>    libfdt is a BSD-licenses library for manipulating device tree files. Since it is BSD licensed,
>    it may be freely incorporated into other software such as firmware and operating system loaders.
>    libfdt can be found in the dtc git repository.
> 
>    Source Code
> 
>    Source for dtc and libfdt is maintained in a git repository on git.kernel.org. You can find the
>    repository here:
> 
>    https://git.kernel.org/cgit/utils/dtc/dtc.git
> 
>    Or you can clone it with the following command:
> 
>    git clone git://git.kernel.org/pub/scm/utils/dtc/dtc.git
> 
> 
> Most of that information is redundant for README, since README is already in the dtc
> git repo. Maybe the best solution is to remove the link to devicetree.org from
> README.

Yeah, that's probably the best idea in the short term.  Pushed.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      parent reply	other threads:[~2016-09-28  1:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-26 16:18 Home Page of dtc is gone? Thomas Huth
     [not found] ` <1f25b3eb-efbb-561c-1eff-f3daebdaa80a-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-09-26 16:49   ` Warner Losh
2016-09-27  5:25   ` David Gibson
     [not found]     ` <20160927052513.GA5956-K0bRW+63XPQe6aEkudXLsA@public.gmane.org>
2016-09-27 20:07       ` Frank Rowand
     [not found]         ` <57EAD19F.2060404-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-09-28  1:29           ` David Gibson [this message]

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=20160928012955.GC14447@umbus.fritz.box \
    --to=david-xt8fgy+axnrb3ne2bgzf6laj5h9x9tb+@public.gmane.org \
    --cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=thuth-H+wXaHxf7aLQT0dZR+AlfA@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).