From: "Pali Rohár" <pali.rohar@gmail.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: "Filip Matijević" <filip.matijevic.pz@gmail.com>,
sre@kernel.org, "kernel list" <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-omap@vger.kernel.org, tony@atomide.com, khilman@kernel.org,
aaro.koskinen@iki.fi, ivo.g.dimitrov.75@gmail.com,
patrikbachan@gmail.com, serge@hallyn.com, abcloriens@gmail.com,
clayton@craftyguy.net, martijn@brixit.nl,
sakari.ailus@linux.intel.com
Subject: Re: 4.13 (and probably all recent) kernels refuse to boot on one Nokia N950, work or another
Date: Thu, 26 Oct 2017 09:21:13 +0200 [thread overview]
Message-ID: <20171026072113.z5bqer7os62ckf3z@pali> (raw)
In-Reply-To: <20171026070815.GA20634@amd>
On Thursday 26 October 2017 09:08:15 Pavel Machek wrote:
> On Thu 2017-10-26 08:25:02, Filip Matijević wrote:
> > Last time I couldn't get output on serial I used CONFIG_DEBUG_LL,
> > CONFIG_DEBUG_OMAP3UART3, CONFIG_EARLY_PRINTK... and ignore_loglevel
> > earlyprintk kernel params to get output early enough - I guess you
> > already tried that.
>
> I realized I'm not getting output from the decompessor (even on "S"
> machine), and enabled that.
That is because you have not enabled those EARLY PRINK or DEBUG LL.
Similar thing is needed for N900 and IIRC in some of my linux-n900
branches I have config for it. Plus it needs patching some arch/arm
source files to make it working.
> But I'm _still_ not getting any output on decompressor... early
> printing works ok on "S" but not on "P".
I guess there can be either problem with memory mapping and RAM size or
with OMAP HS mode?
--
Pali Rohár
pali.rohar@gmail.com
next prev parent reply other threads:[~2017-10-26 7:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-25 20:34 4.13 (and probably all recent) kernels refuse to boot on one Nokia N950, work or another Pavel Machek
2017-10-25 21:28 ` Tony Lindgren
2017-10-25 21:34 ` Aaro Koskinen
2017-10-26 7:16 ` Pavel Machek
2017-10-26 7:34 ` Filip Matijević
2017-10-26 8:49 ` Pavel Machek
2017-10-26 9:13 ` Pavel Machek
2017-10-26 9:31 ` Sebastian Reichel
2017-10-26 9:57 ` Pavel Machek
2017-10-26 12:01 ` Sebastian Reichel
2017-10-26 16:28 ` Pavel Machek
2017-10-27 10:19 ` Pavel Machek
2017-10-27 12:58 ` Filip Matijević
2017-10-30 19:43 ` n950: mmc fails to work, omap_hsmmc 480b4000.mmc: RX DMA channel request failed ? was " Pavel Machek
2017-10-30 20:02 ` Pavel Machek
2017-10-27 20:27 ` Backlight on Nokia N900 " Pavel Machek
2017-10-30 7:51 ` Pavel Machek
2017-10-26 9:53 ` Pavel Machek
2017-10-26 6:25 ` Filip Matijević
2017-10-26 7:08 ` Pavel Machek
2017-10-26 7:21 ` Pali Rohár [this message]
2017-10-26 7:27 ` Pavel Machek
2017-10-26 7:32 ` Pali Rohár
2017-10-26 8:24 ` Pavel Machek
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=20171026072113.z5bqer7os62ckf3z@pali \
--to=pali.rohar@gmail.com \
--cc=aaro.koskinen@iki.fi \
--cc=abcloriens@gmail.com \
--cc=clayton@craftyguy.net \
--cc=filip.matijevic.pz@gmail.com \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=martijn@brixit.nl \
--cc=patrikbachan@gmail.com \
--cc=pavel@ucw.cz \
--cc=sakari.ailus@linux.intel.com \
--cc=serge@hallyn.com \
--cc=sre@kernel.org \
--cc=tony@atomide.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox