public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Brian S. Park <brian.park@corelis.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Building u-boot for Walnut board (PPC 405GPr)
Date: Mon, 26 Sep 2011 12:03:16 -0700	[thread overview]
Message-ID: <4E80CC74.1030108@corelis.com> (raw)
In-Reply-To: <20110926184425.E57531407999@gemini.denx.de>

Thank you for the information. I'm just re-learning my way around 
u-boot. I appreciate your comments and pointers. Last time I used 
u-boot, it did not use the current method for configuration and I was 
able to us // to comment stuff out in the configuration header file.

Thank you and you guys rock!

Brian

On 9/26/2011 11:44 AM, Wolfgang Denk wrote:
> Dear "Brian S. Park",
>
> In message<4E80BF3D.8050801@corelis.com>  you wrote:
>> It seems that the tool that generates u-boot.lds does not like // in the
>> header file and putting it in the u-boot.lds file.
> The "tool that generates u-boot.lds" is the standard C preprocessor.
>
> Best regards,
>
> Wolfgang Denk
>


-- 
*Boundary-scan with limited budget, insufficient resources, or tight 
schedules? Try TestGenie! 
<http://www.corelis.com/products-JTAG/TestGenie-Boundary-Scan.htm>*
*Need a JTAG Refresher? Sign Up for a Free Boundary-Scan Training Class 
Today! 
<http://www.corelis.com/education/JTAG_Boundary-Scan_Seminars_and_Training.htm>* 

  reply	other threads:[~2011-09-26 19:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-24  1:11 [U-Boot] Building u-boot for Walnut board (PPC 405GPr) Brian S. Park
2011-09-24 10:05 ` Anatolij Gustschin
2011-09-26 16:20   ` Brian S. Park
2011-09-26 17:54     ` Brian S. Park
2011-09-26 18:06       ` Brian S. Park
2011-09-26 18:44         ` Wolfgang Denk
2011-09-26 19:03           ` Brian S. Park [this message]
2011-09-26 18:42       ` 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=4E80CC74.1030108@corelis.com \
    --to=brian.park@corelis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox