From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Li Yang-r58472 <LeoLi@freescale.com>
Cc: Phillips Kim-R1AAHA <Kim.Phillips@freescale.com>,
Yin Olivia-r63875 <Hong-Hua.Yin@freescale.com>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
linuxppc-dev@ozlabs.org, 'Paul Mackerras' <paulus@samba.org>,
Chu hanjin-r52514 <Hanjin.Chu@freescale.com>
Subject: RE: [PATCH 1/7] powerpc: Add mpc8360epb platform support
Date: Wed, 05 Jul 2006 08:39:40 +1000 [thread overview]
Message-ID: <1152052780.13828.101.camel@localhost.localdomain> (raw)
In-Reply-To: <9FCDBA58F226D911B202000BDBAD467306E05003@zch01exm40.ap.freescale.net>
> The problem is that we don't have this PPC_UBDG_16550 option configurable now,
> and it is only made by default for several boards including pseries, chrp, prep, cell,
> and all 83xx and 85xx platforms. If we need to change the whole thing, how should we do it?
It's up to your platformn code to enable it though. udbg will only kick
in from the legacy serial console code if your firmware indicates that
stdout is on a serial port. If the firmware doesn't, udbg won't kick in.
But yeah, build it in by default if you want then.
Ben.
next prev parent reply other threads:[~2006-07-04 22:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-04 7:00 [PATCH 1/7] powerpc: Add mpc8360epb platform support Li Yang-r58472
2006-07-04 22:39 ` Benjamin Herrenschmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-30 10:27 Li Yang-r58472
2006-07-01 9:00 ` Benjamin Herrenschmidt
2006-06-30 7:58 Li Yang-r58472
2006-06-29 9:28 Li Yang-r58472
2006-06-29 18:03 ` Andy Fleming
2006-06-29 18:51 ` Vitaly Bordug
2006-06-29 19:18 ` Andy Fleming
2006-06-29 19:56 ` Vitaly Bordug
2006-06-29 21:04 ` Andy Fleming
2006-06-29 22:10 ` Vitaly Bordug
2006-06-28 14:23 Li Yang-r58472
2006-06-28 16:58 ` Vitaly Bordug
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=1152052780.13828.101.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=Hanjin.Chu@freescale.com \
--cc=Hong-Hua.Yin@freescale.com \
--cc=Kim.Phillips@freescale.com \
--cc=LeoLi@freescale.com \
--cc=linux-kernel@vger.kernel.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).