public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3] MX28: Add u-boot.mx28.sd and u-boot.mx28.nand make targets
Date: Fri, 22 Jun 2012 14:44:46 +0200	[thread overview]
Message-ID: <201206221444.46242.marex@denx.de> (raw)
In-Reply-To: <20120621203115.BF33E202253@gemini.denx.de>

Dear Wolfgang Denk,

> Dear Marek Vasut,
> 
> In message <201205231422.17293.marex@denx.de> you wrote:
> > > What would be wrong if all boards would use the same
> > > "u-boot.bin.sdcard" target name?
> > 
> > That such file (u-boot.bin.sdcard) would be generated by a different tool
> > for each different board, unlike u-boot.bin . Maybe I'm just flat
> > missing something here.
> 
> Who cares which tool is building the image?  or why would this matter?

I think we're missing each others point. So, lemme put it this way:

We have CPU X, which uses sequence of commands, sequence A.
We have CPU Y, which uses sequence of commands, sequence B.

We want make target M, which results in file named F.

How do we make sure the target M will result in file F produced by sequence A if 
u-boot is configured for CPU X && file F produced by sequence B if u-boot is 
configured for CPU Y ?

I think I might have already answered myself ... u-boot is configured for CPU 
X/CPU Y, right?

> All we need to know is that "u-boot.bin.sdcard" is an image that can
> be installed on a SDCard to be booted from.
> 
> Best regards,
> 
> Wolfgang Denk

Best regards,
Marek Vasut

  reply	other threads:[~2012-06-22 12:44 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-22 23:32 [U-Boot] [PATCH 1/3] MX28: Add u-boot.mx28.sd and u-boot.mx28.nand make targets Marek Vasut
2012-05-22 23:32 ` [U-Boot] [PATCH 2/3] MX28: Cleanup mxsboot within make mrproper Marek Vasut
2012-05-22 23:32 ` [U-Boot] [PATCH 3/3] M28: Disable USB power on boot Marek Vasut
2012-05-23 11:14   ` Wolfgang Denk
2012-05-23 11:53     ` Marek Vasut
2012-05-23 12:48       ` Fabio Estevam
2012-05-23 13:08         ` Marek Vasut
2012-05-23 13:10           ` Fabio Estevam
2012-05-23 13:01   ` Fabio Estevam
2012-05-23 13:07     ` Marek Vasut
2012-05-23 13:15       ` Fabio Estevam
2012-05-23 13:20         ` Marek Vasut
2012-05-23  9:16 ` [U-Boot] [PATCH 1/3] MX28: Add u-boot.mx28.sd and u-boot.mx28.nand make targets Wolfgang Denk
2012-05-23  9:27   ` Marek Vasut
2012-05-23  9:44     ` Marek Vasut
2012-05-23 11:17       ` Wolfgang Denk
2012-05-23 11:34         ` Marek Vasut
2012-05-23 11:47           ` Wolfgang Denk
2012-05-23 12:22             ` Marek Vasut
2012-06-21 20:31               ` Wolfgang Denk
2012-06-22 12:44                 ` Marek Vasut [this message]
2012-06-22 13:11                   ` Wolfgang Denk
2012-05-23 11: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=201206221444.46242.marex@denx.de \
    --to=marex@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