linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "tiejun.chen" <tiejun.chen@windriver.com>
To: Stephen Horton <SHorton@kodiaknetworks.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Marvell mv64462 + mpc744x PCI Interrupt Cause Error Handling
Date: Wed, 03 Dec 2008 09:52:27 +0800	[thread overview]
Message-ID: <4935E65B.30305@windriver.com> (raw)
In-Reply-To: <295C5089A56CE143B316E5F67CA99CB001F4389F@cowboy.inovate.inovate.com>

Stephen Horton wrote:
> Hi folks,
> 
>  
> 
> I'm really hoping Mark Greer or Dale Farnsworth sees this email. In my
> current project, we are in the process of updating a board that has a
> Marvell mv64462 system controller and a Freescale mpc7447A processor on
> it. The board was originally developed with Gentoo Linux 2.6.9, but we
> have ported Linux 2.6.24 kernel onto it. The new kernel is working well
> thanks to help from people on this list. However, in examining the
> differences between the 2 kernels, I can see that the 2.6.24 kernel
> registers no interrupt error handling routines (see PCI Error Report
> Register Map in the Marvell documentation). The error handlers for cpu,
> sram, and specifically for the PCI bus that were previously in:
> 
>             /arch/ppc/syslib/mv64460_pic.c
> 
> are absent from:
> 
>             /arch/powerpc/sysdev/mv64x60_pic.c
> 
>  
> 
> Can someone who is familiar with the history of the ppc->powerpc
> migration for this architecture help me figure out why the error
> handling wasn't ported over? Is there some reason for this, such as it
> didn't work properly or had some disadvantages? Is this error handling
> done in 2.6.24 in some more generic manner that I have not yet found? Is
> this an exercise left for me to implement?
> 
>  

Untill v2.6.27 you can find corresponding dts content such as cpu-error,
sram-ctrl, pci-error and mem-ctrl, in file, prpmc2800.dts. All events are
handled on EDAC, error detection and reporting, as an unified mode. So you can
track the directory drivers/edac/ for more information. I think these are not
upgraded completely for v2.6.24.

Best Regards
Tiejun

> 
> Thanks,
> 
> Stephen
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded

  reply	other threads:[~2008-12-03  1:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-02 23:28 Marvell mv64462 + mpc744x PCI Interrupt Cause Error Handling Stephen Horton
2008-12-03  1:52 ` tiejun.chen [this message]
2008-12-03 21:06   ` Stephen Horton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4935E65B.30305@windriver.com \
    --to=tiejun.chen@windriver.com \
    --cc=SHorton@kodiaknetworks.com \
    --cc=linuxppc-embedded@ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).