From: Timur Tabi <timur@freescale.com>
To: Olof Johansson <olof@lixom.net>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] Update udbg_progress() to display the integer
Date: Tue, 06 Feb 2007 17:08:30 -0600 [thread overview]
Message-ID: <45C90A6E.3040302@freescale.com> (raw)
In-Reply-To: <20070206013051.GA15525@lixom.net>
Olof Johansson wrote:
> On Mon, Feb 05, 2007 at 01:51:55PM -0600, Timur Tabi wrote:
>> Although udbg_progress() takes a string and a short as parameters, only
>> the string is displayed. This patch also displays the integer, if it's not
>> equal to 0xFFFF. This gives callers the option to display only the string.
>
> Some platforms do this already, but they output the numbers first. It's
> a good idea to stay consistent with that.
>
> See maple_progress, ps3_progress and friends for templates. They're
> quite verbose though.
Actually, they're just one line each:
static void __init maple_progress(char *s, unsigned short hex)
{
printk("*** %04x : %s\n", hex, s ? s : "");
}
static void __init ps3_progress(char *s, unsigned short hex)
{
printk("*** %04x : %s\n", hex, s ? s : "");
}
The reason I can't use the same exact printk() is because of this code in
function ppc_init():
/* clear the progress line */
if ( ppc_md.progress ) ppc_md.progress(" ", 0xffff);
If I could get rid of this line, then I wouldn't need to check for "hex ==
0xFFFF", but I don't know why ppc_init() thinks it needs to "clear the progress
line". Maybe this is for some kind of LED display.
I'll submit a new patch in a minute.
--
Timur Tabi
Linux Kernel Developer @ Freescale
next prev parent reply other threads:[~2007-02-06 23:08 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 [this message]
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
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=45C90A6E.3040302@freescale.com \
--to=timur@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=olof@lixom.net \
/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.