linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Wei.Zhang@freescale.com
Subject: Re: [PATCH 1/4] Add DMA sector to Documentation/powerpc/booting-without-of.txt file.
Date: Tue, 17 Jul 2007 21:17:13 +1000	[thread overview]
Message-ID: <18076.42297.26124.137770@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <B2EA074C-5D8E-4E13-B6BF-E81FBA52E76E@kernel.crashing.org>

Segher Boessenkool writes:

> The device tree describes _all_ hardware in the system,
> not just the things that are somewhat harder to probe
> for.

Actually, for embedded systems, the device tree is really only
required to describe the things that it's useful for the Linux kernel
to know.

The point of the device tree for embedded systems is to provide
configuration information, not to be able to claim compliance with
some set of legalistic requirements. :)

I think in some cases we have gone a little over the top in trying to
put everything in the device tree, in fact.  Ultimately I think it has
to be up to the more experienced embedded developers to say how much
detail in the device tree is actually helpful and how much is dead
weight.

Paul.

  reply	other threads:[~2007-07-17 11:17 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-10  9:44 [PATCH 0/4] DMA engine driver for Freescale MPC8xxx processor Zhang Wei
2007-07-10  9:44 ` [PATCH 1/4] Add DMA sector to Documentation/powerpc/booting-without-of.txt file Zhang Wei
2007-07-10  9:44   ` [PATCH 2/4] Add dma sector to mpc8641hpcn board dts Zhang Wei
2007-07-10 13:55     ` Segher Boessenkool
2007-07-11  7:16       ` Zhang Wei-r63237
2007-07-11 11:27         ` Segher Boessenkool
2007-07-12  9:51           ` Zhang Wei-r63237
2007-07-10 13:57     ` Segher Boessenkool
2007-07-11  7:17       ` Zhang Wei-r63237
2007-07-10 14:01   ` [PATCH 1/4] Add DMA sector to Documentation/powerpc/booting-without-of.txt file Segher Boessenkool
2007-07-10 16:11     ` Scott Wood
2007-07-11 10:00       ` Zhang Wei-r63237
2007-07-11 15:23         ` Scott Wood
2007-07-11 17:53           ` Segher Boessenkool
2007-07-12  9:48             ` Zhang Wei-r63237
2007-07-12 17:12               ` Phil Terry
2007-07-12 19:10                 ` Scott Wood
2007-07-16 14:56                   ` Segher Boessenkool
2007-07-16 14:54                 ` Segher Boessenkool
2007-07-17 11:17                   ` Paul Mackerras [this message]
2007-07-17 15:36                     ` Segher Boessenkool
2007-07-11 11:18       ` Segher Boessenkool
2007-07-11 15:30         ` Scott Wood
2007-07-11 18:01           ` Segher Boessenkool
2007-07-11 18:18             ` Scott Wood
2007-07-11 18:43               ` Segher Boessenkool
2007-07-11 19:03                 ` Scott Wood
2007-07-11 19:19                   ` Segher Boessenkool
2007-07-11 19:27                     ` Scott Wood
2007-07-11 20:27                       ` Segher Boessenkool
2007-07-11 10:06     ` Zhang Wei-r63237
2007-07-11 11:40       ` Segher Boessenkool
2007-07-12  9:45         ` Zhang Wei-r63237

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=18076.42297.26124.137770@cargo.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --cc=Wei.Zhang@freescale.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=segher@kernel.crashing.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).