From: Andrey Panin <pazke@orbita1.ru>
To: linux-kernel@vger.kernel.org
Cc: Linus Torvalds <torvalds@transmeta.com>
Subject: [PATCH] visws: make startup_32 kernel entry point (3/13)
Date: Fri, 14 Feb 2003 15:58:00 +0300 [thread overview]
Message-ID: <20030214125800.GC8230@pazke> (raw)
[-- Attachment #1: Type: text/plain, Size: 315 bytes --]
Hi.
This patch marks startup_32 (in head.S) as kernel entry point,
visws kernel loader uses raw elf kernel images and entry point
at stext causes jump to wrong address.
Please consider applying.
Best regards.
--
Andrey Panin | Embedded systems software developer
pazke@orbita1.ru | PGP key: wwwkeys.pgp.net
[-- Attachment #2: patch-stext --]
[-- Type: text/plain, Size: 1298 bytes --]
diff -urN -X /usr/share/dontdiff linux-2.5.60.vanilla/arch/i386/Makefile linux-2.5.60/arch/i386/Makefile
--- linux-2.5.60.vanilla/arch/i386/Makefile Thu Feb 13 20:29:07 2003
+++ linux-2.5.60/arch/i386/Makefile Thu Feb 13 20:42:02 2003
@@ -17,7 +17,7 @@
LDFLAGS := -m elf_i386
OBJCOPYFLAGS := -O binary -R .note -R .comment -S
-LDFLAGS_vmlinux := -e stext
+LDFLAGS_vmlinux :=
LDFLAGS_BLOB := --format binary --oformat elf32-i386
CFLAGS += -pipe
diff -urN -X /usr/share/dontdiff linux-2.5.60.vanilla/arch/i386/kernel/head.S linux-2.5.60/arch/i386/kernel/head.S
--- linux-2.5.60.vanilla/arch/i386/kernel/head.S Tue Jan 14 12:32:27 2003
+++ linux-2.5.60/arch/i386/kernel/head.S Fri Feb 14 15:02:32 2003
@@ -42,7 +42,7 @@
*
* On entry, %esi points to the real-mode code as a 32-bit pointer.
*/
-startup_32:
+ENTRY(startup_32)
/*
* Set segments to known values
*/
diff -urN -X /usr/share/dontdiff linux-2.5.60.vanilla/arch/i386/vmlinux.lds.S linux-2.5.60/arch/i386/vmlinux.lds.S
--- linux-2.5.60.vanilla/arch/i386/vmlinux.lds.S Thu Feb 13 20:29:07 2003
+++ linux-2.5.60/arch/i386/vmlinux.lds.S Thu Feb 13 20:42:02 2003
@@ -6,7 +6,7 @@
OUTPUT_FORMAT("elf32-i386", "elf32-i386", "elf32-i386")
OUTPUT_ARCH(i386)
-ENTRY(_start)
+ENTRY(startup_32)
jiffies = jiffies_64;
SECTIONS
{
reply other threads:[~2003-02-14 13:02 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=20030214125800.GC8230@pazke \
--to=pazke@orbita1.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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