linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org,
	Stuart Yoder <stuart.yoder@freescale.com>
Subject: Re: [PATCH] powerpc: delete boot-cpu and chosen nodes from all DTS files
Date: Wed, 14 Feb 2007 08:03:57 -0600	[thread overview]
Message-ID: <45D316CD.9070901@freescale.com> (raw)
In-Reply-To: <1171431334.20192.138.camel@localhost.localdomain>

Benjamin Herrenschmidt wrote:

>> I just don't understand why it's okay to leave it there.
> 
> To make sure there is one. I suspect kernel bits might get upset if it's
> absent.

That's not what I meant.  What I don't understand is: what's so special 
about the 8272 that its DTS should have a 'chosen' section, but no other 
DTS needs one?

Obviously, the kernel needs a 'chosen' section, and that's why U-Boot 
adds one.  And since U-Boot adds one, the DTS itself doesn't need one. 
Does the 8272 never use U-Boot?

  reply	other threads:[~2007-02-14 14:04 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-13 23:34 [PATCH] powerpc: delete boot-cpu and chosen nodes from all DTS files Timur Tabi
2007-02-13 23:57 ` Benjamin Herrenschmidt
2007-02-14  5:15   ` Timur Tabi
2007-02-14  5:19     ` David Gibson
2007-02-14  5:24       ` Timur Tabi
2007-02-14 14:40       ` Jon Loeliger
2007-02-14  5:27     ` Benjamin Herrenschmidt
2007-02-14  5:31       ` Timur Tabi
2007-02-14  5:35         ` Benjamin Herrenschmidt
2007-02-14 14:03           ` Timur Tabi [this message]
2007-02-14 20:23             ` Guennadi Liakhovetski
2007-02-14 20:32               ` Timur Tabi
2007-02-14 20:47                 ` Guennadi Liakhovetski
2007-02-14 20:51                   ` Timur Tabi
2007-02-14 20:58                     ` Guennadi Liakhovetski
2007-02-14 20:54             ` Benjamin Herrenschmidt
2007-02-14 21:02               ` Timur Tabi
2007-02-14 21:17                 ` Benjamin Herrenschmidt
2007-02-14 21:58                   ` Timur Tabi
2007-02-14 22:53                     ` Benjamin Herrenschmidt
2007-02-14 23:37                   ` David Gibson
2007-02-14 21:09               ` [PATCH] powerpc: delete boot-cpu and chosen nodes from all DTSfiles Yoder Stuart-B08248
2007-02-14 23:37                 ` David Gibson
2007-02-15  1:45     ` [PATCH] powerpc: delete boot-cpu and chosen nodes from all DTS files Segher Boessenkool
  -- strict thread matches above, loose matches on Subject: below --
2007-02-13 16:47 Timur Tabi
2007-02-13 17:16 ` Kumar Gala
2007-02-13 17:20   ` Timur Tabi
2007-02-13 19:29   ` Timur Tabi
2007-02-15  1:42   ` Segher Boessenkool
2007-02-14  0:31 ` David Gibson
2007-02-14  5:18   ` Timur Tabi
2007-02-14  5:24     ` David Gibson
2007-02-14 14:05       ` Timur Tabi
2007-02-14 23:33         ` David Gibson
2007-02-14 23:47           ` Timur Tabi
2007-02-15  1:40           ` Segher Boessenkool
2007-02-15 16:18           ` Timur Tabi

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=45D316CD.9070901@freescale.com \
    --to=timur@freescale.com \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.org \
    --cc=stuart.yoder@freescale.com \
    /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).