[PATCH] x86/boot: Add ability to call printf in video modes initialization

[Alexander Kuleshov]

Added ability to call printf in video-mode.c, video-bios.c, video-vesa.c and
video-vga.c for debugging purposes.

Signed-off-by: Alexander Kuleshov <kuleshovmail@xxxxxxxxx>
---
 arch/x86/realmode/rm/Makefile | 4 ++--
 arch/x86/realmode/rm/printf.c | 1 +
 arch/x86/realmode/rm/string.c | 1 +
 arch/x86/realmode/rm/tty.c    | 1 +
 4 files changed, 5 insertions(+), 2 deletions(-)
 create mode 100644 arch/x86/realmode/rm/printf.c
 create mode 100644 arch/x86/realmode/rm/string.c
 create mode 100644 arch/x86/realmode/rm/tty.c

diff --git a/arch/x86/realmode/rm/Makefile b/arch/x86/realmode/rm/Makefile
index 7c0d7be..e0f78f5 100644
--- a/arch/x86/realmode/rm/Makefile
+++ b/arch/x86/realmode/rm/Makefile
@@ -9,8 +9,8 @@
 
 always := realmode.bin realmode.relocs
 
-wakeup-objs	:= wakeup_asm.o wakemain.o video-mode.o
-wakeup-objs	+= copy.o bioscall.o regs.o
+wakeup-objs	:= wakeup_asm.o wakemain.o string.o tty.o printf.o
+wakeup-objs	+= video-mode.o copy.o bioscall.o regs.o
 # The link order of the video-*.o modules can matter.  In particular,
 # video-vga.o *must* be listed first, followed by video-vesa.o.
 # Hardware-specific drivers should follow in the order they should be
diff --git a/arch/x86/realmode/rm/printf.c b/arch/x86/realmode/rm/printf.c
new file mode 100644
index 0000000..bae7729
--- /dev/null
+++ b/arch/x86/realmode/rm/printf.c
@@ -0,0 +1 @@
+#include "../../boot/printf.c"
diff --git a/arch/x86/realmode/rm/string.c b/arch/x86/realmode/rm/string.c
new file mode 100644
index 0000000..cbd5413
--- /dev/null
+++ b/arch/x86/realmode/rm/string.c
@@ -0,0 +1 @@
+#include "../../boot/string.c"
diff --git a/arch/x86/realmode/rm/tty.c b/arch/x86/realmode/rm/tty.c
new file mode 100644
index 0000000..d915398
--- /dev/null
+++ b/arch/x86/realmode/rm/tty.c
@@ -0,0 +1 @@
+#include "../../boot/tty.c"
-- 
2.2.1.212.gc5b9256

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/