On Mon, 18 May 2009, Michael Neuling wrote:
> > > We can compile and boot with NR_CPUS=3D8192, so make this the max. 1024
> > > was an arbitrary decision anyway.
> >
> > Is 8192 still arbitrary? Or does something break above that?
>
> Yeah, the compile breaks after that with 4K pages.
>
> In dr
Hi Linus !
A few more 2.6.30 things for you... a defconfig update, and a couple
of small fixes, either obvious enough or regression fixes.
Cheers,
Ben.
The following changes since commit 86460103c412f9e11aeb7950cce64b9e51539d4d:
Linus Torvalds (1):
Merge branch 'for-linus' of git://git
On Mon, 2009-05-18 at 15:47 +1000, Stephen Rothwell wrote:
> Hi Ben,
>
> On Mon, 18 May 2009 15:12:03 +1000 Benjamin Herrenschmidt
> wrote:
> >
> > Thanks, but it's been fixed already :-)
> >
> > See commit b62c31ae401c6df25c61b206681a6e904ef97169.
>
> Should this be submitted for 2.6.29 stabl
Hi Ben,
On Mon, 18 May 2009 15:12:03 +1000 Benjamin Herrenschmidt
wrote:
>
> Thanks, but it's been fixed already :-)
>
> See commit b62c31ae401c6df25c61b206681a6e904ef97169.
Should this be submitted for 2.6.29 stable?
--
Cheers,
Stephen Rothwells...@canb.auug.org.au
http:
I don't think anything guarantees that the objects in data.page_aligned
are a multiple of PAGE_SIZE, thus the section may end on any boundary.
So the following section, .data.cacheline_aligned needs an explicit
alignment.
Signed-off-by: Benjamin Herrenschmidt
---
And this is the right patch aft
On Sun, 2009-05-17 at 23:49 -0500, Torez Smith wrote:
> File arch/powerpc/mm/tlb_nohash_low.S defines various processor specific low
> level TLB invalidation. Most all family of validations are grouped via
> pre-processor defines with the intent we error out if we reach the end and
> our platfor
File arch/powerpc/mm/tlb_nohash_low.S defines various processor specific low
level TLB invalidation. Most all family of validations are grouped via
pre-processor defines with the intent we error out if we reach the end and our
platform is not represented. Given this, the last few lines of the fi
On Thu, 2009-05-14 at 17:42 -0500, Becky Bruce wrote:
> This patch includes the basic infrastructure to use swiotlb
> bounce buffering on 32-bit powerpc. It is not yet enabled on
> any platforms. Probably the most interesting bit is the
> addition of addr_needs_map to dma_ops - we need this as
>
I don't think anything guarantees that the objects in data.page_aligned
are a multiple of PAGE_SIZE, thus the section may end on any boundary.
So the following section, .data.cacheline_aligned needs an explicit
alignment.
Signed-off-by: Benjamin Herrenschmidt
---
arch/powerpc/kernel/vmlinux.ld
On Thu, 2009-04-30 at 19:56 -0400, Tim Abbott wrote:
> .data.cacheline_aligned should not need a separate output section;
> this change moves it into the .data section.
>
> Since there isn't an ALIGN() directive before the
> .data.cacheline_aligned scetion in the current linker script, I'd like
>
From: Lennert Buytenhek
Date: Sat, 16 May 2009 01:53:30 +0200
> On Fri, May 15, 2009 at 08:39:24PM +0200, Gabriel Paubert wrote:
>
>> After 2.6.29, PPC no more admits passing NULL to the dev parameter of
>> the DMA API. The result is a BUG followed by solid lock-up when the
>> mv643xx_eth drive
On Tue, 2009-05-05 at 19:11 -0400, Steven Rostedt wrote:
> OK, so what's the status with this patch series?
>
> I don't want to pull it in unless I have an ack from Sam, and now
> there's issues with having -fno-omit-frame-pointer. Should we add a
> patch instead that simply removes that?
>
> If
> > We can compile and boot with NR_CPUS=3D8192, so make this the max. 1024
> > was an arbitrary decision anyway.
>
> Is 8192 still arbitrary? Or does something break above that?
Yeah, the compile breaks after that with 4K pages.
In drivers/base/node.c we have:
/* 2008/04/07: buf curren
On Thu, 2009-05-14 at 19:13 +0530, K.Prasad wrote:
> plain text document attachment (ppc64_prepare_code_01)
> Prepare the PowerPC code for HW Breakpoint infrastructure patches by including
> relevant constant definitions and function declarations.
Hi !
Some comments below...
> +#define HBP_NUM
On Sun, 2009-05-17 at 12:26 +0200, Krzysztof Helt wrote:
> If so please ignore my comment.
>
> Acked-by: Krzysztof Helt
Andrew, will you merge this or should I stick it into the powerpc.git
tree ?
Cheers,
Ben.
___
Linuxppc-dev mailing list
Linuxppc
On Fri, 2009-05-15 at 14:43 +0530, Vinay Sridhar wrote:
> Hello All,
>
> Quite a while back Michael Ellerman had posted a patch to add support to xmon
> to print the contents of the console log pointed to by __log_buf.
> Here's the link to that patch -
> http://ozlabs.org/pipermail/linuxppc64-de
On Fri, 2009-05-15 at 20:18 +0200, Gabriel Paubert wrote:
> Since PPC_MUTIPLATFORM was removed, it was impossible to select the
> driver for mv643xx_eth on the Pegasos. Fix by allowing to select
> the driver on CHRP platforms; Pegasos is a CHRP platform and the driver
> will not work wihtout arch/p
On Mon, 2009-05-18 at 11:13 +1000, Michael Neuling wrote:
> We can compile and boot with NR_CPUS=8192, so make this the max. 1024
> was an arbitrary decision anyway.
Is 8192 still arbitrary? Or does something break above that?
cheers
signature.asc
Description: This is a digitally signed messag
We can compile and boot with NR_CPUS=8192, so make this the max. 1024
was an arbitrary decision anyway.
Signed-off-by: Michael Neuling
--
No, I've not actually booted on a 8192 way machine, although if wishing
made it so
arch/powerpc/platforms/Kconfig.cputype |4 ++--
1 file changed,
> > How Solved:
> > Code was added that checks if initrd is in the highmem and relocates initrd
> > into lowmem if required.
>
> I don't think this is needed. Just don't load the ramdisk to highmem
> in the first place.
Well, it does make some sense to avoid the kernel eating itself if
passed
On Fri, 2009-05-15 at 16:43 +0800, Harry Ciao wrote:
> Support EDAC INT mode for Hypertransport devices, where southbridge
> NMI Request messages posted through Hypertransport Channel will
> be transferred to a MPIC interrupt instance that latches MPIC INT0
> pin. Also, Hypertransport Hostbridge co
> Also if initrd is in the highmem, uBoot adds initrd highmem region into the
> initial_boot_params->off_mem_rsvmap. This leads to kernel crash, because
> kernel
> assumes that regions from the initial_boot_params->off_mem_rsvmap are in the
> lowmem. So patch skips initrd highmem region when kern
At Sun, 17 May 2009 11:29:21 +0200 (CEST),
Julia Lawall wrote:
>
> From: Julia Lawall
>
> Eliminate direct accesses to the driver_data field.
> cf 82ab13b26f15f49be45f15ccc96bfa0b81dfd015
>
> The semantic patch that makes this change is as follows:
> (http://www.emn.fr/x-info/coccinelle/)
>
>
Dear Konstantin Baydarov,
In message <4a103edf.7050...@ru.mvista.com> you wrote:
>
> It turned out that:
> PPC uBoot always loads initrd image at the highest RAM address. So if board
> has
Please read the documentation, for example the U-Boot README - pay
speicial attention to the secti
Hello.
Recently I faced following issue:
On PPC targets with uBoot monitor with RAM size more than 768 Mb, boot with
initrd(rootfs image that is loaded separately from uImage) fails. Kernel crashes very early.
It turned out that:
PPC uBoot always loads initrd image at the highest RAM addres
On Sun, 17 May 2009 10:25:31 +0200
Geert Uytterhoeven wrote:
> On Sun, May 17, 2009 at 10:06, Krzysztof Helt wrote:
> > On Fri, 15 May 2009 12:19:17 -0600 Grant Likely
> > wrote:
> >> diff --git a/drivers/video/xilinxfb.c b/drivers/video/xilinxfb.c
> >> index 40a3a2a..7a868bd 100644
> >> --- a
From: Julia Lawall
Eliminate direct accesses to the driver_data field.
cf 82ab13b26f15f49be45f15ccc96bfa0b81dfd015
The semantic patch that makes this change is as follows:
(http://www.emn.fr/x-info/coccinelle/)
//
@@
struct device *dev;
expression E;
type T;
@@
- dev->driver_data = (T)E
+ dev
Hi,
(I haven't found any answers in the archives)
How would I access a NTFS shared directory from a Freescale MPC8313?
Will Samba run on a Freescale MPC8313?
Thanks,
Chris Plasun
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.o
Hi,
While part of my subject line might be redundant, how would I go about
accessing MS SQL Server from my Freescale MPC8313 machine?
Do I need to use a Linux ODBC driver?
Thank you for any help.
Chris Plasun
___
Linuxppc-dev mailing list
Linuxppc-
On Sun, May 17, 2009 at 10:06, Krzysztof Helt wrote:
> On Fri, 15 May 2009 12:19:17 -0600 Grant Likely
> wrote:
>> diff --git a/drivers/video/xilinxfb.c b/drivers/video/xilinxfb.c
>> index 40a3a2a..7a868bd 100644
>> --- a/drivers/video/xilinxfb.c
>> +++ b/drivers/video/xilinxfb.c
>> @@ -107,17 +
Hi Grant and John,
On Fri, 15 May 2009 12:19:17 -0600
Grant Likely wrote:
> Antonino,
>
Antonino is gone for quite a long time. I have reviewed your patch.
I have two comments only. Both are of small caliber.
> If you prefer, I'm willing to merge it via my powerpc tree.
>
As you prefer. If
31 matches
Mail list logo
