From: rob.herring@calxeda.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: serial tty name
Date: Wed, 14 Dec 2011 09:31:59 -0600 [thread overview]
Message-ID: <4EE8C16F.8060501@calxeda.com> (raw)
In-Reply-To: <20111214144344.GA2090@richard-laptop>
Richard,
On 12/14/2011 08:43 AM, Richard Zhao wrote:
> How to map different uart port to ttymxc0 (take imx for example)?
>
> In rootfs, it usually "getty ttymxc0" to get
> serial console. And the rootfs may be shared by different boards.
> Traditionaly way is to set right platform device ID.
>
> But with DT, UART2 always generate ttymxc1, UART3 for ttymxc2. You
> always needs to modify the getty command when your change another board.
>
> Is there a way to fix it?
That's what the aliases are for.
Rob
next prev parent reply other threads:[~2011-12-14 15:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 14:43 serial tty name Richard Zhao
2011-12-14 15:10 ` Igor Grinberg
2011-12-14 18:33 ` Uwe Kleine-König
2011-12-15 0:44 ` Richard Zhao
2011-12-14 15:31 ` Rob Herring [this message]
2011-12-15 0:31 ` Richard Zhao
2011-12-19 4:08 ` Shawn Guo
2011-12-19 4:49 ` Jason Liu
2011-12-19 5:41 ` Richard Zhao
2011-12-19 3:56 ` Shawn Guo
2011-12-19 5:40 ` Richard Zhao
2011-12-19 6:05 ` Shawn Guo
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=4EE8C16F.8060501@calxeda.com \
--to=rob.herring@calxeda.com \
--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