On 06/16/11 19:44, Michal Simek wrote:
Changes:
- Find out address where kernel runs
- Create the first 256MB TLB from online detected address
Limitations:
- Kernel must be aligned to 256MB
Backport:
- Changes in page.h are backported from newer kernel version
mmu_mapin_ram function has to
Hi,
John mentioned in his email that we have some patches.
I am also sending them [patch 1/7-6/7]. It is support for non zero
boot address for ppc44x.
Patch 7/7 is relocatable support for ppc44x.
All patches are against 2.6.31.13 but it shouldn't be big problem
to port them to the latest and
Changes:
- Find out address where kernel runs
- Create the first 256MB TLB from online detected address
Limitations:
- Kernel must be aligned to 256MB
Backport:
- Changes in page.h are backported from newer kernel version
mmu_mapin_ram function has to reflect offset in memory start.
On 06/14/11 17:34, Michal Simek wrote:
Hi,
have someone tried to support RELOCATABLE kernel on ppc44x?
As Josh, mentioned, I will be working on this. In fact I was trying a couple of
patches towards this on PPC440x. But, I am stuck in debugging the hang that I am
experiencing with the changes
The PPC440X currently uses 256M TLB entries to pin the
lowmem. When we go for a relocatable kernel we have to :
1) Restrict the kernel load address to be 256M aligned
OR
2) Use 16M TLB(the next possible TLB page size supported)
entries till the first
256M and then use the 256M TLB
On Wed, Jun 15, 2011 at 11:30 AM, David Laight david.lai...@aculab.comwrote:
The PPC440X currently uses 256M TLB entries to pin the
lowmem. When we go for a relocatable kernel we have to :
1) Restrict the kernel load address to be 256M aligned
OR
2) Use 16M TLB(the next possible
On Wed, 2011-06-15 at 11:43 +0530, Suzuki Poulose wrote:
On 06/14/11 17:34, Michal Simek wrote:
Hi,
have someone tried to support RELOCATABLE kernel on ppc44x?
As Josh, mentioned, I will be working on this. In fact I was trying a couple
of
patches towards this on PPC440x. But, I am
On Wed, 2011-06-15 at 10:30 +0100, David Laight wrote:
The PPC440X currently uses 256M TLB entries to pin the
lowmem. When we go for a relocatable kernel we have to :
1) Restrict the kernel load address to be 256M aligned
OR
2) Use 16M TLB(the next possible TLB page size
On 06/15/11 15:41, Benjamin Herrenschmidt wrote:
On Wed, 2011-06-15 at 11:43 +0530, Suzuki Poulose wrote:
On 06/14/11 17:34, Michal Simek wrote:
Hi,
have someone tried to support RELOCATABLE kernel on ppc44x?
As Josh, mentioned, I will be working on this. In fact I was trying a couple
On Wed, Jun 15, 2011 at 7:40 AM, Suzuki Poulose suz...@in.ibm.com wrote:
On 06/15/11 15:41, Benjamin Herrenschmidt wrote:
On Wed, 2011-06-15 at 11:43 +0530, Suzuki Poulose wrote:
On 06/14/11 17:34, Michal Simek wrote:
Hi,
have someone tried to support RELOCATABLE kernel on ppc44x
On Wed, 15 Jun 2011 20:11:55 +1000
Benjamin Herrenschmidt b...@kernel.crashing.org wrote:
On Wed, 2011-06-15 at 11:43 +0530, Suzuki Poulose wrote:
On 06/14/11 17:34, Michal Simek wrote:
Hi,
have someone tried to support RELOCATABLE kernel on ppc44x?
As Josh, mentioned, I
Hi,
have someone tried to support RELOCATABLE kernel on ppc44x?
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian
On Tue, Jun 14, 2011 at 02:04:45PM +0200, Michal Simek wrote:
Hi,
have someone tried to support RELOCATABLE kernel on ppc44x?
Suzuki will be working on this eventually as part of getting kexec/kdump
working for 44x. I've CC'd him.
josh
___
Linuxppc
13 matches
Mail list logo
