Work around a problem reported on:
http://ozlabs.org/pipermail/linuxppc-embedded/2005-July/019038.html
Without this patch I2C on mpc5200 becomes unusable after a while.
Tested on mpc5200 based boards by Matthias and me.
Signed-off-by: Domen Puncer [EMAIL PROTECTED]
---
Low-power mode implementation for Lite5200b.
Some I/O registers are also saved here.
A recent U-Boot that supports this (lite5200b_PM_config) is needed.
Signed-off-by: Domen Puncer [EMAIL PROTECTED]
---
It would be nice to get this merged.
arch/powerpc/platforms/52xx/Makefile |3
sparse caught these static functions / __iomem annotations
under arch/powerpc/platform/52xx/
Signed-off-by: Domen Puncer [EMAIL PROTECTED]
---
Reposting, adding tnt to Cc, and requesting inclusion.
The patch is pretty much harmless :-)
arch/powerpc/platforms/52xx/efika.c |4 ++--
When compiled without swap support, arch/mm/tlb.c complains about missing
function declarations. This patch fixes the warnings.
Signed-off-by: Laurent Pinchart [EMAIL PROTECTED]
---
arch/ppc/mm/tlb.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/arch/ppc/mm/tlb.c
Hi All,
I am currently trying to identify an anoying feature of linux on my
sparc32 systems but I will do some work on the ppc - powerpc migration
as soon as I have exauhsted my current avenues of investiation on the
sparc32 issue.
Regards
Mark Fortescue.
On Mon, 9 Jul 2007, Arnd
On 7/9/07, Domen Puncer [EMAIL PROTECTED] wrote:
Work around a problem reported on:
http://ozlabs.org/pipermail/linuxppc-embedded/2005-July/019038.html
Without this patch I2C on mpc5200 becomes unusable after a while.
Tested on mpc5200 based boards by Matthias and me.
Index:
On 7/9/07, Domen Puncer [EMAIL PROTECTED] wrote:
sparse caught these static functions / __iomem annotations
under arch/powerpc/platform/52xx/
Signed-off-by: Domen Puncer [EMAIL PROTECTED]
Signed-off-by: Grant Likely [EMAIL PROTECTED]
---
Reposting, adding tnt to Cc, and requesting
On 7/8/07, John Rigby [EMAIL PROTECTED] wrote:
I see your point, I agree the two layers of glue is bad. But this means
the double code is spread across many drivers instead of being in one
place (fsl_soc.c).
??? I don't understand what you mean. Are you saying that it's
better to have all
I'm just saying that an argument can be made that having all the OF to
non-OF
glue in one place is better than having dual bindings in every driver.
If you count ugliness in terms of file count the fsl_soc.c solution
gets a score of 1 and the dual binding solution gets an score of N.
Where N is
hi:
I had read some confusing code about io address map in
MPC8560 that employs E500 core. My confusion is when io address map is
setup, if _PAGE_PRESENT flag of page is set? In implementation of
mpc8560 , that seems page flag that maps to io address region is
0x280, means only the
10 matches
Mail list logo
