All of lore.kernel.org
 help / color / mirror / Atom feed
From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: PB1176 broken in -rc1
Date: Tue, 16 Aug 2011 11:21:50 +0200	[thread overview]
Message-ID: <CACRpkdaoDJy-YKONaz2j07pPvTZuHZ7KgEm6XGxNXK-jNzB8_w@mail.gmail.com> (raw)
In-Reply-To: <20110810152400.GO10121@e102144-lin.cambridge.arm.com>

On Wed, Aug 10, 2011 at 5:24 PM, Will Deacon <will.deacon@arm.com> wrote:

> Hi Linus,
>
> My PB1176 platform appears to lock up as soon as it hits userspace when
> running a 3.1-rc1 kernel.

My kernel does not even boot on either -rc1 or -rc2 on the
PB1176, with or wthout Jamies poisoning fixup.

Did you change anything else on top of -rc1 when you tested this?

Will, Jamie, any hints?

If I cherry-pick my TCM patches adding PB1176 support to a clean
v3.0 branch, everything works fine, so I suspect I am not guilty for
this AFAICT, it's something else.

Also the -rc2 code works fine on U300 which has a TCM,
ARM926-EJS.

P.S. By the way regarding this:

> [ ? ?0.000000] CPU: found DTCM0 4k @ 00000000, not enabled
> [ ? ?0.000000] CPU: moved DTCM0 4k to fffe8000, enabled
> [ ? ?0.000000] CPU: found DTCM1 4k @ 00000000, not enabled
> [ ? ?0.000000] CPU: moved DTCM1 4k to fffe9000, enabled
> [ ? ?0.000000] CPU: found ITCM0 4k @ 00000000, not enabled
> [ ? ?0.000000] CPU: moved ITCM0 4k to fffe0000, enabled
> [ ? ?0.000000] CPU: found ITCM1 4k @ 00000000, not enabled
> [ ? ?0.000000] CPU: moved ITCM1 4k to fffe1000, enabled

[Will]
> The NULL addresses in the dmesg look
> strange to me, but I'm not familiar with the TCMs.

This looks perfectly normal. The TCMs are default disabled and mapped
to address 0x00000000, I activate them and move them to our desired
location.

Thanks,
Linus Walleij

  parent reply	other threads:[~2011-08-16  9:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-10 15:24 PB1176 broken in -rc1 Will Deacon
2011-08-10 15:39 ` Jamie Iles
2011-08-10 15:53   ` Will Deacon
2011-08-11 13:02     ` Linus Walleij
2011-08-11 14:05 ` Linus Walleij
2011-08-11 14:24   ` Will Deacon
2011-08-16  9:21 ` Linus Walleij [this message]
2011-08-16  9:26   ` Will Deacon
2011-08-16  9:35     ` Linus Walleij
2011-08-16  9:59       ` Will Deacon
2011-08-16 10:09         ` Russell King - ARM Linux
2011-08-16 10:17           ` Will Deacon
2011-08-16 11:34             ` Russell King - ARM Linux
2011-08-16 21:38               ` Will Deacon
2011-08-16 12:44         ` Linus Walleij
2011-08-16 12:52           ` Russell King - ARM Linux
2011-08-16  9:28   ` Jamie Iles
2011-08-16  9:50     ` Jamie Iles

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=CACRpkdaoDJy-YKONaz2j07pPvTZuHZ7KgEm6XGxNXK-jNzB8_w@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.