public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V3 3/3] rpi: add support for Raspberry Pi 2 model B
Date: Tue, 17 Feb 2015 15:22:02 -0500	[thread overview]
Message-ID: <20150217202202.GA11752@bill-the-cat> (raw)
In-Reply-To: <54E3980D.5020303@wwwdotorg.org>

On Tue, Feb 17, 2015 at 12:35:41PM -0700, Stephen Warren wrote:
> On 02/16/2015 06:03 PM, Tom Rini wrote:
> >On Mon, Feb 16, 2015 at 12:16:15PM -0700, Stephen Warren wrote:
> >
> >>USB doesn't seem to work yet; the controller detects the on-board Hub/
> >>Ethernet device but can't read the descriptors from it. I haven't
> >>investigated yet.
> >>
> >>Signed-off-by: Stephen Warren <swarren@wwwdotorg.org>
> >>---
> >>v3: Rebased on top of u-boot-dm merge.
> >>v2: Implement new board_rev decoding scheme, to avoid hard-coding the
> >>board revision onthe RPi 2.
> >
> >+(rpi_2) make[3]: *** No rule to make target
> >`arch/arm/cpu/armv7/bcm2835/../../arm1176/bcm2835//init.o', needed by
> >`arch/arm/cpu/armv7/bcm2835/built-in.o'.  Stop.
> >+(rpi_2) make[2]: *** [arch/arm/cpu/armv7/bcm2835] Error 2
> >+(rpi_2) make[1]: *** [arch/arm/cpu/armv7] Error 2
> >
> >When I try and build it with buildman.  Something get left out
> >somewhere?  Thanks!
> 
> I've reproduced this error on my machine at work, where I previously
> worked out the right stuff to put into ~/.buildman.
> 
> Now that I try the regular build process (in-tree build using just
> make) multiple times after a "git clean -f -d -x" , I see the same
> error that way too, sometimes, so it's nothing to do with buildman.
> 
> However, I don't always get the error with either plain make or with
> buildman, and it doesn't always complain about the same file:
> 
> >+make[1]: *** No rule to make target `arch//cpu/u-boot.lds', needed by `u-boot.lds'.  Stop.
> 
> >+make[3]: *** No rule to make target `arch/arm/cpu/armv7/bcm2835/../../arm1176/bcm2835//init.o', needed by `arch/arm/cpu/armv7/bcm2835/built-in.o'.  Stop.
> 
> This isn't anything to do with these patches; I can see the exact
> same issue building the following existing boards in unmodified
> u-boot/master:
> 
> rpi (arm1176, no SPL)
> tnetv107x_evm_defconfigs (arm1176 no SPL)
> mx35pdk_defconfig (arm1136, no SPL)
> nhk8815_defconfig (arm926ejs, no SPL)
> imx27lite_defconfig (arm926ejs, SPL)
> vexpress_ca15_tc2_defconfig (ARMv7, no SPL)
> 
> Strangely I don't see the issue for:
> 
> seaboard (ARMv7, SPL)
> maxbcm_defconfig (ARMv7, SPL)
> 
> I wonder if bisecting would show up where this issue was introduced.

I bet it will and I bet it's when we switch to Kconfig.  Masahiro, any
ideas?

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20150217/8893be97/attachment.sig>

  reply	other threads:[~2015-02-17 20:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-16 19:16 [U-Boot] [PATCH V3 1/3] bcm2835/rpi: add SPDX license tags for some files Stephen Warren
2015-02-16 19:16 ` [U-Boot] [PATCH V3 2/3] bcm2836 SoC support (used in Raspberry Pi 2 model B) Stephen Warren
2015-02-22  2:57   ` Tom Rini
2015-02-16 19:16 ` [U-Boot] [PATCH V3 3/3] rpi: add support for Raspberry Pi 2 model B Stephen Warren
2015-02-17  1:03   ` Tom Rini
2015-02-17  4:09     ` Stephen Warren
2015-02-17  4:15       ` Simon Glass
2015-02-17  4:19         ` Stephen Warren
2015-02-18  2:39           ` Simon Glass
2015-02-17 19:35     ` Stephen Warren
2015-02-17 20:22       ` Tom Rini [this message]
2015-02-19  6:00         ` Stephen Warren
2015-02-19  8:50           ` Masahiro Yamada
2015-02-19 12:18             ` Tom Rini
2015-03-24 15:36             ` Stephen Warren
2015-02-22  2:57   ` Tom Rini
2015-02-22  2:57 ` [U-Boot] [PATCH V3 1/3] bcm2835/rpi: add SPDX license tags for some files Tom Rini

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=20150217202202.GA11752@bill-the-cat \
    --to=trini@ti.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