In message <4e1543b6.9060...@linux.vnet.ibm.com> you wrote:
> Hi ,
>
> Problem Description:
> Firmware update using the update_flash -f results to soft lockup
> BUG
> FLASH: preparing saved firmware image for flash
> FLASH: flash image is 50141296 bytes
> FLASH: performing flash and reboot
> FLAS
Hi ,
Problem Description:
Firmware update using the update_flash -f results to soft lockup
BUG
FLASH: preparing saved firmware image for flash
FLASH: flash image is 50141296 bytes
FLASH: performing flash and reboot
FLASH: this will take several minutes. Do not power off!
BUG: soft lockup - CPU#
As a result of changes to Kconfig files, we no longer enable
the lockup and hung task detectors. Both are very light weight
and provide useful information in the event of a hang, so
reenable them.
Signed-off-by: Anton Blanchard
---
Index: linux-powerpc/arch/powerpc/configs/ppc64_defconfig
==
Add mpt2sas driver to pseries and ppc64 defconfig.
Signed-off-by: Anton Blanchard
---
Index: linux-powerpc/arch/powerpc/configs/ppc64_defconfig
===
--- linux-powerpc.orig/arch/powerpc/configs/ppc64_defconfig 2011-07-07
09:07:29
The IRQs off tracer enables mcount which has a big impact on
performance. Disable it.
Signed-off-by: Anton Blanchard
---
Index: linux-powerpc/arch/powerpc/configs/ppc64_defconfig
===
--- linux-powerpc.orig/arch/powerpc/configs/ppc64
The pseries defconfig had a number of drivers enabled and we may
as well add them to the ppc64 defconfig.
Signed-off-by: Anton Blanchard
---
Index: linux-powerpc/arch/powerpc/configs/ppc64_defconfig
===
--- linux-powerpc.orig/arch/p
Here are a few defconfig updates I had lying around in my tree.
Anton
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
GPIO drivers are getting consolidated into drivers/gpio. While at it,
change the driver name to mpc5200-gpio* to avoid collisions.
Signed-off-by: Grant Likely
---
Ben, I'm going to take this via the gpio/next branch to avoid
conflicts with the big gpio rename.
g.
arch/powerpc/platforms/52xx/
On Mon, May 23, 2011 at 11:25:30AM +0200, Anatolij Gustschin wrote:
> The mpc52xx_gpio driver currently supports 8 wakeup GPIOs and 32
> simple GPIOs. Extend it to also support GPIO function of 8 simple
> interrupt GPIOs controlled in the standard GPIO register module.
>
> Signed-off-by: Anatolij
On Wed, Jul 06, 2011 at 11:43:19AM +0200, Anatolij Gustschin wrote:
> Hi Grant,
>
> can you please pick these patches for 3.1 ?
>
> On Mon, 16 May 2011 18:02:43 +0200
> Anatolij Gustschin wrote:
>
> > Both, #address-cells and #size-cells properties are required
> > for spi bus node, so add them
On Wed, Jul 06, 2011 at 11:46:27AM +0200, Anatolij Gustschin wrote:
> Hi Grant,
>
> Can you please pick this patch for 3.1 ?
>
> On Tue, 7 Jun 2011 00:27:05 +0200
> Anatolij Gustschin wrote:
>
> > timer0 and timer1 pins are used as simple GPIO on this board.
> > Add gpio-controller and #gpio-c
Hi Grant,
Ping.
On Mon, 23 May 2011 11:25:30 +0200
Anatolij Gustschin wrote:
> The mpc52xx_gpio driver currently supports 8 wakeup GPIOs and 32
> simple GPIOs. Extend it to also support GPIO function of 8 simple
> interrupt GPIOs controlled in the standard GPIO register module.
>
> Signed-off-
Hi Grant,
Can you please pick this patch for 3.1 ?
On Tue, 7 Jun 2011 00:27:05 +0200
Anatolij Gustschin wrote:
> timer0 and timer1 pins are used as simple GPIO on this board.
> Add gpio-controller and #gpio-cells properties to timer nodes
> so that we can control gpio lines using available MPC
Hi Grant,
can you please pick these patches for 3.1 ?
On Mon, 16 May 2011 18:02:43 +0200
Anatolij Gustschin wrote:
> Both, #address-cells and #size-cells properties are required
> for spi bus node, so add them.
>
> Signed-off-by: Anatolij Gustschin
> ---
> arch/powerpc/boot/dts/mpc5200b.dtsi
On Tue, 05 Jul 2011 16:40:10 +1000
Michael Neuling wrote:
> The existing code it pretty ugly. How about we clean it up even more
> like this?
Looks good and it passed my kdump test cases.
Anton
> From: Anton Blanchard
>
> We check for timeout expiry in the outer loop, but we also need to
>
Return -EAGAIN when we get H_BUSY back from the hypervisor. This
makes the hvc console driver retry, avoiding dropped printks.
Signed-off-by: Anton Blanchard
Cc:
---
Index: linux-powerpc/arch/powerpc/platforms/pseries/hvconsole.c
From: Hendrik Brueckner
Currently, the hvc_console_print() function drops console output if the
hvc backend's put_chars() returns 0. This patch changes this behavior
to allow a retry through returning -EAGAIN.
This change also affects the hvc_push() function. Both functions are
changed to hand
Hi Hendrik,
> So with the patch below, the backend can now indirectly control the
> way console output is handled for it. I still have to think if this
> solution is ok or if it is better to introduce a new callback to
> console output only (and might provide a default implemenatation
> similar
On Tue, 2011-07-05 at 19:14 -0400, Matthew L. Creech wrote:
> From: Mike Hench
>
> The eLBC NAND driver currently follows up each program/write operation with a
> read-back of the page, in order to [ostensibly] fill in ECC data for the
> caller. However, the page address used for this read is alw
19 matches
Mail list logo