linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: johannes@sipsolutions.net (Johannes Berg)
To: linux-arm-kernel@lists.infradead.org
Subject: MTK mt8173-evb: mainline unstable, and big-endian boot failures
Date: Thu, 28 Jan 2016 10:37:09 +0100	[thread overview]
Message-ID: <1453973829.2217.0.camel@sipsolutions.net> (raw)
In-Reply-To: <CAF-23O2y7qRB=ZoU8cn2gcX7rjFdXh+rdLXSjF1nnym79Mknug@mail.gmail.com> (sfid-20160128_103122_810896_2EF40B14)

On Thu, 2016-01-28 at 17:31 +0800, Koan-Sin Tan wrote:
>?
> > I have yet to debug this any further, but still wanted to report it
> > in case anyone else has the time to debug it further.
> bisect showed that the culprit of the big endian problem is a
> "regmap-mmio: Use native endianness for read/write"
> patch [1]. I saw Johannes already proposed to revert it [2].
> 

Mark has real fixes for it instead:
https://git.kernel.org/cgit/linux/kernel/git/broonie/regmap.git/log/?h=fix/mmio

johannes

      parent reply	other threads:[~2016-01-28  9:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-28  0:55 MTK mt8173-evb: mainline unstable, and big-endian boot failures Kevin Hilman
2016-01-28  1:16 ` Kevin Hilman
     [not found]   ` <CAF-23O3ps0Wt_UCmJbArpc5iJJryJKA0k_2qAyNb7op8O=UnAg@mail.gmail.com>
2016-01-28  6:56     ` Eddie Huang
2016-01-30  0:09       ` Kevin Hilman
2016-02-01  6:49         ` Eddie Huang
2016-02-02  1:17           ` Kevin Hilman
2016-02-02  2:17             ` Fan Chen
2016-02-02 18:46               ` Kevin Hilman
2016-02-03  1:38                 ` Fan Chen
2016-02-03  6:44                   ` Kevin Hilman
     [not found] ` <CAF-23O2y7qRB=ZoU8cn2gcX7rjFdXh+rdLXSjF1nnym79Mknug@mail.gmail.com>
2016-01-28  9:37   ` Johannes Berg [this message]

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=1453973829.2217.0.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --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;
as well as URLs for NNTP newsgroup(s).