public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman•id.au>
To: 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>,
	oss@buserror•net
Subject: Re: udgb on fsl booke?
Date: Mon, 16 May 2016 11:40:19 +1000	[thread overview]
Message-ID: <1463362819.5704.8.camel@ellerman.id.au> (raw)
In-Reply-To: <57367455.5060306@cisco.com>

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.

cheers

  reply	other threads:[~2016-05-16  1:40 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 [this message]
2016-05-16  2:46   ` Scott Wood

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=1463362819.5704.8.camel@ellerman.id.au \
    --to=mpe@ellerman$(echo .)id.au \
    --cc=danielwa@cisco$(echo .)com \
    --cc=galak@kernel$(echo .)crashing.org \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    --cc=oss@buserror$(echo .)net \
    --cc=xe-kernel@external$(echo .)cisco.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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