Re: [Xen-devel] [RFC 6/6] xen/arm: Replace early_printk call to printk call

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Wed, 2014-02-19 at 17:56 +0000, Julien Grall wrote:
> Hi Ian,
> 
> On 02/19/2014 11:20 AM, Ian Campbell wrote:
> > On Sun, 2014-01-05 at 21:26 +0000, Julien Grall wrote:
> >> Now that the console supports earlyprintk, we can get a rid of
> >> early_printk call.
> >>
> >> Signed-off-by: Julien Grall <julien.grall@xxxxxxxxxx>
> > 
> > Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx>
> 
> Thanks, due to some conflicts I have rebased this patch on top my patch
> "xen/serial: Don't leak memory mapping if the serial initialization has
> failed".
> 
> I will resend this series later.

Thanks.

> > Now all we need is a way to make it a runtime option :-)
> 
> I let you write a device tree parser in assembly ;).

;-)

I was actually thinking more along the lines of a .word at a defined
offset which you could hex edit to a specific value to activate a
particular flavour of early printk handling. That would be sufficient
e.g. for osstest to activate the appropriate stuff for the specific
platform.

TBH I'm not sure a dumb DTB parser which just runs through looking for a
single property on a particular node would be all that hard, but I'm not
all that keen to find out for sure ;-)

Ian.


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel