From: Wolfgang Denk <wd@denx.de>
To: "Pedro Luis D. L." <carcadiz@hotmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: TQM5200 2.6-denx SM501 voyager enabling problem.
Date: Sat, 08 Mar 2008 02:27:37 +0100 [thread overview]
Message-ID: <20080308012738.0C3D9247AF@gemini.denx.de> (raw)
In-Reply-To: Your message of "Fri, 07 Mar 2008 15:10:07 +0100." <BLU106-W13F58AFC51977B5ACB4318CA130@phx.gbl>
In message <BLU106-W13F58AFC51977B5ACB4318CA130@phx.gbl> you wrote:
>
> I thought about this possible solution (adding resource description to device tree), but as far as I understood, the device tree was intended to describe the microcontroller peripherals and tqm5200, based on the mpc5200 is sold out also without sm501, s
> o that's why I discarded this option.
The device tree describes the hardware, and the TQM5200 (with SM501)
and the TQM5200S (without the SM501) are two different boards and
need different device trees.
And, Pedro - could you please restrict your line length to some 70+
characters or so? Thanks.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
"The greatest warriors are the ones who fight for peace."
- Holly Near
next prev parent reply other threads:[~2008-03-08 1:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-22 11:29 TQM5200 2.6-denx SM501 voyager enabling problem Pedro Luis D. L.
2008-02-28 15:01 ` Martin Krause
2008-02-28 15:31 ` Pedro Luis D. L.
2008-03-06 14:09 ` Pedro Luis D. L.
2008-03-07 12:05 ` Anatolij Gustschin
2008-03-07 14:10 ` Pedro Luis D. L.
2008-03-08 1:27 ` Wolfgang Denk [this message]
2008-03-10 8:38 ` Pedro Luis D. L.
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=20080308012738.0C3D9247AF@gemini.denx.de \
--to=wd@denx.de \
--cc=carcadiz@hotmail.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).