On 11/30/11 20:11, Josh Boyer wrote:
On Mon, Nov 28, 2011 at 5:59 PM, Scott Woodscottw...@freescale.com wrote:
On 11/23/2011 10:47 AM, Josh Boyer wrote:
On Mon, Nov 14, 2011 at 12:41 AM, Suzuki K. Poulosesuz...@in.ibm.com wrote:
The current implementation of CONFIG_RELOCATABLE in BookE is
On Wed, Dec 7, 2011 at 7:40 AM, Suzuki Poulose suz...@in.ibm.com wrote:
Josh,
I rebased my patches to 3.2.0-rc3 and was able to verify it on my QEMU
setup.
However I am facing problems getting the my boards booted with the network
cards
(even without the patches). Here is what I see :
On Mon, Nov 28, 2011 at 5:59 PM, Scott Wood scottw...@freescale.com wrote:
On 11/23/2011 10:47 AM, Josh Boyer wrote:
On Mon, Nov 14, 2011 at 12:41 AM, Suzuki K. Poulose suz...@in.ibm.com
wrote:
The current implementation of CONFIG_RELOCATABLE in BookE is based
on mapping the page aligned
On 11/23/2011 10:47 AM, Josh Boyer wrote:
On Mon, Nov 14, 2011 at 12:41 AM, Suzuki K. Poulose suz...@in.ibm.com wrote:
The current implementation of CONFIG_RELOCATABLE in BookE is based
on mapping the page aligned kernel load address to KERNELBASE. This
approach however is not enough for
On Mon, Nov 14, 2011 at 12:41 AM, Suzuki K. Poulose suz...@in.ibm.com wrote:
The current implementation of CONFIG_RELOCATABLE in BookE is based
on mapping the page aligned kernel load address to KERNELBASE. This
approach however is not enough for platforms, where the TLB page size
is large
The current implementation of CONFIG_RELOCATABLE in BookE is based
on mapping the page aligned kernel load address to KERNELBASE. This
approach however is not enough for platforms, where the TLB page size
is large (e.g, 256M on 44x). So we are renaming the RELOCATABLE used
currently in BookE to
