On pseries powerpc, IPIs are registered with an IRQ number so
/proc/interrupts looks like this on a 2 core/2 thread machine:
CPU0 CPU1 CPU2 CPU3
16:316428232905141138794 983121 XICS Level
IPI
18:2605674 0 304994
>> > > A follow up question. With this method, the total image size
>> > > (uncompressed) is limited to the 4MB (the link address of
>> the boot
>> > > wrapper)?
>> >
>> > No.
>>
>> Yes, unless you change the link address, or provide a
>> vmlinux_alloc callback (which currently only happens on true
On Sep 21, 2010, at 5:34 PM, Timur Tabi wrote:
> On Tue, Sep 21, 2010 at 5:17 PM, Scott Wood wrote:
>
>> It needs to be the actual device that is performing the DMA -- the
>> platform may need to do things such as IOMMU manipulation where
>> knowing the device matters.
>
> Ok, this all makes s
On 09/21/2010 08:25 PM, Finn Thain wrote:
On Tue, 21 Sep 2010, Justin P. Mattock wrote:
Below is an update from the original, with changes to the broken web
addresses and removal of archive.org and moved to a seperate patch for
you guys to decide if you want to use this and/or just leave the o
On Tue, 21 Sep 2010, Justin P. Mattock wrote:
> Below is an update from the original, with changes to the broken web
> addresses and removal of archive.org and moved to a seperate patch for
> you guys to decide if you want to use this and/or just leave the old url
> in and leave it at that..
>
Below is a patch consisting of only the broken web addresses using
webarchive.org.
Please have a look and let me know if you want to go on with using these and/or
just
leave the old links in there.
Note: the address needs to have an %2A added to it due to webarchive.org
using a "*" for it's sea
Below is an update from the original, with changes to the broken web addresses
and removal of
archive.org and moved to a seperate patch for you guys to decide if you want to
use this and/or
just leave the old url in and leave it at that..
Please dont apply this to anything just comments and fixe
> -Original Message-
> From:
> linuxppc-dev-bounces+tiejun.chen=windriver@lists.ozlabs.or
> g
> [mailto:linuxppc-dev-bounces+tiejun.chen=windriver@lists.o
> zlabs.org] On Behalf Of Scott Wood
> Sent: Wednesday, September 22, 2010 6:07 AM
> To: Anderson, Trevor
> Cc: david.hag...@g
> -Original Message-
> From:
> linuxppc-dev-bounces+tiejun.chen=windriver@lists.ozlabs.or
> g
> [mailto:linuxppc-dev-bounces+tiejun.chen=windriver@lists.o
zlabs.org] On Behalf Of Scott Wood
> Sent: Wednesday, September 22, 2010 1:53 AM
> To: Chen, Tiejun
> Cc: ppcdev; uboot
> Subj
> -Original Message-
> From: Scott Wood [mailto:scottw...@freescale.com]
> Sent: Wednesday, September 22, 2010 1:00 AM
> To: Chen, Tiejun
> Cc: linuxppc-dev@lists.ozlabs.org; Guillaume Dargaud
> Subject: Re: Generating elf kernel ?
>
> On Tue, 21 Sep 2010 03:00:40 +0200
> "Chen, Tiejun"
On Tue, Sep 21, 2010 at 5:17 PM, Scott Wood wrote:
> It needs to be the actual device that is performing the DMA -- the
> platform may need to do things such as IOMMU manipulation where
> knowing the device matters.
Ok, this all makes sense. So it appears that the patch is valid, at
least in th
On Tue, 21 Sep 2010 17:08:54 -0500
Timur Tabi wrote:
> On Tue, Sep 21, 2010 at 5:05 PM, Dan Malek wrote:
>
> > The DMA descriptors are accessed using DMA by the
> > controller itself.
>
> Yes and no. Technically, it is DMA, but it's not something that
> SWIOTLB could ever know about. We just
On Sep 21, 2010, at 2:49 PM, Scott Wood wrote:
On Tue, 21 Sep 2010 16:43:12 -0500
Timur Tabi wrote:
Since we don't DMA the descriptors themselves, I just don't see how
this patch does anything.
Look in dmaengine.c, there are calls to dma_map_single() and
dma_map_page(), using what I assum
On Tue, Sep 21, 2010 at 5:05 PM, Dan Malek wrote:
> The DMA descriptors are accessed using DMA by the
> controller itself.
Yes and no. Technically, it is DMA, but it's not something that
SWIOTLB could ever know about. We just pass the physical address to
the DMA controller, and it does a memor
On Tue, 21 Sep 2010 17:37:15 -0400
"Anderson, Trevor" wrote:
> IRQ assignments for MPC8641D are "virtual",
This is true for powerpc in general.
> meaning "made up" and quite difficult to determine by looking through code.
> But I believe the plan goes something like this:
>
> IRQ
>
On Tue, Sep 21, 2010 at 4:49 PM, Scott Wood wrote:
> Look in dmaengine.c, there are calls to dma_map_single() and
> dma_map_page(), using what I assume is that same device pointer --
> unless there's confusion between the channel and the controller.
You're right. I missed this line in the drive
On Tue, 21 Sep 2010 16:43:12 -0500
Timur Tabi wrote:
> On Tue, Sep 21, 2010 at 4:34 PM, Scott Wood wrote:
>
> > This doesn't control allocation (it probably should with
> > dma_alloc_coherent, though I don't see it in the code), it controls
> > whether swiotlb will create a bounce buffer -- def
On Tue, Sep 21, 2010 at 4:34 PM, Scott Wood wrote:
> This doesn't control allocation (it probably should with
> dma_alloc_coherent, though I don't see it in the code), it controls
> whether swiotlb will create a bounce buffer -- defeating the point of
> using DMA to accelerate a memcpy.
But it w
IRQ assignments for MPC8641D are "virtual", meaning "made up" and quite
difficult to determine by looking through code.
But I believe the plan goes something like this:
IRQ
-
0 No interrupt
1 - 15External interrupts (only 1..12 would be used)
16 - 127 Inte
On Tue, 21 Sep 2010 16:24:10 -0500
Timur Tabi wrote:
> On Tue, Sep 21, 2010 at 7:55 AM, Kumar Gala wrote:
> >
> > On Sep 21, 2010, at 5:57 AM, Li Yang wrote:
> >
> >> Signed-off-by: Li Yang
> >> ---
> >
> > We really should have a sentence about how or why this works to address
> > 36-bit addr
On Tue, Sep 21, 2010 at 7:55 AM, Kumar Gala wrote:
>
> On Sep 21, 2010, at 5:57 AM, Li Yang wrote:
>
>> Signed-off-by: Li Yang
>> ---
>
> We really should have a sentence about how or why this works to address
> 36-bit addressing.
For example, I would like to know which memory is going to be
al
On Fri, Aug 27, 2010 at 18:30, John Stultz wrote:
> On one side, there is the view that the kernel should abstract and hide
> the hardware details to increase app portability. And the other is that
> the raw hardware details should be exposed, so the OS stays out of the
> way.
>
> Neither of these
On Tue, 21 Sep 2010 03:03:22 +0200
"Chen, Tiejun" wrote:
> > -Original Message-
> > From: Shawn Jin [mailto:shawnx...@gmail.com]
> > Sent: Tuesday, September 21, 2010 1:53 AM
> > To: Chen, Tiejun
> > Cc: ppcdev; uboot
> > Subject: Re: cuImage and multi image?
> >
> > >> I have a cuImage
On Tue, 21 Sep 2010 03:00:40 +0200
"Chen, Tiejun" wrote:
> This should be depend on the hypervisor design implementation. I think
> your
> option should be based on the Freescale hypervisor.
Again, I was giving an example, about ELF loading. I was not making any
claims about what all hyperviso
> -Original Message-
> From: linuxppc-dev-bounces+tmarri=amcc@lists.ozlabs.org
> [mailto:linuxppc-dev-bounces+tmarri=amcc@lists.ozlabs.org] On
> Behalf Of Ilya Yanok
> Sent: Sunday, September 19, 2010 1:01 PM
> To: linuxppc-...@ozlabs.org
> Subject: Re: [PATCH 1/2] PPC4xx: Genereliz
Hi Richard,
1. Character device
2. POSIX clock with dynamic ids
Please, just take your pick ;^)
Just to reopen this nearly dead but very interesting thread: I'm happy
with every solution that has no impact on the accuracy of the PTP clock.
If I can choose, I would prefer the POSIX clock wi
I'm new to developing on the PPC (most of my experience is on x86), and I
have a couple of questions about mapping of interrupts on the PPC,
specifically on the Freescale 8641D embedded CPU.
1) How does one allocate interrupt vectors for the embedded devices, such
as the MPIC? All the kernel how-t
On Sep 21, 2010, at 5:57 AM, Li Yang wrote:
> Signed-off-by: Li Yang
> ---
We really should have a sentence about how or why this works to address 36-bit
addressing.
> drivers/dma/fsldma.c |3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/dma/fsldma.c b/d
Hi Scott,
> On Sat, 18 Sep 2010 14:22:12 -0400
> Josh Boyer wrote:
>
>> Capitalizing? The patch you posted that uses this symbol is for a GPL
>> driver so you gain or lose nothing by having this symbol be
>> EXPORT_SYMBOL_GPL. Are you somehow advocating and getting some sort
>> of gain by allow
Signed-off-by: Li Yang
---
drivers/dma/fsldma.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/drivers/dma/fsldma.c b/drivers/dma/fsldma.c
index cea08be..9163552 100644
--- a/drivers/dma/fsldma.c
+++ b/drivers/dma/fsldma.c
@@ -1,7 +1,7 @@
/*
* Freescale MPC85xx, MPC
Hello,
I have a board with 2 PHYs attached to one FEC ethernet controler on
powerpc.
I want to implement some kind of main-standby attachment to LAN by
setting the ISOLATE bit on one on the two PHYs then monitoring the link
status and switch to the other PHY when the link status goes down.
I
31 matches
Mail list logo
