From: Michael Neuling <mikey@neuling.org>
To: Santosh Kumar <santoshkumar.a@gmail.com>
Cc: linuxppc-dev@ozlabs.org, Ian Munsie <ianmunsi@au1.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: powerpc 476, Little-endian, pte fault
Date: Mon, 31 Oct 2011 20:49:48 +1100 [thread overview]
Message-ID: <20440.1320054588@neuling.org> (raw)
In-Reply-To: <CAJw04pAh5QDQMkUHbj9=rRPiUCZejimHiydCJFMAoZeSd_ydhA@mail.gmail.com>
> I have built a cross compiler for ppc440 in little endian mode and
> using it to build the kernel.
>
> Yes i am running Linux in Little-Endian. This is the first user space
> process. I wrote the below program and running it as init from
> /sbin/init. I have also set the permissions with chmod +s.
>
> main()
> {
>
> while(1){
> printf("hello world");
> sleep(1);
> }
> }
Does libc even support little endian on PPC?
> I have attached the patch.
This is a pretty huge patch:
115 files changed, 44479 insertions(+), 7398 deletions(-)
It seems to include a new platform as well as a bunch of unrelated junk.
I suggest you need to break this down into something more digestible.
Like remove all the junk in the patch. Then add the support for the new
platform (invader? platform). Then start looking at little endian.
Unless you do this, it's unlikely anyone here is going to be able to
help.
When you get to the little endian work, you might want to take a look at
this patch series from Ian Munsie:
http://lists.ozlabs.org/pipermail/linuxppc-dev/2010-October/086165.html
Mikey
next prev parent reply other threads:[~2011-10-31 9:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJw04pD24W_nGSLheWunCa_o7QqBmRf_TSAD44EkzazigRe_nQ@mail.gmail.com>
2011-10-31 5:51 ` powerpc 476, Little-endian, pte fault Michael Neuling
2011-10-31 6:35 ` Santosh Kumar
2011-10-31 7:38 ` Santosh Kumar
2011-10-31 9:49 ` Michael Neuling [this message]
2011-10-31 11:23 ` Benjamin Herrenschmidt
2011-11-01 3:02 ` Santosh Kumar
2011-11-01 13:44 ` Peter Bergner
2011-11-01 17:14 ` Santosh Kumar
2011-11-01 18:44 ` Peter Bergner
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=20440.1320054588@neuling.org \
--to=mikey@neuling.org \
--cc=ianmunsi@au1.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).