public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: Armada XP Internal registers
Date: Wed, 6 Nov 2013 15:38:53 +0100	[thread overview]
Message-ID: <20131106153853.0564e22e@skate> (raw)
In-Reply-To: <CAFJTrDv_UdSP9hxAgrXa2Z6p1HFK0WnbQO=csKh8-EL9yUEvqQ@mail.gmail.com>

Dear Matthew Minter,

On Wed, 6 Nov 2013 14:31:49 +0000, Matthew Minter wrote:

> Thanks for the clarification regarding this CP15 bit, I saw various
> documentation mentioning it and had assumed it had been implemented. I
> understand the issue now and also understand why there is a difference
> between the easiest solution and the most elegant.

I believe the CP15 bit solution might have showed up in some Marvell
U-Boot versions, since it was part of our plan to use that, but our
plan failed :)

> However now I understand the issue that is no longer a problem, the
> other half of my email was regarding issues I was having booting using
> a certain, seemingly briefly available version of Marvell's Q2 2013
> u-boot which was causing the kernel to read spurious interrupts and a
> particular "Unhandled fault: external abort on non-linefetch" problem
> which would cause the kernel to panic during the boot process, usually
> during PCI initialisation. However it seems that the problem was due
> to a bug in the version of uboot and has now been patched by Marvell
> and was not an issue with the kernel after all. This at least seems to
> be the case as the patched u-boot allows the previously problematic
> kernel's to boot fine.
> 
> Ultimately I think it is a non issue as it was not (to my
> understanding) a kernel issue in the first place, sorry.

Sure, no problem, thanks for getting back to us about this!

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

       reply	other threads:[~2013-11-06 14:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAFJTrDv_UdSP9hxAgrXa2Z6p1HFK0WnbQO=csKh8-EL9yUEvqQ@mail.gmail.com>
2013-11-06 14:38 ` Thomas Petazzoni [this message]
2013-10-21 14:47 Armada XP Internal registers Matthew Minter
2013-10-21 14:59 ` Matthew Minter
2013-10-21 17:43 ` Ezequiel Garcia
2013-10-21 18:42   ` Jason Cooper
2013-10-22 13:29     ` Thomas Petazzoni
2013-10-22 15:56       ` Matthew Minter
2013-10-22 16:11         ` Thomas Petazzoni
     [not found]           ` <CAFJTrDsaq-NjLhcwHBuN1Q_zu-Q-yJkWLMUER1zVzc1=AFNM=Q@mail.gmail.com>
2013-11-06 14:19             ` Thomas Petazzoni

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=20131106153853.0564e22e@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=linux-arm-kernel@lists.infradead.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