From: "Mark A. Greer" <mgreer@mvista.com>
To: Dan Malek <dan@embeddededge.com>
Cc: linuxppc-dev <Linuxppc-dev@ozlabs.org>
Subject: Re: Remove progress msgs from MMU_init()
Date: Tue, 30 Aug 2005 18:29:40 -0700 [thread overview]
Message-ID: <20050831012940.GA3276@mag.az.mvista.com> (raw)
In-Reply-To: <d561d896950ba7adde6b93c1a2bba272@embeddededge.com>
On Tue, Aug 30, 2005 at 09:09:55PM -0400, Dan Malek wrote:
>
> On Aug 30, 2005, at 7:38 PM, Mark A. Greer wrote:
>
> >Does anyone object to this patch?
>
> Don't you still need this to run stuff like xmon and kgdb?
Those should work with just an io_block_mapping() which will be active
before setup_arch() calls xmon() and breakpoint().
The problem with progress msgs in MMU_init() is that they try to bang on
the uart before ioremaps/io_block_mappings are active. That's why I (and
others) had the xxx_set_bat() hack.
Mark
next prev parent reply other threads:[~2005-08-31 1:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-30 23:38 Remove progress msgs from MMU_init() Mark A. Greer
2005-08-31 1:09 ` Dan Malek
2005-08-31 1:29 ` Mark A. Greer [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-31 1:39 Mark A. Greer
2005-08-31 3:41 ` Paul Mackerras
2005-08-31 16:05 ` 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=20050831012940.GA3276@mag.az.mvista.com \
--to=mgreer@mvista.com \
--cc=Linuxppc-dev@ozlabs.org \
--cc=dan@embeddededge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.