Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Building for Raspberry Pi on Pi (in Ubuntu WSL same is working)
Date: Tue, 25 Aug 2020 09:49:42 +0200	[thread overview]
Message-ID: <20200825094942.3c865b79@windsurf.home> (raw)
In-Reply-To: <VI1PR03MB452849E1179528B11527FB1A98570@VI1PR03MB4528.eurprd03.prod.outlook.com>

Hello,

On Tue, 25 Aug 2020 07:43:06 +0000
Marie Maurer <marie.maurer@pixida.de> wrote:

> it is a Raspberry Pi Compute Module 3 Plus. This is the output during startup:
> 
> [    0.000000] Booting Linux on physical CPU 0x0
> [    0.000000] Linux version 5.4.51-v7+ (dom at buildbot) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611)) #1333 SMP Mon Aug 10 16:4
> 5:19 BST 2020
> [    0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d
> [    0.000000] CPU: div instructions available: patching division code
> [    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
> [    0.000000] OF: fdt: Machine model: Raspberry Pi Compute Module 3 Plus Rev 1.0
> [    0.000000] Memory policy: Data cache writealloc
> [    0.000000] Reserved memory: created CMA memory pool at 0x37400000, size 64 MiB
> [    0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
> [    0.000000] On node 0 totalpages: 242688
> [    0.000000]   Normal zone: 2133 pages used for memmap
> [    0.000000]   Normal zone: 0 pages reserved
> [    0.000000]   Normal zone: 242688 pages, LIFO batch:63
> [    0.000000] percpu: Embedded 20 pages/cpu s49856 r8192 d23872 u81920
> [    0.000000] pcpu-alloc: s49856 r8192 d23872 u81920 alloc=20*4096
> [    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
> 
> pi at raspberrypi:~/buildroot/buildroot-2020.08-rc1 $ uname -a
> Linux raspberrypi 5.4.51-v7+ #1333 SMP Mon Aug 10 16:45:19 BST 2020 armv7l GNU/Linux

OK, this is really an ARMv7 system. Could you also provide the output
of "gcc -v" on this platform ?

> First it was just a mistake, I took the wrong windows to compile buildroot
> and thought if this is the only bug, it is worth reporting.

I think in general there is no reason for Buildroot to not work on
non-x86 systems. We even used to have an autobuilder running on a
PowerPC64 system. However, since using Buildroot on non-x86 systems is
not that common, it is pretty likely that there will be a few issues
here and there, like you're experiencing.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2020-08-25  7:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-24 14:09 [Buildroot] Building for Raspberry Pi on Pi (in Ubuntu WSL same is working) Marie Maurer
2020-08-24 17:40 ` Aaron Dewes
2020-08-24 20:19 ` Thomas Petazzoni
2020-08-25  7:18   ` Marie Maurer
2020-08-25  7:26     ` Marie Maurer
2020-08-25  7:33       ` Thomas Petazzoni
2020-08-25  7:43         ` Marie Maurer
2020-08-25  7:49           ` Thomas Petazzoni [this message]
2020-08-25  7:53             ` Marie Maurer
2020-08-25  7:56               ` Marie Maurer
2020-08-25  8:17                 ` Thomas Petazzoni

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=20200825094942.3c865b79@windsurf.home \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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