All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Nicolas Pitre <nicolas.pitre@linaro.org>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Lists Linaro-dev <linaro-dev@lists.linaro.org>,
	Stephen Warren <swarren@nvidia.com>,
	Kevin Hilman <khilman@ti.com>, Jamie Iles <jamie@jamieiles.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org,
	Srinidhi KASAGAR <srinidhi.kasagar@stericsson.com>,
	Rabin VINCENT <rabin.vincent@stericsson.com>
Subject: Re: linux-next not booting on snowball
Date: Wed, 14 Dec 2011 16:27:19 +0800	[thread overview]
Message-ID: <20111214082718.GC3072@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CACRpkda_EzSbYAmeXQz1XjwKLfmV6JiDcC=4+4HiABWRVg2UPw@mail.gmail.com>

On Wed, Dec 14, 2011 at 09:24:33AM +0100, Linus Walleij wrote:

> The above remaps and reads from some random ROM page to get
> the ASIC ID is actually not screwing things up. Right now.

The ASIC ID reads are also done by Samsung platforms which boot fine -
it's not strictly good but it happens to work (and has done for some
considerable time).

  reply	other threads:[~2011-12-14  8:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-01 14:51 linux-next not booting on snowball Daniel Lezcano
     [not found] ` <4ED79454.1090304-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2011-12-01 14:58   ` Mark Brown
2011-12-01 15:34     ` Daniel Lezcano
2011-12-01 19:03       ` Nicolas Pitre
2011-12-01 23:06         ` Daniel Lezcano
2011-12-02  0:11           ` Nicolas Pitre
2011-12-02 17:31             ` Daniel Lezcano
2011-12-07  4:09               ` Nicolas Pitre
2011-12-13 12:35                 ` Linus Walleij
2011-12-14  8:24                   ` Linus Walleij
2011-12-14  8:27                     ` Mark Brown [this message]
2011-12-14  8:38                       ` Linus Walleij
2011-12-12 15:41               ` Daniel Lezcano
2011-12-12 16:56                 ` Nicolas Pitre

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=20111214082718.GC3072@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=jamie@jamieiles.com \
    --cc=khilman@ti.com \
    --cc=linaro-dev@lists.linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-next@vger.kernel.org \
    --cc=nicolas.pitre@linaro.org \
    --cc=rabin.vincent@stericsson.com \
    --cc=sfr@canb.auug.org.au \
    --cc=srinidhi.kasagar@stericsson.com \
    --cc=swarren@nvidia.com \
    /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.