linux-kernel - [RFC 0/5] of: Automatic console registration cleanups

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1396022885-6102-1-git-send-email-grant.likely@linaro.org>
Date:	Fri, 28 Mar 2014 09:08:00 -0700
From:	Grant Likely <grant.likely@...aro.org>
To:	devicetree@...r.kernel.org, christoffer.dall@...aro.org,
	linux-kernel@...r.kernel.org, olof@...om.net,
	benh@...nel.crashing.org, rob.herring@...aro.org
Subject: [RFC 0/5] of: Automatic console registration cleanups

Hi all,

This is a series that I've been playing with over the last few days to
clean up the selection of default console devices when using the device
tree. The device tree defines a way of specifying the console by using a
"stdout-path" property in the /chosen node, but very few drivers
actually attempt to use that data, and so for most platforms there needs
to be a "console=" line in the command line if a serial port is intended
to be used as the console.

With this series, if there is a /chosen/stdout-path property, and if
that property points to a serial port node, then when the serial driver
registers the port, the core uart_add_one_port() function will notice
and if no console= argument was provided then add it as a preferred
console.

I've not tested this very extensively yet, but I want to get some
feedback before I go further.

The one downside with this approach is that it doesn't do anything for
early console setup. That still needs to be added on a per-driver basis,
but at least it shouldn't conflict with this approach.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/