From: Helge Deller <deller@gmx.de>
To: Kyle McMartin <kyle@mcmartin.ca>
Cc: linux-parisc@vger.kernel.org
Subject: Re: [PATCH] parisc: pass through '\t' to early (iodc) console
Date: Mon, 14 Jun 2010 22:08:44 +0200 [thread overview]
Message-ID: <4C168C4C.9080706@gmx.de> (raw)
In-Reply-To: <20100614160227.GK20317@bombadil.infradead.org>
On 06/14/2010 06:02 PM, Kyle McMartin wrote:
> The firmware handles '\t' internally, so stop trying to emulate it
> (which, incidentally, had a bug in it.)
>
> Fixes a really weird hang at bootup in rcu_bootup_announce, which,
> as far as I can tell, is the first printk in the core kernel to use
> a tab as the first character.
>
> Signed-off-by: Kyle McMartin <kyle@parisc-linux.org>
Kernel boots now nicely.
Thanks Kyle!
Tested-by: Helge Deller <deller@gmx.de>
> ---
> arch/parisc/kernel/firmware.c | 12 ++----------
> 1 files changed, 2 insertions(+), 10 deletions(-)
>
> diff --git a/arch/parisc/kernel/firmware.c b/arch/parisc/kernel/firmware.c
> index 4c247e0..df971fa 100644
> --- a/arch/parisc/kernel/firmware.c
> +++ b/arch/parisc/kernel/firmware.c
> @@ -1123,7 +1123,6 @@ static char __attribute__((aligned(64))) iodc_dbuf[4096];
> */
> int pdc_iodc_print(const unsigned char *str, unsigned count)
> {
> - static int posx; /* for simple TAB-Simulation... */
> unsigned int i;
> unsigned long flags;
>
> @@ -1133,19 +1132,12 @@ int pdc_iodc_print(const unsigned char *str, unsigned count)
> iodc_dbuf[i+0] = '\r';
> iodc_dbuf[i+1] = '\n';
> i += 2;
> - posx = 0;
> goto print;
> - case '\t':
> - while (posx & 7) {
> - iodc_dbuf[i] = ' ';
> - i++, posx++;
> - }
> - break;
> case '\b': /* BS */
> - posx -= 2;
> + i--; /* overwrite last */
> default:
> iodc_dbuf[i] = str[i];
> - i++, posx++;
> + i++;
> break;
> }
> }
next prev parent reply other threads:[~2010-06-14 20:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-14 16:02 [PATCH] parisc: pass through '\t' to early (iodc) console Kyle McMartin
2010-06-14 20:08 ` Helge Deller [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-08-04 0:38 Kyle McMartin
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=4C168C4C.9080706@gmx.de \
--to=deller@gmx.de \
--cc=kyle@mcmartin.ca \
--cc=linux-parisc@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 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.