LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: John Clark <jeclark2006@aim.com>
To: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: P1020 implementation crashes with "Data Cache Parity Error" on board derived from Freescale P1020Wlan eval board.
Date: Fri, 3 Jan 2014 14:10:20 -0800	[thread overview]
Message-ID: <E53B211E-0F37-40AA-B6E3-7539089DFD7A@aim.com> (raw)

I have a problem when booting the linux kernel using two cores of the =
P1020 Freescale ppc implementation.

I have found on the Freescale site one other person who has a similar =
problem and we both are using designed driver from the P1020Wlan 'eval' =
board.

I would like to know if others have this 'problem', and used the =
P1020Wlan as their hardware starting point, and what they did to =
overcome this problem.

Single core works fine. Further the original P1020Wlan board boots my =
'new' kernel, 3.10.15 from OpenWRT sources, 'just fine'.

The problem may be that we used a different DDR3 chip than the original =
eval, and some subtle difference in timing that needs some 'adjustment' =
has eluded me.

Thanks for any info/insight,

John Clark.

                 reply	other threads:[~2014-01-03 22:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=E53B211E-0F37-40AA-B6E3-7539089DFD7A@aim.com \
    --to=jeclark2006@aim.com \
    --cc=linuxppc-dev@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