linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@armlinux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Linux 4.7 and Jornada 720 (SA-1100)
Date: Fri, 19 Aug 2016 14:26:50 +0100	[thread overview]
Message-ID: <20160819132650.GO1041@n2100.armlinux.org.uk> (raw)
In-Reply-To: <7Tcq9hpfIfmjNv8%gof@news.chmurka.net>

On Fri, Aug 19, 2016 at 01:11:13PM +0000, Adam Wysocki wrote:
> Russell King - ARM Linux <linux@armlinux.org.uk> wrote:
> 
> > Make sure you have "console=ttySA0,38400n8" or similar to get serial
> > console output - it needs to be a "ttySA" port, not "ttyS".
> 
> Hmm... I changed to:
> 
> root=0x302 mem=32m console=ttySA0,115200n8
> 
> and success - it helped! The screen is still blank, but I least I have 
> some messages on the serial port, finished with kernel panic because of 
> failing to mount root. It looks like I didn't enable some drivers for 
> the CF controller, but I look and it seems everything that should be 
> enabled is enabled... maybe this kernel doesn't support CF on Jornada 
> without a patch?
> 
> http://pastebin.com/J2ATKxQM
> 
> And I'm just wondering why the screen is blank while I definitely enabled 
> the SA-1100 framebuffer support and console on framebuffer... I'm not sure 
> if it should be blank when I specified console=ttySA0, but I don't think 
> it should be blank without any console= setting...

Looking at the board file, the jornada720 doesn't use sa11x0-fb at all.
It uses an Epson s1d13xxx device.  The defconfig for jornada720 has:

CONFIG_FB_S1D13XXX=y

so if your configuration is derived from that, you should have the
driver already enabled.

> > Same probably goes for "earlyprintk=serial,ttyS0,115200", although I've
> > no experience of earlyprintk myself.
> 
> It seems that earlyprintk is ignored anyway, maybe there's no support for 
> it on this platform?

No idea, sorry.  I use my printascii() hack in printk() when I need early
or lowlevel debugging rather than early printk.

> > However, if you're not even getting the "Uncompressing Linux... done, 
> > booting the kernel." line, that suggests the decompressor is not running, 
> > or is trying to access the wrong serial port.  The decompressor tries to 
> > find the first serial port out of serial 3, 1 and 2 which has been left 
> > enabled.
> 
> In this order? Maybe it tries to send its messages to the built-in modem 
> or IrDA port...

Yes, that order.

-- 
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.

  reply	other threads:[~2016-08-19 13:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-18 14:05 Linux 4.7 and Jornada 720 (SA-1100) Adam Wysocki
2016-08-19 10:29 ` Russell King - ARM Linux
2016-08-19 13:11   ` Adam Wysocki
2016-08-19 13:26     ` Russell King - ARM Linux [this message]
2016-08-19 14:33       ` Adam Wysocki
2016-08-19 15:18         ` Russell King - ARM Linux
2016-08-24 13:34           ` Adam Wysocki
2016-08-24 14:52             ` Adam Wysocki

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=20160819132650.GO1041@n2100.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --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).