public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@nvidia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 6/7] ARM: bcm283x: merge BCM2835/BCM2836 directories into mach-bcm283x
Date: Mon, 16 Mar 2015 22:23:22 -0600	[thread overview]
Message-ID: <5507AC3A.1050200@nvidia.com> (raw)
In-Reply-To: <CAK7LNAQ-v8TrKX+nD3E9Rqyv0wSmM0K35r2Z=HuqMh3J=vGKnw@mail.gmail.com>

On 03/16/2015 09:51 PM, Masahiro Yamada wrote:
> Hi Stephen,
> 
> 
> 
> 2015-03-17 12:39 GMT+09:00 Stephen Warren <swarren@nvidia.com>:
>> On 03/16/2015 04:35 AM, Masahiro Yamada wrote:
>>> BCM2835 (used on Raspberry Pi) and BCM2836 (used on Raspberry Pi 2)
>>> are similar enough.  One of the biggest differences is the ARM
>>> processor.  It is reasonable to collect the source files into a
>>> single place, arch/arm/mach-bcm283x/.
>>
>>> diff --git a/arch/arm/cpu/arm1176/bcm2835/Makefile b/arch/arm/mach-bcm283x/Makefile
>>
>>> -obj-y        := lowlevel_init.o
>>> +obj-$(CONFIG_TARGET_RPI) += lowlevel_init.o
>>>  obj-y        += init.o reset.o timer.o mbox.o
>>
>> Why is only one file conditional; shouldn't they all be either -y or
>> -$(CONFIG_TARGET_RPI)?
> 
> This patch just moves source files, not changing the behavior.
> 
> If you see arch/arm/cpu/armv7/bcm2835/Makefile (it is added by you),
> 
> --------------->8------------------
> src_dir := ../../arm1176/bcm2835/
> 
> obj-y   :=
> obj-y   += $(src_dir)/init.o
> obj-y   += $(src_dir)/reset.o
> obj-y   += $(src_dir)/timer.o
> obj-y   += $(src_dir)/mbox.o
> --------------8<------------------
> 
> 
> BCM2836 borrows source files from BCM2835, except lowlevel_init.S.
> 
> I intended to reflect the same behavior.
> 
> Anyway, lowlevel_init is not linked for Raspberry Pi2
> because you added CONFIG_SKIP_LOWLEVEL_INIT to include/configs/rpi_2.h

OK, that makes sense. But, shouldn't the bcm2835-specific file be left
in its existing location rather than putting it into a common location
when it isn't common?

  reply	other threads:[~2015-03-17  4:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-16 10:35 [U-Boot] [PATCH 0/7] Some improvements related to build system Masahiro Yamada
2015-03-16 10:35 ` [U-Boot] [PATCH 1/7] generic-board: move __HAVE_ARCH_GENERIC_BOARD to Kconfig Masahiro Yamada
2015-03-16 10:35 ` [U-Boot] [PATCH 2/7] generic-board: select SYS_GENERIC_BOARD for some architectures Masahiro Yamada
2015-03-16 10:35 ` [U-Boot] [PATCH 3/7] m68k: remove arch board.c Masahiro Yamada
2015-03-16 10:35 ` [U-Boot] [PATCH 4/7] malloc_f: remove redundant defalut values of CONFIG_SYS_MALLOC_F_LEN Masahiro Yamada
2015-03-16 10:35 ` [U-Boot] [PATCH 5/7] malloc_f: enable SYS_MALLOC_F by default if DM is on Masahiro Yamada
2015-03-16 10:35 ` [U-Boot] [PATCH 6/7] ARM: bcm283x: merge BCM2835/BCM2836 directories into mach-bcm283x Masahiro Yamada
2015-03-17  3:39   ` Stephen Warren
2015-03-17  3:51     ` Masahiro Yamada
2015-03-17  4:23       ` Stephen Warren [this message]
2015-03-17  6:11         ` Masahiro Yamada
2015-03-16 10:35 ` [U-Boot] [PATCH 7/7] ARM: bcm283x: move SoC headers to mach-bcm283x/include/mach Masahiro Yamada
2015-03-17  3:42   ` Stephen Warren

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=5507AC3A.1050200@nvidia.com \
    --to=swarren@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