From: "Enrico Weigelt, metux IT consult" <enrico.weigelt@gr13.net>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] boot problem w/ barebox
Date: Wed, 13 Sep 2017 12:56:00 +0200 [thread overview]
Message-ID: <22271166-0ca6-22ad-6b0c-5318c7f9ed07@gr13.net> (raw)
In-Reply-To: <20170912083202.urfrvyewzddlghg6@pengutronix.de>
On 12.09.2017 10:32, Uwe Kleine-König wrote:
Hi,
> CONFIG_DEBUG_IMX_UART_PORT=2 means it should use UART-2 as documented in
> the reference manual. But yeah, this is confusing, the problem is that
> the hardware guy numbering the UARTS named the first UART UART-1 which
> isn't what a kernel hacker would have picked.
Perhaps we could add some notes in the description, so people
won't get confused anymore.
> When the UART tty driver are configured doesn't play a role here. At
> some point during boot all unused clocks are disabled and up to then no
> driver ensured your uart clock to be used.
The clock wasn't the only problem. I've hacked out that, so console
(printk) continued to work, but later on /dev/console couldn't be
opened (ENODEV). And this was due to missing tty device. See printk.c:
console_device().
>> * hacking out the clock disable lead further to the point where rootfs
>> is mounted and init started
>
> There is no need for a hack, just pass "clk_ignore_unused" on the kernel
> command line.
Wasn't aware of that yet. Thx.
--mtx
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2017-09-13 10:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-09 9:01 Enrico Weigelt, metux IT consult
2017-09-11 7:16 ` Uwe Kleine-König
2017-09-11 18:47 ` Enrico Weigelt, metux IT consult
2017-09-12 8:32 ` Uwe Kleine-König
2017-09-13 10:56 ` Enrico Weigelt, metux IT consult [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=22271166-0ca6-22ad-6b0c-5318c7f9ed07@gr13.net \
--to=enrico.weigelt@gr13.net \
--cc=ptxdist@pengutronix.de \
/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