From: Scott Wood <oss@buserror.net>
To: Michael Ellerman <mpe@ellerman.id.au>,
Daniel Walker <danielwa@cisco.com>,
linuxppc-dev@ozlabs.org,
"xe-kernel@external.cisco.com" <xe-kernel@external.cisco.com>,
Kumar Gala <galak@kernel.crashing.org>
Subject: Re: udgb on fsl booke?
Date: Sun, 15 May 2016 21:46:20 -0500 [thread overview]
Message-ID: <1463366780.16584.118.camel@buserror.net> (raw)
In-Reply-To: <1463362819.5704.8.camel@ellerman.id.au>
On Mon, 2016-05-16 at 11:40 +1000, Michael Ellerman wrote:
> On Fri, 2016-05-13 at 17:41 -0700, Daniel Walker wrote:
>
> > Hi,
> >
> > I noticed that udbg is missing for fsl booke , or at least it doesn't
> > appear to be implemented. I don't know a great deal about fsl book. I'm
> > working on an MCP85XX at the moment , and I was looking into the udbg
> > system to get prints. It looks like fsl booke might be similar enough to
> > 44x to use the already implemented udbg routines for that.
> >
> > Does anyone have suggestion on this ? Is fsl booke missing because it's
> > not possible to have this, or no one ever needed it ?
>
> Yeah I noticed this recently too.
>
> I don't know the history of why there isn't one, I suspect probably it just
> was
> never merged upstream. Hopefully someone from Freescale can chime in.
>
> On my machine (p5020ds) there is a real UART, so it should just be a matter
> of
> creating a mapping for it and then using the existing udbg_16550 code.
We don't have udbg support for these chips anywhere. I usually just dump the
logbuffer from an external debugger (or bisect with a branch-to-self using the
external debugger to see if it was reached, if the logbuffer is empty) when
there's a boot problem. It'd be nice to have; it just never got done.
-Scott
prev parent reply other threads:[~2016-05-16 3:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-14 0:41 udgb on fsl booke? Daniel Walker
2016-05-16 1:40 ` Michael Ellerman
2016-05-16 2:46 ` Scott Wood [this message]
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=1463366780.16584.118.camel@buserror.net \
--to=oss@buserror.net \
--cc=danielwa@cisco.com \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=xe-kernel@external.cisco.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).