Messages in this thread | | | From | Grant Likely <> | Subject | Re: [RFC 1/5] of: Add support for ePAPR "stdout-path" property | Date | Fri, 28 Mar 2014 17:30:50 -0700 |
| |
On Sat, 29 Mar 2014 08:33:16 +1100, Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote: > On Fri, 2014-03-28 at 09:08 -0700, Grant Likely wrote: > > ePAPR 1.1 defines the "stdout-path" property for specifying the console > > device, but Linux currently only handles the older "linux,stdout-path" > > property. This patch adds parsing for the new property name. > > Generally a good idea I think, but of course I need time to review and > test ... :-) > > One thing that's been annoying me lately with the existing code which > you don't address is ... in a few cases my consoles are usable *VERY* > early. For example PAPR hvc and OPAL hvc can be used before we even turn > the MMU on on powerpc (and thus before we unflatten the device-tree). > > It would be nice to be able to have the console going that early, > unfortunately that would imply using the flat device-tree for the > parsing / matching of the stdout-path in those drivers.
I think we can get that done. Rob's series goes a long way to that, and I don't think the flattree parsing will be all that complex.
g.
| |