From: Victor Gallardo <vgallardo@amcc.com>
To: linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH] Add AMCC Arches DTS
Date: Fri, 18 Jul 2008 12:32:11 -0700 (PDT) [thread overview]
Message-ID: <18536319.post@talk.nabble.com> (raw)
In-Reply-To: <20080716073913.100d259a@zod.rchland.ibm.com>
> Could you convert this to a dts-v1 file please? All the in-tree DTS
> files are dts-v1 and I'd very much like to keep it that way.
OK. Will look into this. I used the glacier.dts file as a base line. Is the
glacier.dts file in dts-v1 format?
> <snip>
> If this is a dual-460GT, why is there only one CPU node listed? Is it
> simply because Linux will only see one CPU as it is an AMP
> configuration?
Yes, the board is a dual processor board with each processor providing
independent resources. Each CPU will boots up with its own Linux image.
Victor Gallardo
--
View this message in context: http://www.nabble.com/-PATCH--Add-AMCC-Arches-DTS-tp18480767p18536319.html
Sent from the linuxppc-embedded mailing list archive at Nabble.com.
next prev parent reply other threads:[~2008-07-18 19:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-16 5:34 [PATCH] Add AMCC Arches DTS fkan
2008-07-16 11:39 ` Josh Boyer
2008-07-18 19:32 ` Victor Gallardo [this message]
2008-07-18 19:42 ` Jon Loeliger
2008-07-18 21:15 ` Victor Gallardo
2008-07-18 14:24 ` Stefan Roese
2008-07-18 22:10 ` Victor Gallardo
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=18536319.post@talk.nabble.com \
--to=vgallardo@amcc.com \
--cc=linuxppc-embedded@ozlabs.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).