From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4 00/29] zynq: More boards support
Date: Wed, 8 Jan 2014 20:34:15 +0100 [thread overview]
Message-ID: <20140108203415.4eca59af@lilith> (raw)
In-Reply-To: <CAD6G_RSBnNr5aDk9bSP=9Bi6aMriDp7NaHPi7=spRauk_20sTQ@mail.gmail.com>
Hi Jagan,
On Wed, 8 Jan 2014 22:57:10 +0530, Jagan Teki
<jagannadh.teki@gmail.com> wrote:
> Hi Albert,
>
> On Wed, Jan 8, 2014 at 10:44 PM, Albert ARIBAUD
> <albert.u.boot@aribaud.net> wrote:
> > Hi Jagannadha,
> >
> > On Wed, 8 Jan 2014 15:53:07 +0530, Jagannadha Sutradharudu Teki
> > <jagannadha.sutradharudu-teki@xilinx.com> wrote:
> >
> >> These changes are from u-boot-xlnx.git repo from git.xilinx.com
> >> and in addition of basic fdt support. This repo is well tested
> >> on xilinx zynq platform, hence pushing the same on upstream.
> >>
> >> Excluded qspi and nand changes from previous series.
> >>
> >> Please note that all this series available in u-boot-spi.git/master-xlnx
> >> repo.
> >>
> >> --
> >> Thanks,
> >> Jagan.
> >>
> >> Changes for v4:
> >> - rebase to master
> >> - Removed CONFIG_SYS_NO_FLASH in zynq-common.h
> >
> > As the series was rebased tu u-boot/master, not u-boot-arm/master,
> > all patches adding board support failed to apply properly due to
> > boards.cfg differences.
> Yes - I saw this i'll rebase your u-boot-arm/master then.
>
> >
> > I did resolve these manually, but at build-test time, all Zynq boards
> > failed with "Makefile:11: *** Please define CONFIG_DEFAULT_DEVICE_TREE
> > in your board header file. Stop." -- and were the only ones to do so.
> Actually build will successful when you give the dts at runtime while
> building u-boot like Linux style.
> $ make DEVICE_TREE=<dts_file_name>
> ex: make DEVICE_TREE=zynq-zc702
>
> This is the reason I am not defining this on individual pre-board configs.
> I guess this could be fine, please comment.
Boards in U-Boot are expected to build with commands
make <board>_config
make
or with
./MAKEALL <board>
I am therefore not fine with a board which fails when built as above.
Instead of explicitly specifying a DT in the build command line, just
make this DT the default one, by following the advice in the error
message above, and putting it in the config header files. Each board
can (and will, I assume) have its own default DT.
This way, building the board by default will wok, an you will still
be able to override the default DT by specifying a different one on the
command line if you so wish or need.
Amicalement,
--
Albert.
next prev parent reply other threads:[~2014-01-08 19:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 10:23 [U-Boot] [PATCH v4 00/29] zynq: More boards support Jagannadha Sutradharudu Teki
2014-01-08 17:14 ` Albert ARIBAUD
2014-01-08 17:27 ` Jagan Teki
2014-01-08 19:34 ` Albert ARIBAUD [this message]
2014-01-08 19:39 ` Albert ARIBAUD
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=20140108203415.4eca59af@lilith \
--to=albert.u.boot@aribaud.net \
--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