From: Peter Bergner <bergner@vnet.ibm.com>
To: Santosh Kumar <santoshkumar.a@gmail.com>
Cc: Michael Neuling <mikey@neuling.org>,
Ian Munsie <ianmunsi@au1.ibm.com>,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: powerpc 476, Little-endian, pte fault
Date: Tue, 01 Nov 2011 13:44:53 -0500 [thread overview]
Message-ID: <1320173093.2996.244.camel@otta> (raw)
In-Reply-To: <CAJw04pA3mDOgHrOvPxeXR8Fw6Jn1kBz9qSrgq2vJ7HPpyQwSbg@mail.gmail.com>
On Tue, 2011-11-01 at 22:44 +0530, Santosh Kumar wrote:
> I had a problem configuring the GCC for 476 in little endian mode,
What type of problem? I assume the binutils you are building
against has 476 support too, correct? You'll need that.
> So is this PTE fault related to the compiler options?
This could be caused by anything, but I highly doubt this is
caused by a compiler option issue. My $$ are that you either
have a bug in your kernel patch or there are more places in
the kernel source that need patching.
Peter
WARNING: multiple messages have this Message-ID (diff)
From: Peter Bergner <bergner@vnet.ibm.com>
To: Santosh Kumar <santoshkumar.a@gmail.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linuxppc-dev@ozlabs.org, Michael Neuling <mikey@neuling.org>,
Ian Munsie <ianmunsi@au1.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: powerpc 476, Little-endian, pte fault
Date: Tue, 01 Nov 2011 13:44:53 -0500 [thread overview]
Message-ID: <1320173093.2996.244.camel@otta> (raw)
In-Reply-To: <CAJw04pA3mDOgHrOvPxeXR8Fw6Jn1kBz9qSrgq2vJ7HPpyQwSbg@mail.gmail.com>
On Tue, 2011-11-01 at 22:44 +0530, Santosh Kumar wrote:
> I had a problem configuring the GCC for 476 in little endian mode,
What type of problem? I assume the binutils you are building
against has 476 support too, correct? You'll need that.
> So is this PTE fault related to the compiler options?
This could be caused by anything, but I highly doubt this is
caused by a compiler option issue. My $$ are that you either
have a bug in your kernel patch or there are more places in
the kernel source that need patching.
Peter
next prev parent reply other threads:[~2011-11-01 18:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-31 5:30 powerpc 476, Little-endian, pte fault Santosh Kumar
2011-10-31 5:51 ` Michael Neuling
2011-10-31 5:51 ` Michael Neuling
2011-10-31 6:35 ` Santosh Kumar
2011-10-31 7:38 ` Santosh Kumar
2011-10-31 7:38 ` Santosh Kumar
2011-10-31 9:49 ` Michael Neuling
2011-10-31 9:49 ` Michael Neuling
2011-10-31 11:23 ` Benjamin Herrenschmidt
2011-10-31 11:23 ` Benjamin Herrenschmidt
2011-11-01 3:02 ` Santosh Kumar
2011-11-01 3:02 ` Santosh Kumar
2011-11-01 13:44 ` Peter Bergner
2011-11-01 13:44 ` Peter Bergner
2011-11-01 17:14 ` Santosh Kumar
2011-11-01 17:14 ` Santosh Kumar
2011-11-01 18:44 ` Peter Bergner [this message]
2011-11-01 18:44 ` Peter Bergner
2011-10-31 7:48 ` Shan Hai
2011-10-31 9:17 ` Santosh Kumar
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=1320173093.2996.244.camel@otta \
--to=bergner@vnet.ibm.com \
--cc=ianmunsi@au1.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mikey@neuling.org \
--cc=santoshkumar.a@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.