linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: EricDuj <eric.dujardin@sagem.com>
To: linuxppc-dev@ozlabs.org
Subject: Re: [BUG][PATCH] 2.6.25-rc2 build fails on mpc52xx_psc_spi
Date: Tue, 19 Feb 2008 03:58:20 -0800 (PST)	[thread overview]
Message-ID: <15560565.post@talk.nabble.com> (raw)
In-Reply-To: <15560559.post@talk.nabble.com>


Hello again,

Here is a second patch as the link fails with the same configuration. The
error is the following:

Image Name:   Linux-2.6.25-rc2
Created:      Tue Feb 19 13:57:46 2008
Image Type:   PowerPC Linux Kernel Image (gzip compressed)
Data Size:    1662959 Bytes = 1623.98 kB = 1.59 MB
Load Address: 0x00400000
Entry Point:  0x00400550
  Building modules, stage 2.
  MODPOST 24 modules
ERROR: "mpc52xx_set_psc_clkdiv" [drivers/spi/mpc52xx_psc_spi.ko] undefined!
make[1]: *** [__modpost] Erreur 1
make: *** [modules] Erreur 2

Here is the patch:

--- arch/powerpc/platforms/52xx/mpc52xx_common.c.orig	2008-02-19
14:14:52.000000000 +0100
+++ arch/powerpc/platforms/52xx/mpc52xx_common.c	2008-02-19
14:12:56.000000000 +0100
@@ -199,6 +199,7 @@
 
 	return 0;
 }
+EXPORT_SYMBOL(mpc52xx_set_psc_clkdiv);
 
 /**
  * mpc52xx_restart: ppc_md->restart hook for mpc5200 using the watchdog
timer


Best,

Eric


EricDuj wrote:
> 
> Hi all,
> 
> I am trying to cross compile the vanilla 2.6.25-rc2 kernel with the Denx
> 4.1 toolchain (gcc-4.0.0 based).
> 
> 

-- 
View this message in context: http://www.nabble.com/-BUG--PATCH--2.6.25-rc2-build-fails-on-mpc52xx_psc_spi-tp15560559p15560565.html
Sent from the linuxppc-dev mailing list archive at Nabble.com.

  reply	other threads:[~2008-02-19 11:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-19 11:35 [BUG][PATCH] 2.6.25-rc2 build fails on mpc52xx_psc_spi EricDuj
2008-02-19 11:58 ` EricDuj [this message]
2008-02-19 15:12   ` [PATCH] fix 2.6.25-rc2 build with CONFIG_SPI_MPC52xx_PSC Grant Likely
2008-02-19 15:09 ` [PATCH] fix 2.6.25-rc2 compilation " Grant Likely

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=15560565.post@talk.nabble.com \
    --to=eric.dujardin@sagem.com \
    --cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).