public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] arm: auto gen asm-offsets.h for mb86r0x
Date: Mon, 01 Aug 2011 22:37:02 +0200	[thread overview]
Message-ID: <20110801203702.5481C1208DCF@gemini.denx.de> (raw)
In-Reply-To: <4E36ED80.4050701@arcor.de>

Dear Matthias Weisser,

In message <4E36ED80.4050701@arcor.de> you wrote:
> 
> Would you please consider this patch for inclusion. Currently jadecpu is
> broken since [f456445f29d22bb31ad29fdf1d6b2769decd37a2]. It is not clear
> to me why the referenced patch breaks jadecpu (must be some make
> dependency stuff) but it slipped through my testing as I had applied the
> above patch in an earlier version when submitting the patch which breaks it.
> 
> This patch fixes jadecpu and also gets rid of the hand written
> asm-offsets.h.
> 
> I can't test it (no powerpc toolchain at hand) but the above mentioned
> commit may also break mpc512x based boards. If that is the case
> ./arch/powerpc/cpu/mpc512x/asm-offsets.h should also be autogenerated.
> If this is done we will not have any non-autogenerated asm-offsets.h in
> u-boot anymore.

Which sort of errors should I look for?  Buil errors?  Or run-time
errors?

All MPC512x based boards build fine:

+ ./MAKEALL 512x
Configuring for pdm360ng board...
   text    data     bss     dec     hex filename
 285842   32608   29776  348226   55042 /work/wd/tmp-ppc/u-boot
Configuring for aria board...
   text    data     bss     dec     hex filename
 253515   19760   29464  302739   49e93 /work/wd/tmp-ppc/u-boot
Configuring for mecp5123 board...
   text    data     bss     dec     hex filename
 249391   20244  221024  490659   77ca3 /work/wd/tmp-ppc/u-boot
Configuring for mpc5121ads board...
   text    data     bss     dec     hex filename
 322971   22940  270552  616463   9680f /work/wd/tmp-ppc/u-boot
Configuring for mpc5121ads_rev2 - Board: mpc5121ads, Options: MPC5121ADS_REV2
   text    data     bss     dec     hex filename
 309335   22428  270328  602091   92feb /work/wd/tmp-ppc/u-boot

--------------------- SUMMARY ----------------------------
Boards compiled: 5
----------------------------------------------------------


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
COMPONENT EQUIVALENCY NOTICE:  The  Subatomic  Particles  (Electrons,
Protons,  etc.) Comprising This Product Are Exactly the Same in Every
Measurable Respect as Those Used in the Products of Other  Manufactu-
rers,  and  No Claim to the Contrary May Legitimately Be Expressed or
Implied.

  parent reply	other threads:[~2011-08-01 20:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-04  7:17 [U-Boot] [PATCH] arm: auto gen asm-offsets.h for mb86r0x Matthias Weisser
2011-08-01 15:11 ` [U-Boot] [PATCH v2] " Matthias Weisser
2011-08-01 18:16   ` Matthias Weisser
2011-08-01 19:47     ` Albert ARIBAUD
2011-08-01 20:37     ` Wolfgang Denk [this message]
2011-08-04 11:58   ` Albert ARIBAUD

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=20110801203702.5481C1208DCF@gemini.denx.de \
    --to=wd@denx.de \
    --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