linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mundt <paul.mundt@renesas.com>
To: linux-sh@vger.kernel.org
Subject: Re: Missing of "Uncompressing Linux... " message at boot sequence
Date: Thu, 06 May 2010 05:05:26 +0000	[thread overview]
Message-ID: <20100506050526.GC31681@renesas.com> (raw)
In-Reply-To: <4BDFCEF4.8010607@dcl.info.waseda.ac.jp>

On Wed, May 05, 2010 at 09:49:57PM -0700, Paul Mundt wrote:
> On Tue, May 04, 2010 at 04:38:28PM +0900, Hitoshi Mitake wrote:
> > If you have a plan to revive the message, I'd like to co-operate.
> > Because I'm working on new board support, serial output is a big problem 
> > for me.
> > 
> I'll have a look at restoring it, but be forewarned that there will
> likely be outstanding sh-bios issues. If you're able to assist with
> debugging this then of course I have no problem with reinstanting this
> sort of support.

Also note that the earlyprintk stuff should largely make this irrelevant
for most people. The cases where the earlyprintk code ends up being
useless is primarily with memory initialization or getting the serial
port up on a new CPU (although the latter case is not so exceptional
anymore), so it's quite possible that simply turning off the sh-bios
stuff and using the earlyprintk code as-is will be sufficient for you to
get early messages.

  parent reply	other threads:[~2010-05-06  5:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-04  7:38 Missing of "Uncompressing Linux... " message at boot sequence Hitoshi Mitake
2010-05-06  4:49 ` Paul Mundt
2010-05-06  5:05 ` Paul Mundt [this message]
2010-05-09 14:37 ` Hitoshi Mitake

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=20100506050526.GC31681@renesas.com \
    --to=paul.mundt@renesas.com \
    --cc=linux-sh@vger.kernel.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).