From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: Kernel 3.4 on Dreamplug: no serial console
Date: Mon, 4 Jun 2012 14:30:59 +0000 [thread overview]
Message-ID: <201206041430.59397.arnd@arndb.de> (raw)
In-Reply-To: <2396575.dLS9zmzUSD@flexo>
On Monday 04 June 2012, Florian Fainelli wrote:
> On Sunday 03 June 2012 14:40:49 Jason Cooper wrote:
> > On Sun, Jun 03, 2012 at 05:12:18PM +0000, Arnd Bergmann wrote:
> > > I'd also accept a patch to make ARCH_KIRKWOOD_DT select OF_SERIAL if
> people
> > > prefer that, but I think just changing the defconfig is better.
> >
> > I'd prefer the defconfig as there are situations where users/oems deploy
> > a kernel without support for serial console. In order to do that with
> > your patch, or similar approaches, they would have to change the code.
> > With defconfig, they don't.
>
> Should not you rather select OF_SERIAL and add a status propery to the uart
> node in device tree, so that it is up to dtb provider to determine whether
> this device node should be enabled or not? You would avoid all kind of
> defconfig issue.
Obviously the configuration comes from DT, but there are still reasons to
not select the driver. E.g. you might want to build a kernel that runs on
a wide variety of systems and has all drivers as loadable modules rather than
built-in. There are also some systems that are rather memory constraint and
even disable printk support, so the console becomes useless too.
Arnd
next prev parent reply other threads:[~2012-06-04 14:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-02 12:20 Kernel 3.4 on Dreamplug: no serial console Hans Kröner
2012-06-02 15:18 ` Adam Baker
2012-06-03 15:26 ` Hans Kröner
2012-06-03 16:59 ` Adam Baker
2012-06-03 17:12 ` Arnd Bergmann
2012-06-03 18:40 ` Jason Cooper
2012-06-03 19:09 ` Andrew Lunn
2012-06-04 8:29 ` Florian Fainelli
2012-06-04 14:30 ` Arnd Bergmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-06-02 18:57 Andrew Lunn
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=201206041430.59397.arnd@arndb.de \
--to=arnd@arndb.de \
--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.