public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Loïc Minier" <lool@dooz.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] Improve default "make" targets (ALL-y)
Date: Fri, 11 Nov 2011 14:41:46 +0100	[thread overview]
Message-ID: <20111111134146.GD2895@bee.dooz.org> (raw)
In-Reply-To: <CA+M6bXmsoxCvd55DhhdfS0mOanupOkWcohCKyOA7ss4Tiwa02Q@mail.gmail.com>

On Thu, Nov 10, 2011, Tom Rini wrote:
> Any omap3/omap4/omap5/am335x where you generate MLO you want
> u-boot.img rather than u-boot.bin, even for panda iirc.

 Thanks for the hint; I'll follow that rule for OMAP3/OMAP4 boards we
 build in Debian ATM; Aneesh pointed at the Makefile snippet which adds
 u-boot.img on omap3 and omap4 platforms, sounds good to me.

 There are other architectures where it's less obvious:

Debian architecture     board           target
----------------------------------------------
avr32                   hammerhead      u-boot.img
i386                    eNET            u-boot.bin
mipsel                  dbau1100        u-boot.img
mips                    qemu_mips       u-boot.img
powerpc                 ZUMA            u-boot.img
sh4                     r2dplus         u-boot.img
sh4                     sh7785lcr_32bit u-boot.img
sparc                   gr_xc3s_1500    u-boot.img

 I didn't check for each of the single boards above, I wonder whether I
 can tell from the u-boot source code (if it's correct) whether indeed
 u-boot.img or u-boot.bin is the correct binary to ship for that board.

 [ Ideally, "make" would also build the right one, or perhaps "make
 install" or some other special target which represents the final
 deliverables for that board. ]

-- 
Lo?c Minier

  reply	other threads:[~2011-11-11 13:41 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-10 13:49 [U-Boot] Improve default "make" targets (ALL-y) Loïc Minier
2011-11-10 13:49 ` [U-Boot] [PATCH 1/2] Build u-boot.imx by default when board uses it Loïc Minier
2011-11-10 15:35   ` Stefano Babic
2011-11-10 23:24   ` Mike Frysinger
2011-11-10 23:45     ` Loïc Minier
2011-11-11  1:51       ` Mike Frysinger
2011-11-11  3:39         ` Aneesh V
2011-11-11 13:31           ` Loïc Minier
2011-11-11 13:35         ` Loïc Minier
2011-11-11 16:43           ` Mike Frysinger
2011-11-17  7:07           ` Stefano Babic
2011-11-17  7:37           ` Wolfgang Denk
2011-11-11  2:29       ` Daniel Schwierzeck
2011-11-11 13:26         ` Loïc Minier
2012-04-02 17:03           ` Stefano Babic
2012-04-02 18:25             ` Mike Frysinger
2012-04-03 14:22               ` Stefano Babic
2011-11-10 13:49 ` [U-Boot] [PATCH 2/2] Build u-boot.kwb " Loïc Minier
2011-11-10 14:54 ` [U-Boot] Improve default "make" targets (ALL-y) Tom Rini
2011-11-11 13:41   ` Loïc Minier [this message]
2011-11-11 16:41     ` Mike Frysinger
2011-11-11 21:01       ` Loïc Minier
2011-11-11 22:50         ` Mike Frysinger

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=20111111134146.GD2895@bee.dooz.org \
    --to=lool@dooz.org \
    --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