From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] PowerPC Build Problem
Date: Wed, 4 Sep 2013 09:54:35 +0200 [thread overview]
Message-ID: <20130904095435.2c1c78fc@skate> (raw)
In-Reply-To: <52268480.1000606@rftechnology.com.au>
Dear Jason Rennie,
On Wed, 04 Sep 2013 10:53:20 +1000, Jason Rennie wrote:
> I apologise if the question is inappropriate for this list but I know
> everyone here is knowledgeable and you were very helpful last time
> when I was having problems getting things to start and it turned out
> to be an issue with the device tree.
>
> I'm using buildroot to build for an APC8272ADS chip with Intel/Sharp
> Memory chips on board. That build of the kernel does appear to work
> correctly the relevant portion is
[...]
> But when I try building it with the latest buildroot (2013.08) and I
> configure the kernel (3.10.10) I get one of two things. If I don't
> include specific settings to physmap then I get a kernel panic when
> it can't mount the root filesystem as follows
From what you're telling us, it really looks like a kernel problem
(either a configuration one, or a real problem in the kernel code).
Since you're able to use a recent version of the kernel (3.10), it
means that you can easily benefit from support from the kernel
community. I would therefore recommend you to get in touch with the
PowerPC kernel developers doing the support for this board/SoC and
asking the question there.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2013-09-04 7:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 0:53 [Buildroot] PowerPC Build Problem Jason Rennie
2013-09-04 7:54 ` Thomas Petazzoni [this message]
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=20130904095435.2c1c78fc@skate \
--to=thomas.petazzoni@free-electrons.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