From: olof@lixom.net (Olof Johansson)
To: Timur Tabi <timur@freescale.com>
Cc: Paul Mackerras <paulus@samba.org>, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] Update udbg_progress() to display the integer
Date: Tue, 6 Feb 2007 18:03:26 -0600 [thread overview]
Message-ID: <20070207000326.GA26024@lixom.net> (raw)
In-Reply-To: <45C9151E.70201@freescale.com>
On Tue, Feb 06, 2007 at 05:54:06PM -0600, Timur Tabi wrote:
> Kumar Gala wrote:
>
> >I'm with Ben on this. I'm not aware of any in tree user that just
> >doesn't print this stuff out to a console port. The concept is nice,
> >but does anyone really use it?
>
> I just ran a quick test on an 8349 board, and it appears that everywhere
> ppc_md.progress() is called, printk() works, too.
>
> Is there any platform where ppc_md.progress() does something different than
> printk()? Is there any point in the boot process where ppc_md.progress()
> works but printk() doesn't?
On some IBM machines the progress will also print the status on the hardware
maintenance console's status line for the partition/machine in question.
-Olof
next prev parent reply other threads:[~2007-02-06 23:55 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 [this message]
2007-02-07 0:04 ` Timur Tabi
2007-02-07 21:59 ` Linas Vepstas
2007-02-07 22:26 ` Timur Tabi
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=20070207000326.GA26024@lixom.net \
--to=olof@lixom.net \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=timur@freescale.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 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).