From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V3 3/3] rpi: add support for Raspberry Pi 2 model B
Date: Mon, 16 Feb 2015 21:19:08 -0700 [thread overview]
Message-ID: <54E2C13C.1030203@wwwdotorg.org> (raw)
In-Reply-To: <CAPnjgZ1uzTkENLuwjLQkWRr42zD0p1OcEXqR4U4jYxiD=YHAbA@mail.gmail.com>
On 02/16/2015 09:15 PM, Simon Glass wrote:
> Hi Stephen,
>
> On 16 February 2015 at 21:09, Stephen Warren <swarren@wwwdotorg.org> 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!
>>
>> It works fine for me using make:
>>
>> export CROSS_COMPILE=arm-linux-gnueabi-
>> make ARCH=arm rpi_2_defconfig && make ARCH=arm -j8 -s
>>
>> git status doesn't think I forgot to check anything in. The build
>> works after git clean -f -d -x.
>>
>> I can't remember how to run buildman, and the help text doesn't really
>> clue me in. I guess I'll go wade through the README.
>>
>
> Well worth it :-)
>
> Something like this might work for you:
>
> buildman --fetch-arch arm
> buildman rpi_2
>
> or if you want to build the whole branch:
>
> buildman -b <local_branch> rpi_2
What do I put into ~/.buildman's toolchain section (and why can't it
just automatically pick it up from the CROSS_COMPILE environment
variable)? I usually set CROSS_COMPILE to arm-linux-gnueabi- to point at
Ubuntu's system packaged compiler. However, none of the following works,
since buildman seems to require a compiler that's placed into its own
directory rather than /usr/bin:
[toolchain]
xxx1: /usr/bin/arm-linux-gnueabi-gcc
xxx2: arm-linux-gnueabi-gcc
xxx3: /usr/bin/arm-linux-gnueabi-
xxx4: arm-linux-gnueabi-
xxx5: /usr/bin/arm-linux-gnueabi
xxx6: arm-linux-gnueabi
[swarren at dart u-boot.git]$ ./tools/buildman/buildman --list-tool-chains
Scanning for tool chains
- scanning path '/usr/bin/arm-linux-gnueabi-gcc'
- looking in '/usr/bin/arm-linux-gnueabi-gcc/.'
- looking in '/usr/bin/arm-linux-gnueabi-gcc/bin'
- looking in '/usr/bin/arm-linux-gnueabi-gcc/usr/bin'
- scanning path 'arm-linux-gnueabi-gcc'
- looking in 'arm-linux-gnueabi-gcc/.'
- looking in 'arm-linux-gnueabi-gcc/bin'
- looking in 'arm-linux-gnueabi-gcc/usr/bin'
- scanning path '/usr/bin/arm-linux-gnueabi-'
- looking in '/usr/bin/arm-linux-gnueabi-/.'
- looking in '/usr/bin/arm-linux-gnueabi-/bin'
- looking in '/usr/bin/arm-linux-gnueabi-/usr/bin'
- scanning path 'arm-linux-gnueabi-'
- looking in 'arm-linux-gnueabi-/.'
- looking in 'arm-linux-gnueabi-/bin'
- looking in 'arm-linux-gnueabi-/usr/bin'
- scanning path '/usr/bin/arm-linux-gnueabi'
- looking in '/usr/bin/arm-linux-gnueabi/.'
- looking in '/usr/bin/arm-linux-gnueabi/bin'
- looking in '/usr/bin/arm-linux-gnueabi/usr/bin'
- scanning path 'arm-linux-gnueabi'
- looking in 'arm-linux-gnueabi/.'
- looking in 'arm-linux-gnueabi/bin'
- looking in 'arm-linux-gnueabi/usr/bin'
List of available toolchains (0):
None
I'm not going to download a whole new toolchain just to use a different
build tool. I thought I had this working on my work machine before, but
I have no idea how I had that configured.
next prev parent reply other threads:[~2015-02-17 4:19 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 [this message]
2015-02-18 2:39 ` Simon Glass
2015-02-17 19:35 ` Stephen Warren
2015-02-17 20:22 ` Tom Rini
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=54E2C13C.1030203@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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