From: Michael Ellerman <michael@ellerman.id.au>
To: Dale Farnsworth <dale@farnsworth.org>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] powerpc: Add Marvell mv64x60 udbg putc/getc functions
Date: Fri, 08 Jun 2007 12:15:15 +1000 [thread overview]
Message-ID: <1181268915.6026.5.camel@concordia.ozlabs.ibm.com> (raw)
In-Reply-To: <20070606172900.GA29951@xyzzy.farnsworth.org>
[-- Attachment #1: Type: text/plain, Size: 1749 bytes --]
On Wed, 2007-06-06 at 10:29 -0700, Dale Farnsworth wrote:
> On Wed, Jun 06, 2007 at 04:06:05PM +1000, Paul Mackerras wrote:
> > Dale Farnsworth writes:
> >
> > > Paul, this patch is unchanged from the one I posted 10 days ago.
> > > At that time, I saw no discussion, other than Mark's ACK. I'd
> > > argue that this is a bugfix, and hope that it could go into 2.6.22.
> >
> > Um, it seems rather large, and in particular adds a fair bit of
> > completely new code. Is there a simpler way of getting to an
> > acceptable point - e.g. just not use the udbg console on these boards?
>
> Yeah, that was the first approach I took. Unfortunately, currently the
> udbg console is included unconditionally on arch/powerpc. I created the
> patch below to conditionalize the use of udbg console. I thought it a
> bit risky for 2.6.22, but I think it's the right approach long term.
>
> > If we don't have udbg support for them then the udbg console would
> > seem a bit pointless, no?
>
> There is value in that with the udbg console we do see console output
> much earlier. While there's some new code (I didn't think it was all
> that much), the impact is limited to the single platform now using the
> mv64x60 console port, the prpmc2800.
You don't select PPC_UDBG for any of the cell platforms, which AFAICT
means you'll break early debugging on those.
I think you should be able to do this in terms of
CONFIG_PPC_EARLY_DEBUG, which already exists.
cheers
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-06-08 2:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-23 22:05 [PATCH] powerpc: Add Marvell mv64x60 udbg putc/getc functions Dale Farnsworth
2007-05-23 23:27 ` Olof Johansson
2007-05-24 0:02 ` Dale Farnsworth
2007-05-24 1:53 ` Olof Johansson
2007-06-06 6:06 ` Paul Mackerras
2007-06-06 17:29 ` Dale Farnsworth
2007-06-08 2:15 ` Michael Ellerman [this message]
2007-06-08 17:20 ` Dale Farnsworth
-- strict thread matches above, loose matches on Subject: below --
2007-05-14 19:52 Dale Farnsworth
2007-05-15 18:55 ` Mark A. Greer
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=1181268915.6026.5.camel@concordia.ozlabs.ibm.com \
--to=michael@ellerman.id.au \
--cc=dale@farnsworth.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
/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).