From: Peter Tyser <ptyser@xes-inc.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC][PATCH 3/3] Add board support for the eXMeritus HWW-1U-1A devices
Date: Tue, 07 Sep 2010 16:40:27 -0500 [thread overview]
Message-ID: <1283895627.26713.466.camel@petert> (raw)
In-Reply-To: <584AA181-AD90-4093-B791-251C783F65C3@boeing.com>
Hi Kyle,
> On Sep 03, 2010, at 00:00, Peter Tyser wrote:
> >> --- a/Makefile
> >> +++ b/Makefile
> >> @@ -2499,6 +2499,10 @@ P2020DS_36BIT_config \
> >> P2020DS_config: unconfig
> >> @$(MKCONFIG) -t $(@:_config=) P2020DS ppc mpc85xx p2020ds freescale
> >>
> >> +HWW_1U_1A_36BIT_config \
> >> +HWW_1U_1A_config: unconfig
> >> + @$(MKCONFIG) -t $(@:_config=) HWW_1U_1A ppc mpc85xx hww-1u-1a exmeritus
> >> +
> >
> > The new way to add a board is via boards.cfg. You shouldn't need to
> > modify this Makefile.
>
> Is there some appropriate documentation on how boards.cfg is supposed to work?
Not that I'm aware of. Its a relatively recent change to U-Boot.
> The latest u-boot.git still seems to have the P2020DS lines that I referenced in "Makefile", and it has no references at all to "P2020DS" in the "boards.cfg" file.
It looks like the top-level Makefile is still required for boards that
support multiple configs, eg 'make P2020DS_36BIT' will configure U-Boot
to compile a 36-bit addressable U-Boot image while 'make P2020DS' will
configure a 32-bit addressable U-Boot image, but they both use the same
Makefile rule with some fancy parsing. So I guess if you have a need
for both a 32 and 36bit version of U-Boot you'll to modify the Makefile
like your original patch did unfortunately. If you don't need to
support both U-Boot configs, you can go the route of other similar
boards that are only in boards.cfg, eg P4080DS, P1022DS, XPedite5370,
etc.
Best,
Peter
next prev parent reply other threads:[~2010-09-07 21:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 18:24 [U-Boot] [RFC] Board support patches for the eXMeritus HWW-1U-1A devices Kyle Moffett
2010-08-30 18:24 ` [U-Boot] [RFC][PATCH 1/3] DDR2: Support new JEDEC DDR2 SPD 1.3 spec Kyle Moffett
2010-09-03 3:06 ` Peter Tyser
2010-09-03 5:10 ` Kyle Moffett
2010-08-30 18:24 ` [U-Boot] [RFC][PATCH 2/3] e1000: Intel 82571EB: Don't wait for MNG cycle on unmanaged chips Kyle Moffett
2010-09-13 4:18 ` Ben Warren
2010-09-13 4:24 ` Kyle Moffett
2010-09-13 4:28 ` Ben Warren
2010-08-30 18:24 ` [U-Boot] [RFC][PATCH 3/3] Add board support for the eXMeritus HWW-1U-1A devices Kyle Moffett
2010-09-03 4:00 ` Peter Tyser
2010-09-03 5:50 ` Kyle Moffett
2010-09-07 22:09 ` Peter Tyser
2010-09-07 22:50 ` [U-Boot] [RFC][PATCH 3/3] Add board support for the eXMeritusHWW-1U-1A devices Moffett, Kyle D
2010-09-08 3:43 ` Peter Tyser
2010-09-07 21:21 ` [U-Boot] [RFC][PATCH 3/3] Add board support for the eXMeritus HWW-1U-1A devices Moffett, Kyle D
2010-09-07 21:40 ` Peter Tyser [this message]
2010-09-07 21:59 ` Wolfgang Denk
2010-09-07 22:21 ` [U-Boot] [RFC][PATCH 3/3] Add board support for the eXMeritusHWW-1U-1A devices Moffett, Kyle D
-- strict thread matches above, loose matches on Subject: below --
2010-08-13 16:27 [U-Boot] [RFC] Board support patches for the eXMeritus HWW-1U-1A devices Kyle Moffett
2010-08-13 16:28 ` [U-Boot] [RFC][PATCH 3/3] Add board support " Kyle Moffett
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=1283895627.26713.466.camel@petert \
--to=ptyser@xes-inc.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