Re: Boot hang when setting console=none with MPC5200B custom board

Hi Sylvain: > Humm I see, here is the node I'm creating in the initial ramdisk, so > they are there before mdev is launched in one of my init scripts. [snip] I additionally have "tty0 c 4 0" which might be important here, plus a lot of other crap (should clean up there...;-). I don't use a ramd

Re: [PATCH] Fixes for MPC512x PSC

Hi Steve: A while ago I posted a patch which improves the baud rate calculation of the '5200, but also refactors the driver a little bit so it also influences the '512x. However, there has been some confusion about the config regs of the 521x's uart. It would be great if you colud have a look

Re: [PATCH] Fixes for MPC512x PSC

On Thu, 22 Apr 2010 19:13:21 -0500 "Steve Deiters" wrote: > This will apply on the mpc512x-v2.6.33-devel branch of the DENX git > repository. This is all mostly based > on what was in the Freescale LTIB release from the Freescale website. Please don't use mpc512x-v2.6.33-devel branch, it is obs

Re: [PATCH 1/2][RESEND] ehea: error handling improvement

On 04/22/2010 07:36 AM, David Miller wrote: From: Thomas Klein Date: Wed, 21 Apr 2010 11:10:55 +0200 Reset a port's resources only if they're actually in an error state Signed-off-by: Thomas Klein --- Patch created against net-2.6 I thought you were sorry for wasting my time and that you we

Re: [GIT PULL] Perf probe support for PowerPC, from Ian Munsie

* Paul Mackerras wrote: > Ingo, > > Please pull my perf.git master branch: > > git://git.kernel.org/pub/scm/linux/kernel/git/paulus/perf.git master > > It has two commits from Ian Munsie that allow us to access local > variables with perf probe on PowerPC. We also need a commit in Ben's >

Re: [patch 11/14] powerpc: invoke oom-killer from page fault

On Thu, Apr 22, 2010 at 02:44:22PM -0700, David Rientjes wrote: > On Fri, 23 Apr 2010, npig...@suse.de wrote: > > > As explained in commit 1c0fe6e3bd, we want to call the architecture > > independent > > oom killer when getting an unexplained OOM from handle_mm_fault, rather than > > simply killi

Re: Continual reading from the PowerPc time base register is not stable

Hi Kim The isync is not needed, when I only added the long long cast, the problem can never reproduced. And I found after Linux started, I ran the "gettime" test code in the background, if I ran our software application, the gettime could fail sometimes, and even after killing our soft

Re: My MDIO is acting strange

linux 2.6.22 is working correctly on my board. So, I think this is due to the difference between them. I will check the boot time difference between 2.6.22 and my new port. Hope that will give me a clue. 2010/4/23 Andy Fleming : > On Thu, Apr 22, 2010 at 9:36 PM, Peter Pan wrote: >> I'm porting L

Initcall ordering

I'm having trouble with the I2C devices on my 8347 platform. The problem is that I2C device probe() functions are only called once, as the I2C bus is being initialized (in this case fsl_i2c_init()) I have 2 devices on this bus, one device gets it's initcall before fsl_i2c_init, the second one does

[PATCH 1/2] fsl_pq_mdio: Fix kernel oops during OF address translation

Old P1020RDB device trees were not specifing tbipa address for MDIO nodes, which is now causing this kernel oops: ... eth2: TX BD ring size for Q[6]: 256 eth2: TX BD ring size for Q[7]: 256 Unable to handle kernel paging request for data at address 0x Faulting instruction address: 0xc

[PATCH 2/2] gianfar: Fix potential oops during OF address translation

gianfar driver may pass NULL pointer to the of_translate_address(), which may lead to a kernel oops. Fix this by using of_iomap(), which is also much simpler and shorter. Signed-off-by: Anton Vorontsov --- drivers/net/gianfar.c |6 +- 1 files changed, 1 insertions(+), 5 deletions(-) dif

Re: Initcall ordering

On 04/23/2010 09:56 AM, Gary Thomas wrote: I'm having trouble with the I2C devices on my 8347 platform. The problem is that I2C device probe() functions are only called once, as the I2C bus is being initialized (in this case fsl_i2c_init()) I have 2 devices on this bus, one device gets it's initc

[PATCH] add icswx support

Add Power7 icswx co-processor instruction support. Signed-off-by: Sonny Rao Signed-off-by: Tseng-Hui (Frank) Lin --- arch/powerpc/include/asm/mmu-hash64.h |3 + arch/powerpc/include/asm/mmu_context.h |4 ++ arch/powerpc/include/asm/reg.h |3 + arch/powerpc/mm/mmu_context_ha

Re: [PATCH 1/2] fsl_pq_mdio: Fix kernel oops during OF address translation

From: Anton Vorontsov Date: Fri, 23 Apr 2010 21:12:35 +0400 > Old P1020RDB device trees were not specifing tbipa address for > MDIO nodes, which is now causing this kernel oops: > > ... > eth2: TX BD ring size for Q[6]: 256 > eth2: TX BD ring size for Q[7]: 256 > Unable to handle kernel pagi

Re: [PATCH 2/2] gianfar: Fix potential oops during OF address translation

From: Anton Vorontsov Date: Fri, 23 Apr 2010 21:12:44 +0400 > gianfar driver may pass NULL pointer to the of_translate_address(), > which may lead to a kernel oops. Fix this by using of_iomap(), which > is also much simpler and shorter. > > Signed-off-by: Anton Vorontsov Also applied to net-2.

Re: [PATCH] add icswx support

On Fri, 2010-04-23 at 17:04 -0500, Tseng-Hui (Frank) Lin wrote: > Add Power7 icswx co-processor instruction support. Please provide a -much- more detailed explanation of what it is, what it does and why it requires hooking into the MMU context switch code. _I_ know these things but nobody else on

Re: Initcall ordering

Hi Gary, (adding linux-i2c) On Fri, Apr 23, 2010 at 09:56:07AM -0600, Gary Thomas wrote: > I'm having trouble with the I2C devices on my 8347 platform. > The problem is that I2C device probe() functions are only called > once, as the I2C bus is being initialized (in this case fsl_i2c_init()) > I