From: Sughosh Ganu <urwithsughosh@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] Changes to move hawkboard to the new infrastructure.
Date: Tue, 10 Jan 2012 15:43:18 +0530 [thread overview]
Message-ID: <20120110101318.GA9123@Hardy> (raw)
In-Reply-To: <4F0C07F0.9090003@denx.de>
hi Heiko,
On Tue Jan 10, 2012 at 10:42:08AM +0100, Heiko Schocher wrote:
> Hello Sughosh, Christian, Tom,
>
> Sughosh Ganu wrote:
> >>> I see a CONFIG_MACH_DAVINCI_* like define in da850evm.h and
> >>> hawkboard.h. Should i add a similar define for cam_enc_4xx, and use
> >>> these instead.
> >> Actually the problem is that now we have a board specific file
> >> (hawkboard_nand_spl.c) in the arch tree. Hawkboard has a DA850 SoC so if we
> >> have a da850_spl.c hawkboard should either use it as well, or we make the
> >> *spl.c files board specific and put them into the board tree.
> >
> > I'd vote for moving the *spl.c files to their corresponding board
> > directories -- infact hawkboard_nand_spl.c was earlier under it's
> > board directory. This i think keeps the implementation clean, avoids
> > the risk of breakage, and also makes it simpler for any newer board
> > in the same soc family migrating to spl, which i think might
> > increase the ifdeffery.
>
> Hmm.. I vote against creating board specific files. I am here in line
> with Christians proposal, posted here:
>
> http://lists.denx.de/pipermail/u-boot/2012-January/115166.html
>
> Did this work for the hawkboard? If you do not need some inits, maybe
> we add here defines or better make this functions weak, and you can write
> board specific functions for this parts. The code in board_init_r()
> is only a "selection" from where to load u-boot, which I think in the
> long term could be made more common for other SoCs too ... so I want
> to prevent to split this in board specific files.
I should be able to test these changes in the evening. Will send a
modified patch after testing.
-sughosh
next prev parent reply other threads:[~2012-01-10 10:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 18:28 [U-Boot] [PATCH 2/2] Changes to move hawkboard to the new infrastructure Sughosh Ganu
2012-01-09 23:30 ` Tom Rini
2012-01-10 6:30 ` Sughosh Ganu
2012-01-10 8:15 ` Christian Riesch
2012-01-10 8:42 ` Sughosh Ganu
2012-01-10 9:42 ` Heiko Schocher
2012-01-10 10:13 ` Sughosh Ganu [this message]
2012-01-10 18:15 ` [U-Boot] [PATCH 2/2 V2] Changes to move hawkboard to the new spl infrastructure Sughosh Ganu
2012-01-11 6:52 ` Heiko Schocher
2012-01-11 7:53 ` Sughosh Ganu
2012-01-11 8:54 ` Christian Riesch
2012-01-11 9:17 ` Christian Riesch
2012-01-11 9:40 ` Heiko Schocher
2012-01-11 14:37 ` [U-Boot] [PATCH 2/2 V3] " Sughosh Ganu
2012-01-11 16:10 ` Christian Riesch
2012-01-11 17:03 ` [U-Boot] [PATCH 2/2 V4] " Sughosh Ganu
2012-01-12 7:24 ` Heiko Schocher
2012-01-12 7:30 ` Sughosh Ganu
2012-01-12 7:32 ` Christian Riesch
2012-01-12 9:02 ` Christian Riesch
2012-01-12 9:39 ` Sughosh Ganu
2012-01-12 11:19 ` Christian Riesch
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=20120110101318.GA9123@Hardy \
--to=urwithsughosh@gmail.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