From: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
To: Dale Amon <amon@vnl.com>
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: CMD640 problem in 2.6.0-test8
Date: Mon, 20 Oct 2003 20:56:42 +0200 [thread overview]
Message-ID: <200310202056.42759.bzolnier@elka.pw.edu.pl> (raw)
In-Reply-To: <20031020172733.GA17379@vnl.com>
On Monday 20 of October 2003 19:27, Dale Amon wrote:
> I'm seeing these compile errors:
>
> LD .tmp_vmlinux1
>
> drivers/built-in.o(.init.text+0x4e6b): In function `ide_setup':
> : undefined reference to `cmd640_vlb'
>
> drivers/built-in.o(.init.text+0x5361): In function `probe_for_hwifs':
> : undefined reference to `ide_probe_for_cmd640x'
>
> make: *** [.tmp_vmlinux1] Error 1
>
> The .config contains:
>
> CONFIG_BLK_DEV_CMD640=y
>
> but ide/pci/cmd640.c doesn't seem to get compiled. I tried doing it
> manually and got a screen full of errors.
this patch should fix it,
--bartlomiej
[IDE] fix drivers/ide/pci/cmd640.c for CONFIG_PCI=n
CMD640 driver also supports VLB version of the chipset, therefore fix
drivers/ide/Makefile to include pci/ subdir even if CONFIG_BLK_DEV_IDEPCI=n.
drivers/ide/Makefile | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
diff -puN drivers/ide/Makefile~ide-cmd640-no_pci-fix drivers/ide/Makefile
--- linux-2.6.0-test8/drivers/ide/Makefile~ide-cmd640-no_pci-fix 2003-10-20 20:47:03.701132024 +0200
+++ linux-2.6.0-test8-root/drivers/ide/Makefile 2003-10-20 20:47:17.280067712 +0200
@@ -8,7 +8,7 @@
# In the future, some of these should be built conditionally.
#
# First come modules that register themselves with the core
-obj-$(CONFIG_BLK_DEV_IDEPCI) += pci/
+obj-$(CONFIG_BLK_DEV_IDE) += pci/
# Core IDE code - must come before legacy
_
next prev parent reply other threads:[~2003-10-20 21:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-20 17:27 Dale Amon
2003-10-20 18:56 ` Bartlomiej Zolnierkiewicz [this message]
2003-10-20 22:47 ` Dale Amon
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=200310202056.42759.bzolnier@elka.pw.edu.pl \
--to=b.zolnierkiewicz@elka.pw.edu.pl \
--cc=amon@vnl.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®