linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: Timur Tabi <timur@freescale.com>
Cc: Olof Johansson <olof@lixom.net>,
	Paul Mackerras <paulus@samba.org>,
	linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] Update udbg_progress() to display the integer
Date: Thu, 08 Feb 2007 11:31:46 +1100	[thread overview]
Message-ID: <1170894706.4656.2.camel@concordia.ozlabs.ibm.com> (raw)
In-Reply-To: <45C9FE30.8010108@freescale.com>

[-- Attachment #1: Type: text/plain, Size: 2088 bytes --]

On Wed, 2007-02-07 at 10:28 -0600, Timur Tabi wrote:
> Mike Strosaker wrote:
> 
> > The op panel on recent systems has 2 lines; the first can display 16 
> > characters, the second, 80.  The first line is usually used to display 
> > an 8 character hexadecimal progress/error message (called an SRC: System 
> > Reference Code), and the second line is used to display a location code 
> > when appropriate (e.g. when the SRC indicates a device failure).  IBM 
> > documents many of their OF and RTAS SRCs deep in the Hardware 
> > Information Center:
> 
> In that case, the big question is: does the kernel conform to this standard? 
> Looking at the current usage of ppc_md.progress(), I can't help but think that 
> it being called the same way printk() is being called, i.e. at the whim of the 
> developer who wrote the code.
> 
> So let's say that we need to keep ppc_md.progress().  I think we should have 
> some way of restricting its usage to systems where it does something different 
> than printk().  On an Freescale 83xx reference board, for example, its output 
> goes to the same place as printk(), so it doesn't serve any purpose.
> 
> Perhaps we should define ppc_md.progress() such that it never sends the output 
> to the same place as printk().  If the only output device is the serial port, 
> and printk() already outputs there, then ppc_md.progress() should do nothing. 
> This would eliminate any "accidental" use of ppc_md.progress(), when printk() is 
> the better choice.

But then you'll end up with code that does:

 printk("Setup done");
 ppc_md.progress("Setup done");

Because on systems where the output _does_ go to two places, you'll want
the messages to appear in both.

I don't see what the problem is with progress messages going to the
printk buffer?

cheers

-- 
Michael Ellerman
OzLabs, IBM Australia Development Lab

wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)

We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-02-08  0:31 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
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 [this message]
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=1170894706.4656.2.camel@concordia.ozlabs.ibm.com \
    --to=michael@ellerman.id.au \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=olof@lixom.net \
    --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).