From: Steven Scholz <steven.scholz@imc-berlin.de>
To: Linuxppc-Embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Problems w/ CONFIG_BLK_DEV_MPC8xx_IDE
Date: Mon, 15 Sep 2003 13:31:09 +0200 [thread overview]
Message-ID: <3F65A2FD.3010904@imc-berlin.de> (raw)
In-Reply-To: <3F656CFC.1050706@imc-berlin.de>
Steven Scholz wrote:
> I just noticed that the vanilla 2.4.22 does not compile with
> CONFIG_BLK_DEV_MPC8xx_IDE:
>
> drivers/ide/idedriver.o: In function `ide_timer_expiry':
> drivers/ide/idedriver.o(.text+0xaa30): undefined reference to
> `ide_ack_intr'
> drivers/ide/idedriver.o(.text+0xaa30): relocation truncated to fit:
> R_PPC_REL24
>
> It's the same for the BK trees.
The BK linuxppc_2_4_devel tree has another problem as well:
drivers/ide/idedriver.o: In function `probe_hwif':
drivers/ide/idedriver.o(.text+0x11a30): undefined reference to `wait_hwif_ready'
drivers/ide/idedriver.o(.text+0x11a30): relocation truncated to fit: R_PPC_REL24
wait_hwif_ready
ide-probe.c contains a call for wait_hwif_ready(), which is not defined.
This function exisists in the vanilla source though!
I supposed something went wrong while merging/syncing the IDE changes from the
official tree...
Steven
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-09-15 11:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-15 7:40 Problems w/ CONFIG_BLK_DEV_MPC8xx_IDE Steven Scholz
2003-09-15 11:31 ` Steven Scholz [this message]
2003-09-15 12:00 ` Hubert Figuiere
2003-09-15 12:29 ` Steven Scholz
2003-09-15 15:16 ` Tom Rini
2003-09-16 8:42 ` Steven Scholz
2003-09-17 15:08 ` Tom Rini
2003-09-18 9:25 ` Steven Scholz
2003-09-18 18:05 ` Tom Rini
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=3F65A2FD.3010904@imc-berlin.de \
--to=steven.scholz@imc-berlin.de \
--cc=linuxppc-embedded@lists.linuxppc.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).