linux-mips
[Top] [All Lists]

Re: Is the new generic KGDB patch in upstream-akpm?

To: Daniel Laird <daniel.j.laird@nxp.com>
Subject: Re: Is the new generic KGDB patch in upstream-akpm?
From: Ralf Baechle <ralf@linux-mips.org>
Date: Tue, 29 Jul 2008 08:09:44 +0100
Cc: linux-mips@linux-mips.org
In-reply-to: <64660ef00807250921h75ec4e48v92ef964e1c1185f4@mail.gmail.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <64660ef00807250921h75ec4e48v92ef964e1c1185f4@mail.gmail.com>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.5.18 (2008-05-17)
On Fri, Jul 25, 2008 at 05:21:33PM +0100, Daniel Laird wrote:

> I am trying to respin the patch to add pnx833x support to linux 2.6.27.
> I wanted to patch against the new generic kernel KGDB patch.
> So I removed gdb-hook etc.
> 
> However when I compile I get
> arch/mips/kernel/built-in.o: In function `early_console_write':
> early_printk.c:(.init.text+0x1450): undefined reference to `prom_putchar'
> early_printk.c:(.init.text+0x1450): relocation truncated to fit:
> R_MIPS_26 against `prom_putchar'
> early_printk.c:(.init.text+0x145c): undefined reference to `prom_putchar'
> early_printk.c:(.init.text+0x145c): relocation truncated to fit:
> R_MIPS_26 against `prom_putchar'
> make[1]: *** [.tmp_vmlinux1] Error 1
> 
> These functions were defined in my gdb-hook.c.  Do I need to move
> these somewhere else now? Or just not support EARLY_PRINTK etc.

Bad choice - early printk has no relation whatsoever to GDB - though both
might end bitbanging the same serial, so early printk code should live
in a different file.

  Ralf

<Prev in Thread] Current Thread [Next in Thread>