All of lore.kernel.org
 help / color / mirror / Atom feed
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 14:29:05 +0200	[thread overview]
Message-ID: <3F65B091.1020802@imc-berlin.de> (raw)
In-Reply-To: <1063627208.14615.21.camel@trantor.staff.proxad.net>


Hubert Figuiere wrote:
> On Mon, 2003-09-15 at 13:31, Steven Scholz wrote:
>
>
>>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...
>
>
> Change 'wait_hwif_ready' by 'ide_wait_hwif_ready' in both ide-probe.c
> and ide.c
Ok. This obviously fixes it.
I just noticed that I might have used the wrong source tree.

So which is the BK tree to use:

linuxppc_2_4_devel or linuxppc-2.4 ???

Thanks,

Steven


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-09-15 12:29 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
2003-09-15 12:00   ` Hubert Figuiere
2003-09-15 12:29     ` Steven Scholz [this message]
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=3F65B091.1020802@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 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.