public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Allen Martin <amartin@nvidia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] MAKEALL: fix ARM board lists
Date: Wed, 29 Aug 2012 13:54:07 -0700	[thread overview]
Message-ID: <20120829205407.GG9587@nvidia.com> (raw)
In-Reply-To: <20120829201339.GF9587@nvidia.com>

On Wed, Aug 29, 2012 at 01:13:39PM -0700, Allen Martin wrote:
> On Wed, Aug 29, 2012 at 01:03:40PM -0700, Tom Rini wrote:
> > On 08/29/2012 12:13 PM, Allen Martin wrote:
> > > The LIST_arm rule included the Atmel boards twice (by virtue of
> > > including both LIST_at91 and LIST_ARM9) and was missing all the
> > > arm720t, arm946es, and arm1176 boards.  Change this list to use
> > > boards_by_arch() which is less error prone.  After this change
> > > "./MAKEALL arm" and "./MAKEALL -a arm" build the same boards.
> > > 
> > > Also add the missing arm946es and arm1176 processors to the ARM9
> > > and ARM11 lists respectively and add an ARM7 list for the arm720t
> > > processor.
> > 
> > Good find!  Would you mind looking quickly over the other arches to see
> > if they have any similar but now obvious problems (where LIST_${ARCH}
> > doesn't use boards_by_arch)) ?   Thanks!
> > 
> > -- 
> > Tom
> 
> By experiment it look like m68k and mips have problems too, I'll investigate:
> 

It looks like mips splits out the little endian boards into a virtual
"mips_el" architecture that doesn't actually exist in boardfs.cfg, so
maybe I won't touch that.  I founds some other missing/duplicate
boards in mips and m68k though so I'll add those to the patch.

-Allen
-- 
nvpublic

      reply	other threads:[~2012-08-29 20:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-29 19:13 [U-Boot] [PATCH] MAKEALL: fix ARM board lists Allen Martin
2012-08-29 20:03 ` Tom Rini
2012-08-29 20:13   ` Allen Martin
2012-08-29 20:54     ` Allen Martin [this message]

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=20120829205407.GG9587@nvidia.com \
    --to=amartin@nvidia.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