All of lore.kernel.org
 help / color / mirror / Atom feed
From: JEW-DONG <jewdongkuo_1999@yahoo.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Which U-Boot releases have Device Tree support
Date: Wed, 20 May 2009 11:49:31 -0700 (PDT)	[thread overview]
Message-ID: <23641282.post@talk.nabble.com> (raw)
In-Reply-To: <20090409055236.50B1984C4323@gemini.denx.de>


Hi,

I am new to Linux uboot.  I have also purchased a MPC8360E-RDK.  There is no
uboot source code on the CodeWarrior CD either.  The LTIB
(ltib-mpc8360-com-express-20080709) I downloaded from www.logicpd.com does
not have source code for uboot either.  It comes with a uboot image though. 
I can build kernel image (uImage) and jfss2 file system.  I will very
appreciate if you  can show me where to get the uboot source code and how to
build it for my MPC8360E-RDK board.

Thank you very much!
Jew-Dong


wd wrote:
> 
> Dear Peter Barada,
> 
> In message <1239250418.4414.72.camel@blackhole> you wrote:
>> On Wed, 2009-04-08 at 22:40 -0400, cmfairfa at rockwellcollins.com wrote:
>> > We bought a MPC8360E-RDK development kit to develop applications under 
>> > MontaVista CGE5.0. We were toldby the consultant whose doing our board
>> LSP 
>> > that the U-Boot version that came with the development kit did not have 
>> > device tree support. The consultant upgraded the U-Boot to a version
>> that 
>> > has device tree support, but he says he doesn't have the source code
>> for 
>> > the U-Boot version. I need the source to make certain updates.
>> > 
>> > Which U-Boot version can I download that has device tree support?
>> 
>> If you've registered your MPC8360E-RDK with Logic, you should be able to
>> login to the Logic website and download the entire LTIB source that
>> includes a version of u-boot with full source/patches that fully support
>> dealing with device tree binary (dtb) files, and also includes a kernel
>> for the MPC8360E-RDK, and the build process generates an appropriate
>> device tree binary for the board...
> 
> On the other hand there is zero reason to stick with such an
> out-of-tree port when the board is supported in mainline.
> 
> 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 at denx.de
> Conquest is easy. Control is not.
> 	-- Kirk, "Mirror, Mirror", stardate unknown
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
> 
> 

-- 
View this message in context: http://www.nabble.com/-U-Boot--Which-U-Boot-releases-have-Device-Tree-support-tp22963537p23641282.html
Sent from the Uboot - Users mailing list archive at Nabble.com.

  reply	other threads:[~2009-05-20 18:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-09  2:40 [U-Boot] Which U-Boot releases have Device Tree support cmfairfa at rockwellcollins.com
2009-04-09  3:03 ` Jerry Van Baren
2009-04-09  4:13 ` Peter Barada
2009-04-09  4:25   ` Kumar Gala
2009-04-09  5:52   ` Wolfgang Denk
2009-05-20 18:49     ` JEW-DONG [this message]
2009-05-20 18:55       ` Wolfgang Denk
2009-05-20 23:18       ` JEW-DONG
2009-05-21  7:16         ` Wolfgang Denk

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=23641282.post@talk.nabble.com \
    --to=jewdongkuo_1999@yahoo.com \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.