Hi Paul,
On (11/03/16 21:17), Paul Burton wrote:
> > [..]
> > > + * The device tree stdout-path chosen node property was
> > > + * specified so we don't want to enable the first
> > > + * registered console just now in order to give the
> > > + * device indicated by stdout-path a chance to be
> > > + * registered first. Do however keep track of the
> > > + * first console we see so that we can fall back to
> > > + * using it if we don't see the desired device, either
> > > + * because stdout-path isn't valid, or because we have
> > > + * no driver for the device or our driver doesn't call
> > > + * of_console_check(). See printk_late_init() for this
> > > + * fallback.
> >
> > if the path is not valid then correct the path. no?
>
> ...but what if the path is valid and we simply don't have a driver for the
> device it references? As I said in that comment we may not have a driver at
> all.
well, I suppose, in this case normally one would go and enable the
missing .config option. no?
-ss
