public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "Luck, Tony" <tony.luck@intel.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] PATCH: fix CONFIG_IA64_EARLY_PRINTK
Date: Fri, 09 Nov 2001 00:54:26 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590698805458@msgid-missing> (raw)

This was broken in 2.4.10 when "early_printk()" was given
an extra argument to specify the length of the string to
print, but head.S wasn't updated to pass such an argument.
(Oddly enough the "alloc" call in head.S sets up two 'out'
registers already).

Here is the patch:

diff -ru ../../REF/2.4.14-ia64-011105/arch/ia64/config.in
linux/arch/ia64/config.in
--- ../../REF/2.4.14-ia64-011105/arch/ia64/config.in	Tue Nov  6 11:34:13
2001
+++ linux/arch/ia64/config.in	Thu Nov  8 16:41:15 2001
@@ -266,8 +266,7 @@
    bool '  Disable VHPT' CONFIG_DISABLE_VHPT
    bool '  Magic SysRq key' CONFIG_MAGIC_SYSRQ
 
-# early printk is currently broken for SMP: the secondary processors get
stuck...
-#   bool '  Early printk support (requires VGA!)' CONFIG_IA64_EARLY_PRINTK
+   bool '  Early printk support (requires VGA!)' CONFIG_IA64_EARLY_PRINTK
 
    bool '  Debug memory allocations' CONFIG_DEBUG_SLAB
    bool '  Spinlock debugging' CONFIG_DEBUG_SPINLOCK
diff -ru ../../REF/2.4.14-ia64-011105/arch/ia64/kernel/head.S
linux/arch/ia64/kernel/head.S
--- ../../REF/2.4.14-ia64-011105/arch/ia64/kernel/head.S	Tue Nov  6
11:34:13 2001
+++ linux/arch/ia64/kernel/head.S	Thu Nov  8 16:29:34 2001
@@ -180,10 +180,12 @@
 	.rodata
 alive_msg:
 	stringz "I'm alive and well\n"
+alive_msg_end:
 	.previous
 
 	alloc r2=ar.pfs,0,0,2,0
 	movl out0=alive_msg
+	movl out1=alive_msg_end-alive_msg-1
 	;;
 	br.call.sptk.many rpêrly_printk
 1:	// force new bundle


                 reply	other threads:[~2001-11-09  0:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=marc-linux-ia64-105590698805458@msgid-missing \
    --to=tony.luck@intel.com \
    --cc=linux-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox