All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Neuling <mikey@neuling.org>
To: Santosh Kumar <santoshkumar.a@gmail.com>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: powerpc 476, Little-endian, pte fault
Date: Mon, 31 Oct 2011 16:51:16 +1100	[thread overview]
Message-ID: <12144.1320040276@neuling.org> (raw)
In-Reply-To: <CAJw04pD24W_nGSLheWunCa_o7QqBmRf_TSAD44EkzazigRe_nQ@mail.gmail.com>

Adding linuxppc-dev list to the CC

> KERNEL: linux 2.6.39.4
> POWERPC: 476, little endian.
> 
> I am trying to get linux 2.6.39.4 up on PPC 476 i have done done
> Big-endian to little endian Changes in:

Can you explain what you are trying to do in more detail?  What does "i
have done Big-endian to little endian Changes" mean?

> 1) bitops header file.
> 2) while reading the device tree.
> 3) the PTE read/computed in head_32.S
> 4) added E bit in the TLB entries.
> 
> with all the above changes the kernel_init is done but and inited is
> mounted.

Can you post your patch?

Are you trying to boot the kernel in little endian or just run userspace
in little endian?  

> But while spawning init process the kernel continuously hits pte
> faults at address 0x100000fc and never comes out. Please let me know
> where i should be looking into.

Is this the very first userspace instruction?

Mikey

WARNING: multiple messages have this Message-ID (diff)
From: Michael Neuling <mikey@neuling.org>
To: Santosh Kumar <santoshkumar.a@gmail.com>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
	Tony Breeds <tony@bakeyournoodle.com>
Subject: Re: powerpc 476, Little-endian, pte fault
Date: Mon, 31 Oct 2011 16:51:16 +1100	[thread overview]
Message-ID: <12144.1320040276@neuling.org> (raw)
In-Reply-To: <CAJw04pD24W_nGSLheWunCa_o7QqBmRf_TSAD44EkzazigRe_nQ@mail.gmail.com>

Adding linuxppc-dev list to the CC

> KERNEL: linux 2.6.39.4
> POWERPC: 476, little endian.
> 
> I am trying to get linux 2.6.39.4 up on PPC 476 i have done done
> Big-endian to little endian Changes in:

Can you explain what you are trying to do in more detail?  What does "i
have done Big-endian to little endian Changes" mean?

> 1) bitops header file.
> 2) while reading the device tree.
> 3) the PTE read/computed in head_32.S
> 4) added E bit in the TLB entries.
> 
> with all the above changes the kernel_init is done but and inited is
> mounted.

Can you post your patch?

Are you trying to boot the kernel in little endian or just run userspace
in little endian?  

> But while spawning init process the kernel continuously hits pte
> faults at address 0x100000fc and never comes out. Please let me know
> where i should be looking into.

Is this the very first userspace instruction?

Mikey


  reply	other threads:[~2011-10-31  5:51 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 [this message]
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
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=12144.1320040276@neuling.org \
    --to=mikey@neuling.org \
    --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 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.