Re: Appletouch going wild

2007-11-10 Thread Andreas Schwab
Johannes Berg <[EMAIL PROTECTED]> writes: > On Fri, 2007-11-09 at 13:58 +0100, Andreas Schwab wrote: >> Every once in a while the touchpad in my iBook G4 (geyser1, 030B) is >> going wild, emitting random movement events even when not being touched. >> That started only with 2.6.24-rc1. The only w

Re: [PATCH v4 04/13] [POWERPC] Add generic support for simple MPC5200 based boards

2007-11-10 Thread Wolfgang Denk
In message <[EMAIL PROTECTED]> you wrote: > This patch adds support for 'mpc5200-simple-platform' compatible > boards which do not need a platform specific setup. Such boards > are supported assuming the following: ... > + const char *board[] = { > + "tqc,tqm5200", > +

Re: PPC440EPx on Sequoia: /proc/iomem acts weird

2007-11-10 Thread Stefan Roese
Hi Steve, On Friday 09 November 2007, Steven A. Falco wrote: > I am using the Denx 2.6.32 kernel, which does have powerpc/sequoia. > Xenomai is a real-time kernel built on Adeos/Ipipe. I'll dig into it > further. Is this arch/ppc or arch/powerpc? I remember fixing this a while ago in arch/ppc:

2.6.24-rc2-git powerpc - kernel build fails !CONFIG_SMP

2007-11-10 Thread Kamalesh Babulal
Hi, The 2.6.24-rc2-git1 kernel build fails with randconfig on powerpc, CC arch/powerpc/mm/tlb_64.o arch/powerpc/mm/tlb_64.c: In function ‘pgtable_free_now’: arch/powerpc/mm/tlb_64.c:71: error: ‘pte_free_smp_sync’ undeclared (first use in this function) arch/powerpc/mm/tlb_64.c:71: error:

Re: Kernel locks up after calling kernel_execve()

2007-11-10 Thread Gerhard Pircher
Original-Nachricht > Datum: Fri, 09 Nov 2007 18:50:29 +1100 > Von: Benjamin Herrenschmidt <[EMAIL PROTECTED]> > An: Gerhard Pircher <[EMAIL PROTECTED]> > CC: linuxppc-dev@ozlabs.org > Betreff: Re: Kernel locks up after calling kernel_execve() > > > I tried to use /bin/sh as ini

IRQs in i2c-mpc.c

2007-11-10 Thread Jon Smirl
I'm doing final clean up the i2c open firmware support. What is the intention of this code? Is it meant for a missing IRQ attribute to return a zero and not get an IRQ for the device? Does the device function without an IRQ? If so, it needs a comment explaining things. Otherwise IRQ of zero should

[PATCH] [POWERPC] Fix CONFIG_SMP=n build error on ppc64

2007-11-10 Thread Olof Johansson
[POWERPC] Fix CONFIG_SMP=n build error The patch "KVM: fix !SMP build error" change the way smp_call_function() actually uses the passed in function names on non-SMP builds. So previously it was never caught that the function passed in was never actually defined. This causes a build error on ppc6

Re: IRQs in i2c-mpc.c

2007-11-10 Thread Kumar Gala
On Nov 10, 2007, at 1:44 PM, Jon Smirl wrote: > I'm doing final clean up the i2c open firmware support. What is the > intention of this code? Is it meant for a missing IRQ attribute to > return a zero and not get an IRQ for the device? Does the device > function without an IRQ? If so, it needs a

Re: IRQs in i2c-mpc.c

2007-11-10 Thread Jon Smirl
On 11/10/07, Kumar Gala <[EMAIL PROTECTED]> wrote: > Looking at the current driver it looks like we could get ride of if > check since the previous code checked the return of platform_get_irq(). The code was a snippet from the larger patch that is converting i2c from being a platform driver to a o

Re: IRQs in i2c-mpc.c

2007-11-10 Thread Kumar Gala
On Nov 10, 2007, at 5:16 PM, Jon Smirl wrote: > On 11/10/07, Kumar Gala <[EMAIL PROTECTED]> wrote: >> Looking at the current driver it looks like we could get ride of if >> check since the previous code checked the return of >> platform_get_irq(). > > The code was a snippet from the larger patc

Re: IRQs in i2c-mpc.c

2007-11-10 Thread Jon Smirl
On 11/10/07, Kumar Gala <[EMAIL PROTECTED]> wrote: > > On Nov 10, 2007, at 5:16 PM, Jon Smirl wrote: > > > On 11/10/07, Kumar Gala <[EMAIL PROTECTED]> wrote: > >> Looking at the current driver it looks like we could get ride of if > >> check since the previous code checked the return of > >> platfo

Re: Kernel locks up after calling kernel_execve()

2007-11-10 Thread Benjamin Herrenschmidt
On Sat, 2007-11-10 at 18:11 +0100, Gerhard Pircher wrote: > Original-Nachricht > > Datum: Fri, 09 Nov 2007 18:50:29 +1100 > > Von: Benjamin Herrenschmidt <[EMAIL PROTECTED]> > > An: Gerhard Pircher <[EMAIL PROTECTED]> > > CC: linuxppc-dev@ozlabs.org > > Betreff: Re: Kernel locks

Re: [PATCH] [POWERPC] Fix CONFIG_SMP=n build error on ppc64

2007-11-10 Thread Kamalesh Babulal
On Sat, Nov 10, 2007 at 02:59:29PM -0600, Olof Johansson wrote: > [POWERPC] Fix CONFIG_SMP=n build error > > The patch "KVM: fix !SMP build error" change the way smp_call_function() > actually uses the passed in function names on non-SMP builds. So > previously it was never caught that the functio

Re: [PATCH] Avoid unpaired stwcx. on some processors

2007-11-10 Thread Benjamin Herrenschmidt
> Seems like a "better" (but still ugly) workaround would be to create a > _new_ reservation to a RA that's unavailable to any userspace process, > so that they could never do a successful store to it. That way you would > have stray reservations, but never dangling stwcx:es. No? Many processors

Re: IRQs in i2c-mpc.c

2007-11-10 Thread Benjamin Herrenschmidt
On Sat, 2007-11-10 at 17:18 -0600, Kumar Gala wrote: > On Nov 10, 2007, at 5:16 PM, Jon Smirl wrote: > > > On 11/10/07, Kumar Gala <[EMAIL PROTECTED]> wrote: > >> Looking at the current driver it looks like we could get ride of if > >> check since the previous code checked the return of > >> pl

Re: IRQs in i2c-mpc.c

2007-11-10 Thread Benjamin Herrenschmidt
> irq_of_parse_and_map() returns NO_IRQ when the irq parameter is missing. > > This API appears to be broken. In asm-powerpc/irq.h NO_IRQ is defined > as (0). There is no way to tell an error in the attribute from a valid > attribute selecting interrupt zero. No, it is not broken. Interrupt numb

Re: [PATCH] Avoid unpaired stwcx. on some processors

2007-11-10 Thread Olof Johansson
On Sun, Nov 11, 2007 at 03:46:05PM +1100, Benjamin Herrenschmidt wrote: > > > Seems like a "better" (but still ugly) workaround would be to create a > > _new_ reservation to a RA that's unavailable to any userspace process, > > so that they could never do a successful store to it. That way you wou