> Subject: Question about MPIC_SINGLE_DEST_CPU on P1020 (e500 core) SMP
>
> Hi
> The P1020 manual states (in the PIC chapter) that in the "Internal
> Interrupt Destination" register, only 1 CPU (and not both) can be
> selected as the IRQ destination. How then can we achieve "interrupt
> spraying"
Hi All,
Currently I am working on p1020rdb soc for some kernel bringing up activity.
I have come across one requirement to update the memory map (MMAP) of
kernel from evaluation board to
some other board who is having the same soc.
for my eval board I have used the p1020rdb.dts file from 2.6.38 s
> -Original Message-
> From: Jia Hongtao-B38951
> Sent: Monday, June 11, 2012 8:03 AM
> To: Bhushan Bharat-R65777; linuxppc-dev@lists.ozlabs.org;
> ga...@kernel.crashing.org
> Cc: Li Yang-R58472; b...@kernel.crashing.org; Wood Scott-B07421
> Subject: RE: [PATCH 0/6] Description for PCI pa
On 06/09/2012 04:00 AM, Joakim Tjernlund wrote:
>
>
> Scott Wood wrote on 2012/06/08 21:23:50:
>
>> From: Scott Wood
>> To: Joakim Tjernlund ,
>> Cc:
>> Date: 2012/06/08 21:25
>> Subject: Re: P2010 External HW IRQ number?
>>
>> On 06/08/2012 06:06 AM, Joakim Tjernlund wrote:
>>>
>>> I have be
On 06/10/2012 09:33 PM, Jia Hongtao-B38951 wrote:
>> -Original Message-
>> From: Bhushan Bharat-R65777
>> Sent: Friday, June 08, 2012 6:47 PM
>> To: Jia Hongtao-B38951; linuxppc-dev@lists.ozlabs.org;
>> ga...@kernel.crashing.org
>> Cc: Li Yang-R58472; b...@kernel.crashing.org; Wood Scott-B0
On 06/10/2012 03:37 PM, Gopalakrishnan Raman wrote:
> Hi
>
> The P1020 manual states (in the PIC chapter) that in the “Internal
> Interrupt Destination” register, only 1 CPU (and not both) can be
> selected as the IRQ destination.
Right.
> How then can we achieve “interrupt
> spraying” for the P
Ananth, Srikar,
I think the patch is correct and I am sorry for nit-picking,
this is really minor.
But,
On 06/08, Ananth N Mavinakayanahalli wrote:
>
> Changes in V2:
> Pass (unsigned long)addr
Well, IMHO, this is confusing.
First of all, why do we have this "addr" or even "vaddr"? It should
n
On 06/11, Oleg Nesterov wrote:
>
> Note also that we should move this !UPROBE_COPY_INSN from
> install_breakpoint() to somewhere near alloc_uprobe().
The main problem is, uprobe_register() doesn't have struct file
for read_mapping_page().
Stupid question. I'm afraid the answer is "no" but I'll as
Is it possible to reserve some memory using OF rsvmap such that Linux
will not touch this area at all? Think of is as warm start stash area
were one could store data which should survive a reboot.
One could then create an uio driver which exports this memory to user space I
hope.
Jocke
__
On 06/11/2012 02:52 AM, Kay One wrote:
> Hi All,
>
> Currently I am working on p1020rdb soc for some kernel bringing up activity.
> I have come across one requirement to update the memory map (MMAP) of
> kernel from evaluation board to
> some other board who is having the same soc.
>
> for my eva
On Sun, 2012-06-10 at 23:31 -0400, Justin Hibbits wrote:
> I'll settle on just getting the CPU speed change working, losing 333MHz
> on my TiBook is a few too many MHz for the poor thing to lose :) I do
> have a desktop, but that's my development platform, so needs to be
> at least somewhat stabl
On Tue, Jun 5, 2012 at 11:26 PM, Benjamin Herrenschmidt
wrote:
> On Wed, 2012-05-23 at 11:33 +0900, Hiroo Matsumoto wrote:
>> This patchset is for PCI hotplug.
>>
>>
>> pcibios_setup_bus_devices which sets DMA and IRQs of PCI device is called
>> only when boot. DMA setting in probe for PCI driver,
On Mon, 2012-06-11 at 16:51 -0600, Bjorn Helgaas wrote:
> > This makes me a bit nervous (that doesn't mean it's not right, but
> > we need some careful auditing & testing here, which I won't be
> > able to do until I'm back from leave). Mostly due to the change in when
> > we do the work.
> >
> >
> -Original Message-
> From: Bhushan Bharat-R65777
> Sent: Monday, June 11, 2012 9:25 PM
> To: Jia Hongtao-B38951; linuxppc-dev@lists.ozlabs.org;
> ga...@kernel.crashing.org
> Cc: Li Yang-R58472; b...@kernel.crashing.org; Wood Scott-B07421
> Subject: RE: [PATCH 0/6] Description for PCI pa
> -Original Message-
> From: Wood Scott-B07421
> Sent: Monday, June 11, 2012 11:43 PM
> To: Jia Hongtao-B38951
> Cc: Bhushan Bharat-R65777; linuxppc-dev@lists.ozlabs.org;
> ga...@kernel.crashing.org; Li Yang-R58472; b...@kernel.crashing.org; Wood
> Scott-B07421
> Subject: Re: [PATCH 0/6]
On Fri, 2012-06-08 at 14:51 +0530, Ananth N Mavinakayanahalli wrote:
> On Fri, Jun 08, 2012 at 04:38:17PM +1000, Michael Ellerman wrote:
> > On Fri, 2012-06-08 at 11:49 +0530, Ananth N Mavinakayanahalli wrote:
> > > On Fri, Jun 08, 2012 at 04:17:44PM +1000, Michael Ellerman wrote:
> > > > On Fri, 2
On Tue, Jun 12, 2012 at 02:01:46PM +1000, Michael Ellerman wrote:
> On Fri, 2012-06-08 at 14:51 +0530, Ananth N Mavinakayanahalli wrote:
> > On Fri, Jun 08, 2012 at 04:38:17PM +1000, Michael Ellerman wrote:
> > > On Fri, 2012-06-08 at 11:49 +0530, Ananth N Mavinakayanahalli wrote:
> > > > On Fri, J
From: Wanpeng Li
Warning(arch/powerpc/kernel/pci_of_scan.c:210): Excess function parameter
'node' description in 'of_scan_pci_bridge'
Warning(arch/powerpc/kernel/vio.c:636): No description found for parameter
'desired'
Warning(arch/powerpc/kernel/vio.c:636): Excess function parameter 'new_desir
18 matches
Mail list logo
