From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: dts: sun8i: enable UART1 for iNet D978 Rev2 board
Date: Thu, 25 Aug 2016 22:47:26 +0200 [thread overview]
Message-ID: <20160825204726.GH32598@lukather> (raw)
In-Reply-To: <116041472134355@web12g.yandex.ru>
On Thu, Aug 25, 2016 at 10:12:35PM +0800, Icenowy Zheng wrote:
> >> ?But many codes will require a ttyS0 as console... So I think the
> >> ?bluetooth should be located at ttyS1...
> >
> > Most of them would use /dev/console anyway. What do you have in mind?
>
> As a general configuration, /dev/ttyS0 will be indicated as the default console=
> value... (Otherwise more boards will fail)
There's no reason to make that assumption. The console might be on
another UART entirely (ttyS3, for the sake of the argument), on a
different UART "class" (ttyUSB?, framebuffer console?), or not present
at all.
If you want to use the console, use /dev/console.
I don't what's so special about the UART here. Every single device in
Linux behaves that way.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160825/a14fdef5/attachment-0001.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Icenowy Zheng <icenowy@aosc.xyz>
Cc: Mark Rutland <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Russell King <linux@armlinux.org.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Hans de Goede <hdegoede@redhat.com>, Chen-Yu Tsai <wens@csie.org>,
Rob Herring <robh+dt@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 2/2] ARM: dts: sun8i: enable UART1 for iNet D978 Rev2 board
Date: Thu, 25 Aug 2016 22:47:26 +0200 [thread overview]
Message-ID: <20160825204726.GH32598@lukather> (raw)
In-Reply-To: <116041472134355@web12g.yandex.ru>
[-- Attachment #1.1: Type: text/plain, Size: 880 bytes --]
On Thu, Aug 25, 2016 at 10:12:35PM +0800, Icenowy Zheng wrote:
> >> But many codes will require a ttyS0 as console... So I think the
> >> bluetooth should be located at ttyS1...
> >
> > Most of them would use /dev/console anyway. What do you have in mind?
>
> As a general configuration, /dev/ttyS0 will be indicated as the default console=
> value... (Otherwise more boards will fail)
There's no reason to make that assumption. The console might be on
another UART entirely (ttyS3, for the sake of the argument), on a
different UART "class" (ttyUSB?, framebuffer console?), or not present
at all.
If you want to use the console, use /dev/console.
I don't what's so special about the UART here. Every single device in
Linux behaves that way.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Icenowy Zheng <icenowy@aosc.xyz>
Cc: Chen-Yu Tsai <wens@csie.org>,
Russell King <linux@armlinux.org.uk>,
Hans de Goede <hdegoede@redhat.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] ARM: dts: sun8i: enable UART1 for iNet D978 Rev2 board
Date: Thu, 25 Aug 2016 22:47:26 +0200 [thread overview]
Message-ID: <20160825204726.GH32598@lukather> (raw)
In-Reply-To: <116041472134355@web12g.yandex.ru>
[-- Attachment #1: Type: text/plain, Size: 880 bytes --]
On Thu, Aug 25, 2016 at 10:12:35PM +0800, Icenowy Zheng wrote:
> >> But many codes will require a ttyS0 as console... So I think the
> >> bluetooth should be located at ttyS1...
> >
> > Most of them would use /dev/console anyway. What do you have in mind?
>
> As a general configuration, /dev/ttyS0 will be indicated as the default console=
> value... (Otherwise more boards will fail)
There's no reason to make that assumption. The console might be on
another UART entirely (ttyS3, for the sake of the argument), on a
different UART "class" (ttyUSB?, framebuffer console?), or not present
at all.
If you want to use the console, use /dev/console.
I don't what's so special about the UART here. Every single device in
Linux behaves that way.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-08-25 20:47 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 6:44 [PATCH 0/2] Add support for iNet D978 Rev2 board Icenowy Zheng
2016-08-23 6:44 ` Icenowy Zheng
2016-08-23 6:44 ` [PATCH 1/2] ARM: dts: sun8i: Add dts file for inet-d978_rev2 tablets Icenowy Zheng
2016-08-23 6:44 ` Icenowy Zheng
2016-08-24 19:32 ` Maxime Ripard
2016-08-24 19:32 ` Maxime Ripard
2016-08-24 19:32 ` Maxime Ripard
2016-08-24 23:57 ` Icenowy Zheng
2016-08-24 23:57 ` Icenowy Zheng
2016-08-25 7:35 ` Maxime Ripard
2016-08-25 7:35 ` Maxime Ripard
2016-08-25 7:35 ` Maxime Ripard
2016-08-23 6:44 ` [PATCH 2/2] ARM: dts: sun8i: enable UART1 for iNet D978 Rev2 board Icenowy Zheng
2016-08-23 6:44 ` Icenowy Zheng
2016-08-24 19:36 ` Maxime Ripard
2016-08-24 19:36 ` Maxime Ripard
2016-08-24 19:36 ` Maxime Ripard
2016-08-24 23:58 ` Icenowy Zheng
2016-08-24 23:58 ` Icenowy Zheng
2016-08-25 4:40 ` Chen-Yu Tsai
2016-08-25 4:40 ` Chen-Yu Tsai
2016-08-25 4:40 ` Chen-Yu Tsai
2016-08-25 6:57 ` Icenowy Zheng
2016-08-25 6:57 ` Icenowy Zheng
2016-08-25 8:03 ` Maxime Ripard
2016-08-25 8:03 ` Maxime Ripard
2016-08-25 8:03 ` Maxime Ripard
2016-08-25 14:12 ` Icenowy Zheng
2016-08-25 14:12 ` Icenowy Zheng
2016-08-25 14:17 ` Hans de Goede
2016-08-25 14:17 ` Hans de Goede
2016-08-25 14:17 ` Hans de Goede
2016-08-25 14:53 ` Icenowy Zheng
2016-08-25 14:53 ` Icenowy Zheng
2016-08-25 15:13 ` Hans de Goede
2016-08-25 15:13 ` Hans de Goede
2016-08-25 15:13 ` Hans de Goede
2016-08-25 15:29 ` Icenowy Zheng
2016-08-25 15:29 ` Icenowy Zheng
2016-08-25 14:53 ` Icenowy Zheng
2016-08-25 14:53 ` Icenowy Zheng
2016-08-25 20:47 ` Maxime Ripard [this message]
2016-08-25 20:47 ` Maxime Ripard
2016-08-25 20:47 ` Maxime Ripard
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=20160825204726.GH32598@lukather \
--to=maxime.ripard@free-electrons.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.