linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: Linas Vepstas <linas@austin.ibm.com>
Cc: Olof Johansson <olof@lixom.net>,
	linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] Update udbg_progress() to display the integer
Date: Wed, 07 Feb 2007 16:26:23 -0600	[thread overview]
Message-ID: <45CA520F.1080006@freescale.com> (raw)
In-Reply-To: <20070207215957.GD5616@austin.ibm.com>

Linas Vepstas wrote:

> The HMC progress display is the "same as" the LED's 
> i.e. one line of 30 or 40 chars. Its enough to tell you 
> the kernel version you've booted, or if the machine is
> stuck in firmware. but that's about it. 

In that case, it looks like we need to keep pcc_md.progress(), but I still think 
it should be restricted to platforms where it outputs to a device other than the 
device that printk() is outputting to.

-- 
Timur Tabi
Linux Kernel Developer @ Freescale

  reply	other threads:[~2007-02-07 22:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-05 19:51 [PATCH] Update udbg_progress() to display the integer Timur Tabi
2007-02-06  1:30 ` Olof Johansson
2007-02-06 23:08   ` Timur Tabi
2007-02-06 23:11     ` Paul Mackerras
2007-02-06 23:38       ` Benjamin Herrenschmidt
2007-02-06 23:41         ` Kumar Gala
2007-02-06 23:54           ` Timur Tabi
2007-02-07  0:03             ` Olof Johansson
2007-02-07  0:04               ` Timur Tabi
2007-02-07 21:59                 ` Linas Vepstas
2007-02-07 22:26                   ` Timur Tabi [this message]
2007-02-07  0:00           ` Stephen Rothwell
2007-02-07  0:04             ` Stephen Rothwell
2007-02-06 23:42         ` Timur Tabi
2007-02-07  6:26           ` Mike Strosaker
2007-02-07 16:28             ` Timur Tabi
2007-02-08  0:31               ` Michael Ellerman
2007-02-08  2:07                 ` Timur Tabi
2007-02-07 21:03             ` Benjamin Herrenschmidt

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=45CA520F.1080006@freescale.com \
    --to=timur@freescale.com \
    --cc=linas@austin.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=olof@lixom.net \
    --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).