Guennadi Liakhovetski writes:
> On Thu, 9 Aug 2007, Segher Boessenkool wrote:
>
> > > > strncpy() won't put a terminating zero on there, is everything
> > > > that uses the resulting string okay with that? Also, if the
> > > > name gets cut short, it might match some _other_ expected name.
> > >
Signed-off-by: Stephen Rothwell <[EMAIL PROTECTED]>
---
drivers/macintosh/windfarm_smu_sat.c |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
--
Cheers,
Stephen Rothwell[EMAIL PROTECTED]
diff --git a/drivers/macintosh/windfarm_smu_sat.c
b/drivers/macintosh/windf
This removes some of the #ifdefs from .c files.
Signed-off-by: Stephen Rothwell <[EMAIL PROTECTED]>
---
arch/powerpc/mm/hash_utils_64.c |6 --
arch/powerpc/mm/mmu_context_64.c |8 +---
include/asm-powerpc/page_64.h|7 +++
3 files changed, 8 insertions(+), 13 deletions
From: Stephen Rothwell <[EMAIL PROTECTED]>
Date: Wed, 15 Aug 2007 16:45:15 +1000
> They were only needed for backwards compatibility and all in tree uses
> have now been changed.
>
> Signed-off-by: Stephen Rothwell <[EMAIL PROTECTED]>
Acked-by: David S. Miller <[EMAIL PROTECTED]>
Thanks for doi
They were only needed for backwards compatibility and all in tree uses
have now been changed.
Signed-off-by: Stephen Rothwell <[EMAIL PROTECTED]>
---
include/asm-powerpc/prom.h |1 -
include/asm-ppc/prom.h |1 -
include/linux/of.h |1 -
3 files changed, 0 insertions(+), 3
get_property has been renamed to of_get_property.
Signed-off-by: Stephen Rothwell <[EMAIL PROTECTED]>
---
drivers/char/ipmi/ipmi_si_intf.c |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
--
Cheers,
Stephen Rothwell[EMAIL PROTECTED]
diff --git a/drivers/char
On Tuesday 14 August 2007, Valentine Barshak wrote:
> AMCC Sequoia device tree.
Please find some comments below.
> Signed-off-by: Valentine Barshak <[EMAIL PROTECTED]>
> ---
> arch/powerpc/boot/dts/sequoia.dts | 289
> ++ 1 files changed, 289 insertions(+)
>
>
arch/powerpc/mm/mmu_context_64.c: In function 'init_new_context':
arch/powerpc/mm/mmu_context_64.c:31: warning: unused variable 'new_context'
Signed-off-by: Stephen Rothwell <[EMAIL PROTECTED]>
---
arch/powerpc/mm/mmu_context_64.c |5 ++---
arch/powerpc/mm/slice.c |1 +
2 files c
On Tue, Aug 14, 2007 at 11:04:09PM +0400, Valentine Barshak wrote:
> AMCC 440EPx Sequoia board support.
> The second bit (0x4) in the 440EPx/440GRx PVR value indicates
> the Security/Kasumi engine absence if set.
> This bit has been removed from the pvr mask to use a single
> cputable entry for wit
On Tue, Aug 14, 2007 at 10:53:55PM +0400, Valentine Barshak wrote:
> Bootwrapper code for AMCC 440EPx Sequoia board.
> The DDR2 Denali controller support has been moved to
> arch/powerpc/boot/4xx.c
> The code also uses 440EP clocking fixups
> initially provided for 440EP Bamboo.
>
> Signed-off-by
On Tue, Aug 14, 2007 at 10:48:43PM +0400, Valentine Barshak wrote:
> AMCC Sequoia device tree.
>
> Signed-off-by: Valentine Barshak <[EMAIL PROTECTED]>
> ---
> arch/powerpc/boot/dts/sequoia.dts | 289
> ++
> 1 files changed, 289 insertions(+)
>
> diff -ruN l
I am working on a separate project where there is a
discontiguous physical memory map . In looking at
solutions, it looks like the way to go is to
use something like a SPARSEMEM option.
FWIW, it even mentions something about discontinuous
memory in the Device Tree example about the 970 CPU
(Doc
On Tue, 2007-08-14 at 15:14, mike zheng wrote:
> Hi All,
>
> I am trying to bring up MPC8548 CDS board on 2.4 kernel. I have
> problem in the head
Ow, it hurts when I do this!
> _e500.S. The "mtspr SRR0, r7; mtspr SRR1 r6" does not work for me. The
> content of R7 and R6 are not moved to SRR0 a
Hi All,
I am trying to bring up MPC8548 CDS board on 2.4 kernel. I have problem in
the head_e500.S. The "mtspr SRR0, r7; mtspr SRR1 r6" does not work for me.
The content of R7 and R6 are not moved to SRR0 and SRR1. I am using the
tool-chain from Freescale for 2.6 kernel.
Any idea on this issue?
On Tue, 14 Aug 2007 22:45:00 +0400
Valentine Barshak <[EMAIL PROTECTED]> wrote:
> Sequoia defconfig
>
> Signed-off-by: Valentine Barshak <[EMAIL PROTECTED]>
> ---
> arch/powerpc/configs/sequoia_defconfig | 783
> +
> 1 files changed, 783 insertions(+)
>
> diff
AMCC 440EPx Sequoia board support.
The second bit (0x4) in the 440EPx/440GRx PVR value indicates
the Security/Kasumi engine absence if set.
This bit has been removed from the pvr mask to use a single
cputable entry for with/without Security/Kasumi cpu versions.
Signed-off-by: Valentine Barshak <[
Bootwrapper code for AMCC 440EPx Sequoia board.
The DDR2 Denali controller support has been moved to
arch/powerpc/boot/4xx.c
The code also uses 440EP clocking fixups
initially provided for 440EP Bamboo.
Signed-off-by: Valentine Barshak <[EMAIL PROTECTED]>
---
arch/powerpc/boot/44x.h|
AMCC Sequoia device tree.
Signed-off-by: Valentine Barshak <[EMAIL PROTECTED]>
---
arch/powerpc/boot/dts/sequoia.dts | 289 ++
1 files changed, 289 insertions(+)
diff -ruN linux-2.6.orig/arch/powerpc/boot/dts/sequoia.dts
linux-2.6/arch/powerpc/boot/dts/sequo
Sequoia defconfig
Signed-off-by: Valentine Barshak <[EMAIL PROTECTED]>
---
arch/powerpc/configs/sequoia_defconfig | 783 +
1 files changed, 783 insertions(+)
diff -ruN linux-2.6.orig/arch/powerpc/configs/sequoia_defconfig
linux-2.6/arch/powerpc/configs/sequoia_d
This file was protected by _PPC64_LMB_H, which is confusing, as the 32-bit code
also uses the lmb these days. Changed to _ASM_POWERPC_LMB_H.
Signed-off-by: Becky Bruce <[EMAIL PROTECTED]>
---
include/asm-powerpc/lmb.h |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/
The following patches add initial PowerPC 440EPx Sequoia board support.
The code is based mainly on the Bamboo board support by Josh Boyer and
should be applied on top of the "[patch 00/10] 4xx patch series for 2.6.24"
which adds Bamboo support, since Sequoia shares some code pieces with Bamboo.
Th
Hi Paul,
Is there a reason this hasn't been picked up:
http://ozlabs.org/pipermail/linuxppc-dev/2007-May/035906.html
It fixes a build warning in the tree and removes some dead code. It
appears to still apply cleanly to the top of your tree if there
are issues please let me know so I can
Geert Uytterhoeven wrote:
> Fix probing of PS3 storage devices: in the success case, we should set `error'
> to zero, not `result'.
>
> Without this patch no storage devices are found.
>
> Signed-off-by: Geert Uytterhoeven <[EMAIL PROTECTED]>
> ---
> This brown paper bag bug slipped in due to bad
Fix probing of PS3 storage devices: in the success case, we should set `error'
to zero, not `result'.
Without this patch no storage devices are found.
Signed-off-by: Geert Uytterhoeven <[EMAIL PROTECTED]>
---
This brown paper bag bug slipped in due to bad patch splitting.
Please apply as soon as
On Tue, Aug 14, David Woodhouse wrote:
> On Tue, 2007-08-14 at 13:49 +0200, Olaf Hering wrote:
> > On Wed, Apr 04, Paul Mackerras wrote:
> >
> > > David Woodhouse writes:
> > >
> > > > There are proper device numbers registered for pmac_zilog now. Use them.
> >
> > Which numbers?
>
> shinybook
On Tue, 2007-08-14 at 13:49 +0200, Olaf Hering wrote:
> On Wed, Apr 04, Paul Mackerras wrote:
>
> > David Woodhouse writes:
> >
> > > There are proper device numbers registered for pmac_zilog now. Use them.
>
> Which numbers?
shinybook /shiny/git/mtd-utils $ ls -l /dev/ttyPZ*
crw-rw 1 root
On Wed, Apr 04, Paul Mackerras wrote:
> David Woodhouse writes:
>
> > There are proper device numbers registered for pmac_zilog now. Use them.
Which numbers?
> Sigh. I guess this is inevitable, but IMNSHO this exposes a weakness
> in our serial subsystem.
So, when will the name of pmac_zilog
On Tue, Aug 14, 2007 at 12:29:18AM -0700, Greg KH wrote:
> -stable review patch. If anyone has any objections, please let us know.
>
> --
> From: Benjamin Herrenschmidt <[EMAIL PROTECTED]>
>
> My "slices" address space management code that was added in 2.6.22
> implementation of
On Tue, Aug 14, 2007 at 04:45:34PM +1000, David Gibson wrote:
> On Mon, Aug 13, 2007 at 04:26:27PM -0700, [EMAIL PROTECTED] wrote:
> >
> > This is a note to let you know that we have just queued up the patch titled
> >
> > Subject: powerpc: Fix size check for hugetlbfs
> >
> > to the 2.6.22
-stable review patch. If anyone has any objections, please let us know.
--
From: Benjamin Herrenschmidt <[EMAIL PROTECTED]>
My "slices" address space management code that was added in 2.6.22
implementation of get_unmapped_area() doesn't properly check that the
size is a multiple
30 matches
Mail list logo
