From: Pavel Machek <pavel@ucw.cz>
To: Tony Lindgren <tony@atomide.com>
Cc: pali.rohar@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, 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, filip.matijevic.pz@gmail.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 11:53:43 +0200 [thread overview]
Message-ID: <20171026095343.GA31065@amd> (raw)
In-Reply-To: <20171026091325.GA26929@amd>
[-- Attachment #1: Type: text/plain, Size: 2021 bytes --]
On Thu 2017-10-26 11:13:26, Pavel Machek wrote:
> On Wed 2017-10-25 14:28:07, Tony Lindgren wrote:
> > * Pavel Machek <pavel@ucw.cz> [171025 13:36]:
> > > Hi!
> > >
> > > ...hardware should be identical. 3.5.3-nemo kernel seems to work on
> > > both. 4.13-rc2 with display and clock patches boots on phone "S", but
> > > does not on phone "P"; nothing nothing is received on serial port.
> > >
> > > There is some difference in the bootloaders: S's bootloader provides
> > > lots of debug info, P's is silent. R&D settings do _not_ have
> > > influence on bootloader. We know P's serial works, as 3.5.3 kernel
> > > prints "Uncompressing linux...booting" there.
> > >
> > > I'll need to return "S" phone and serial cable tommorow. If you have
> > > any ideas, let me know.
> >
> > If you get nothing out of the uart, chances are the pins are
> > not muxed for the uart in nolo and maybe kernel dts is missing the
> > pinctrl entries for uart?
> >
> > Also try booting with mem=512M@0x80000000 or 256M or 768M. Maybe the
> > memory is different size or partially broken?
>
> Uhuh. It looks like "P" nokia really wants initrd, otherwise it will
> not boot.
No. Nokia "P" really hates command line on 0xffff command line. initrd
is optional. It also forces delay on "Warning! You have modified"
... screen.
I configured serial port. Now I get up-to working userspace (initrd)
on both "S" and "P" devices.
Welcome to MOSLO vNEMO_MOSLO-N9_0.0.13.2
Could not ioctl(OMAPFB_UPDATE_WINDOW): Inappropriate ioctl for device
check wiki.merproject.org/wiki/Nemo
Could not ioctl(OMAPFB_UPDATE_WINDOW): Inappropriate ioctl for device
Could not ioctl(OMAPFB_UPDATE_WINDOW): Inappropriate ioctl for device
Waiting for eMMC device...
Could not ioctl(OMAPFB_UPDATE_WINDOW): Inappropriate ioctl for device
eMMC device not found!
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-10-26 9:53 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 [this message]
2017-10-26 6:25 ` Filip Matijević
2017-10-26 7:08 ` Pavel Machek
2017-10-26 7:21 ` Pali Rohár
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=20171026095343.GA31065@amd \
--to=pavel@ucw.cz \
--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=pali.rohar@gmail.com \
--cc=patrikbachan@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).