All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Daniel Laird <daniel.j.laird@nxp.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Is the new generic KGDB patch in upstream-akpm?
Date: Tue, 29 Jul 2008 08:09:44 +0100	[thread overview]
Message-ID: <20080729070944.GC1876@linux-mips.org> (raw)
In-Reply-To: <64660ef00807250921h75ec4e48v92ef964e1c1185f4@mail.gmail.com>

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

      parent reply	other threads:[~2008-07-29  7:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-25 16:21 Is the new generic KGDB patch in upstream-akpm? Daniel Laird
2008-07-25 17:42 ` danieljlaird
2008-07-25 17:42   ` danieljlaird
2008-07-29  7:09 ` Ralf Baechle [this message]

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=20080729070944.GC1876@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=daniel.j.laird@nxp.com \
    --cc=linux-mips@linux-mips.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.