>
> It's already in Linus' tree.
Yeah, the problem is what's merged in linus's tree has p4080 listed and it
shouldn't
>
> Thanks,
>
> - - - -
> commit cd1542c8197fc3c2eb3a8301505d5d9738fab1e4
> Author: Anton Vorontsov
> Date: Tue Aug 10 18:03:21 2010 -0700
>
>edac: mpc85xx: add suppor
On Aug 19, 2010, at 4:28 PM, Timur Tabi wrote:
> Like the MPC8610 HPCD, the P1022DS ASoC DMA driver probes on individual DMA
> channel nodes, so the DMA controller nodes' compatible string must be listed
> in
> p1022_ds_ids[] to work.
>
> Signed-off-by: Timur Tabi
> ---
>
> This is for -next.
On Thu, Oct 07, 2010 at 01:18:19AM -0500, Kumar Gala wrote:
[...]
> > diff --git a/drivers/edac/mpc85xx_edac.c b/drivers/edac/mpc85xx_edac.c
> > index cfa86f7..b178cfa 100644
> > --- a/drivers/edac/mpc85xx_edac.c
> > +++ b/drivers/edac/mpc85xx_edac.c
> > @@ -652,7 +652,6 @@ static struct of_device_
On Aug 31, 2010, at 6:24 PM, Matthew McClintock wrote:
> First we check to see if we are the first core booting up. This
> is accomplished by comparing the boot_cpuid with -1, if it is we
> assume this is the first core coming up.
>
> Secondly, we need to update the initial thread info structure
On Aug 1, 2010, at 5:54 AM, Anton Vorontsov wrote:
> On Wed, Jul 21, 2010 at 06:21:08PM -0500, Scott Wood wrote:
> [...]
> + { .compatible = "fsl,p4080-l2-cache-controller", },
L2 on the p4080 is quite different from those other chips. It's part
of the core, controlled by SPR
On Aug 31, 2010, at 5:44 PM, Matthew McClintock wrote:
> The first global-utilities node might not contain the rstcr
> property, so we should search all the nodes
>
> Signed-off-by: Matthew McClintock
> ---
> -Changed KERN_EMERG to KERN_ERR
> -Break if we do not find rstcr mapped
> -Restore of_
On Sep 16, 2010, at 5:58 PM, Matthew McClintock wrote:
> When we do an mpic_reset_core we need to make sure the dcache
> is flushed
>
> Signed-off-by: Matthew McClintock
> ---
> arch/powerpc/platforms/85xx/smp.c | 50 +
> 1 files changed, 50 insertions(+), 0
On Sep 24, 2010, at 11:44 AM, Paul Gortmaker wrote:
>>
>> From d48ebb58b8214f9faec775a5e06902f638f165cf Mon Sep 17 00:00:00 2001
> From: Tiejun Chen
> Date: Tue, 21 Sep 2010 19:31:31 +0800
> Subject: [PATCH] powerpc: Fix invalid page flags in create TLB CAM path for
> PTE_64BIT
>
> There exis
On Sep 20, 2010, at 11:23 AM, Timur Tabi wrote:
> Register the __init and __exit functions in the PowerPC e500 watchdog driver
> as module entry/exit functions, and modify the Kconfig entry.
>
> Add a .release method for the PowerPC e500 watchdog driver, so that the
> watchdog is disabled when t
On Sep 16, 2010, at 5:58 PM, Matthew McClintock wrote:
> We no longer need to call this explicitly as a generic version is
> called by default
>
> Signed-off-by: Matthew McClintock
> ---
> arch/powerpc/platforms/85xx/smp.c |2 --
> 1 files changed, 0 insertions(+), 2 deletions(-)
applied to
On Aug 5, 2010, at 3:02 AM, Kumar Gala wrote:
> The following commit broke 83xx because it assumed the 83xx platforms
> exposed the "IMMR" address in BAR0 like the 85xx/86xx/QoriQ devices do:
>
> commit 3da34aae03d498ee62f75aa7467de93cce3030fd
> Author: Kumar Gala
> Date: Tue May 12 15:51:56
On Sep 8, 2010, at 6:55 PM, Ilya Yanok wrote:
> This patch adds support for MPC8308 P1M board.
> Supported devices:
> DUART
> Dual Ethernet
> NOR flash
> Both I2C controllers
> USB in peripheral mode
> PCI Express
>
> Signed-off-by: Ilya Yanok
> ---
>
> Changed 'compatible' entry for 'cpld' no
On Sep 16, 2010, at 5:58 PM, Matthew McClintock wrote:
> Make kexec_down_cpus atmoic since it will be incremented by all
> cores as they are coming down
>
> Remove duplicate calls to mpc85xx_smp_kexec_down, now it's called
> by the crash and normal kexec pathway only once
>
> Increase the timeo
On Sep 16, 2010, at 5:58 PM, Matthew McClintock wrote:
> Right now just the kexec crash pathway turns turns off the
> interrupts. Pull that out and make a generic version for
> use elsewhere
>
> Signed-off-by: Matthew McClintock
> ---
> arch/powerpc/include/asm/kexec.h |1 +
> arch/pow
On Sep 20, 2010, at 11:23 AM, Timur Tabi wrote:
> Export the global variable 'ppc_tb_freq', so that modules (like the Book-E
> watchdog driver) can use it. To maintain consistency, ppc_proc_freq is
> changed
> to a GPL-only export. This is okay, because any module that needs this symbol
> shou
On Sep 9, 2010, at 1:39 PM, Timur Tabi wrote:
> The device tree for Freescale's P1022DS reference board is missing the node
> for the ngPIXIS FPGA.
>
> Signed-off-by: Timur Tabi
> ---
> arch/powerpc/boot/dts/p1022ds.dts |9 +
> 1 files changed, 9 insertions(+), 0 deletions(-)
>
> di
On Sep 7, 2010, at 8:59 PM, Paul Mackerras wrote:
> On Tue, Sep 07, 2010 at 01:56:55PM -0500, Matthew McClintock wrote:
>
>> In lieu of having multiple similiar lines, we can just have one
>> generic cpu-as line for CONFIG_ALTIVEC
>>
>> ---
>> Was hoping to get comments about this change and if
On Sep 9, 2010, at 1:39 PM, Timur Tabi wrote:
> +static void p1022ds_set_monitor_port(int monitor_port)
> +{
> + struct device_node *pixis_node;
> + u8 __iomem *brdcfg1;
> +
> + pixis_node = of_find_compatible_node(NULL, NULL, "fsl,fpga-pixis");
> + if (!pixis_node) {
> +
On Tue, Oct 5, 2010 at 11:31 AM, Segher Boessenkool
wrote:
> An OS shouldn't expect to have more than its own program image
> RAM mapped, in general.
Linux actually makes calls to allocate more. I'm thankful
that Linux always specifies an address, so I was able to
get away with simply returning
I may have come across a similar problem, but I've never worked card-to-card
without at least one switch in the way.
The problems I have encountered have been hang-ups during memory-mapped
maintenance reads to devices that the switch reports as "up".
A workaround for the hang-up is to use a DMA
On Wed, 2010-10-06 at 07:35 -0700, Gorelik, Jacob (335F) wrote:
> UIC0 (32 IRQ sources) at DCR 0xc0
> UIC1 (32 IRQ sources) at DCR 0xd0
That looks bad. Your device-tree probably. Check the DCR bindings.
I'm on vacation right now, I don't have time to review it in details,
but ask me again next w
Hello,
In start_kernel function, locked_initial() is called; however, it does not do
anything. Is it not needed?
Thank you,
Jacob
On Oct 6, 2010, at 11:38 AM, "linuxppc-dev-requ...@lists.ozlabs.org"
wrote:
> Send Linuxppc-dev mailing list submissions to
>linuxppc-dev@lists.ozlabs.or
Create sysfs interface to export data from H_BEST_ENERGY hcall
that can be used by administrative tools on supported pseries
platforms for energy management optimizations.
/sys/device/system/cpu/pseries_(de)activate_hint_list and
/sys/device/system/cpu/cpuN/
These APIs take logical cpu number as input
Change cpu_first_thread_in_core() to cpu_first_thread_sibling()
Change cpu_last_thread_in_core() to cpu_last_thread_sibling()
These APIs convert core number (index) to logical cpu/thread numbers
Add cpu_first_thread_of_core(int core)
Changed cpu_thread_t
Hi Ben,
The following series adds a new kernel module for powerpc pseries
platforms in order to export platform energy management capabilities.
The module exports data from a new hypervisor call H_BEST_ENERGY.
Comments and suggestions made on the previous iteration of the
patch related to functi
On Wed, Oct 6, 2010 at 7:50 AM, Holger brunck wrote:
> Hello Heiko,
>
> On 10/06/2010 11:53 AM, Heiko Schocher wrote:
So, the question is, is there a possibility to solve this problem?
If there is no standard option, what would be with adding a
"scan_phy" file in
/pro
On Wed, Oct 6, 2010 at 3:53 AM, Heiko Schocher wrote:
> Hello Grant,
>
> Thanks for your answer!
>
> Grant Likely wrote:
>> On Mon, Oct 4, 2010 at 1:32 AM, Heiko Schocher wrote:
>>> Hello all,
>>>
>>> we have on the mgcoge arch/powerpc/boot/dts/mgcoge.dts 3 fs_enet
>>> devices. The first is acces
I'm trying to use an MPC8641D as a PCIe endpoint device, and I'm trying to
work out how the host root complex CPU can interrupt the PPC core. It's
not very clear how to do all of this, and I'd like some help fitting the
pieces together. If there's a good how-to online I've yet to find it.
As I rea
Hello,
I am trying to run linux on a custom PPC440GP board; however, something goes
wrong early in the boot process. I am not sure if the problem is in the device
tree or in the memory map.
I've attached the log and the config files.
Thank you,
Jacob
log.txt
Description: log.txt
auto.conf
D
Hello Grant,
Thanks for your answer!
Grant Likely wrote:
> On Mon, Oct 4, 2010 at 1:32 AM, Heiko Schocher wrote:
>> Hello all,
>>
>> we have on the mgcoge arch/powerpc/boot/dts/mgcoge.dts 3 fs_enet
>> devices. The first is accessible on boot, and so get correct
>> probed and works fine. For the
30 matches
Mail list logo
