From: Michael Walle <michael@walle.cc>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] lsxl: add support for lschlv2 and lsxhl
Date: Thu, 29 Mar 2012 16:39:18 +0200 [thread overview]
Message-ID: <201203291639.18602.michael@walle.cc> (raw)
In-Reply-To: <F766E4F80769BD478052FB6533FA745D1A2F6FA965@SC-VEXCH4.marvell.com>
Am Donnerstag 29 M?rz 2012, 16:24:23 schrieb Prafulla Wadaskar:
> > -----Original Message-----
> > From: Michael Walle [mailto:michael at walle.cc]
> > Sent: 29 March 2012 18:08
> > To: Prafulla Wadaskar
> > Cc: u-boot at lists.denx.de
> > Subject: Re: [PATCH v2] lsxl: add support for lschlv2 and lsxhl
> >
> > Am Dienstag 27 M?rz 2012, 09:27:49 schrieb Prafulla Wadaskar:
> > > > # diff --git a/board/buffalo/lsxl/config.mk
> > > > b/board/buffalo/lsxl/config.mk new file mode 100644
> > > > index 0000000..062554b
> > > > --- /dev/null
> > > > +++ b/board/buffalo/lsxl/config.mk
> > > > @@ -0,0 +1 @@
> > > > +ALL-y += $(obj)u-boot.kwb
> > >
> > > Pls remove this file
> >
> > Is there another way to build the u-boot.kwb binary by default?
> >
> > The main Makefile states:
> > # Always append ALL so that arch config.mk's can add custom ones
> >
> > and theres a rule for $(obj)u-boot.kwb.
>
> Just pass u-boot.kwm to the make, will do the needful, if this satisfies
> the goal of generating u-boot.kwb, then why to add one file to the source
> code?
- this won't work easily for out-of-tree builds, will it? because you have to
pass $(obj)u-boot.kwb to make and $(obj) is $O which is specified by the user,
so he has to specify it twice
- i'm only interested in the u-boot.kwb, why shouldn't it be generated by
default?
- i can't build it with a sinlge make call. Eg. atm i'm doing
make -j3 -C ../u-boot O=`pwd` CROSS_COMPILE=arm-linux-gnueabi- lschlv2
otherwise i have to do
make -j3 -C ../u-boot O=`pwd` CROSS_COMPILE=arm-linux-gnueabi- lschlv2
make -j3 -C ../u-boot O=`pwd` CROSS_COMPILE=arm-linux-gnueabi- \
`pwd`/u-boot.kwb
Overall, it will greatly simplify thinks :)
--
Michael
next prev parent reply other threads:[~2012-03-29 14:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 15:02 [U-Boot] [PATCH v2] lsxl: add support for lschlv2 and lsxhl Michael Walle
2012-03-26 10:15 ` Michael Walle
2012-03-27 7:27 ` Prafulla Wadaskar
2012-03-27 20:38 ` Michael Walle
2012-03-29 12:38 ` Michael Walle
2012-03-29 14:24 ` Prafulla Wadaskar
2012-03-29 14:39 ` Michael Walle [this message]
2012-03-30 11:18 ` Prafulla Wadaskar
2012-03-30 13:57 ` Michael Walle
2012-04-02 6:37 ` Prafulla Wadaskar
2012-03-27 7:28 ` Prafulla Wadaskar
-- strict thread matches above, loose matches on Subject: below --
2012-03-27 10:51 Michael Walle
2012-03-27 11:05 ` Prafulla Wadaskar
2012-03-27 20:55 ` Michael Walle
2012-03-27 21:13 ` Wolfgang Denk
2012-03-29 11:30 ` Michael Walle
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=201203291639.18602.michael@walle.cc \
--to=michael@walle.cc \
--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