From: David Miller <davem@davemloft.net>
To: mroos@linux.ee
Cc: linux-kernel@vger.kernel.org
Subject: Re: libata & no PCI: dma_[un]map_single undefined
Date: Sun, 03 Jun 2007 17:40:10 -0700 (PDT) [thread overview]
Message-ID: <20070603.174010.41894721.davem@davemloft.net> (raw)
In-Reply-To: <Pine.SOC.4.64.0706032314590.20033@math>
From: Meelis Roos <mroos@linux.ee>
Date: Sun, 3 Jun 2007 23:23:33 +0300 (EEST)
> I accidentally enabled libata config options on my Sun Ultra 1 (sparc64,
> UP, no PCI, only SBUS):
>
> MODPOST 440 modules
> ERROR: "dma_unmap_sg" [drivers/ata/libata.ko] undefined!
> ERROR: "dma_map_sg" [drivers/ata/libata.ko] undefined!
> ERROR: "dma_unmap_single" [drivers/ata/libata.ko] undefined!
> ERROR: "dma_mapping_error" [drivers/ata/libata.ko] undefined!
> ERROR: "dma_map_single" [drivers/ata/libata.ko] undefined!
>
> CONFIG_PCI=n
> CONFIG_ATA=m
>
> This seems to be a valid configuration since libata can drive non-PCI
> devices too?
It really makes no sense to allow this on Sparc, there are no
non-PCI Sparc ATA controllers.
Therefore I'll fix it like this:
commit 6274b5c63131c3110405db5d19e71af26cbbd375
Author: David S. Miller <davem@sunset.davemloft.net>
Date: Sun Jun 3 17:39:56 2007 -0700
[ATA]: Don't allow to enable this for SPARC64 without PCI.
Based upon a report from Meelis Roos.
Signed-off-by: David S. Miller <davem@davemloft.net>
diff --git a/drivers/ata/Kconfig b/drivers/ata/Kconfig
index b4a8d60..7d893a6 100644
--- a/drivers/ata/Kconfig
+++ b/drivers/ata/Kconfig
@@ -8,6 +8,7 @@ menuconfig ATA
depends on BLOCK
depends on !(M32R || M68K) || BROKEN
depends on !SUN4 || BROKEN
+ depends on !(SPARC64 && !PCI)
select SCSI
---help---
If you want to use a ATA hard disk, ATA tape drive, ATA CD-ROM or
next prev parent reply other threads:[~2007-06-04 0:40 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-03 20:23 libata & no PCI: dma_[un]map_single undefined Meelis Roos
2007-06-04 0:40 ` David Miller [this message]
2007-06-04 7:47 ` Christoph Hellwig
2007-06-04 17:19 ` Jeff Garzik
2007-06-05 11:22 ` Alan Cox
2007-06-05 13:56 ` Jeff Garzik
2007-06-05 14:17 ` Russell King
2007-06-05 14:25 ` Jeff Garzik
2007-06-05 14:35 ` Jeff Garzik
2007-06-05 14:51 ` Russell King
2007-06-05 14:56 ` Jeff Garzik
2007-06-05 14:59 ` Russell King
2007-06-05 15:11 ` Jeff Garzik
2007-06-05 15:18 ` Russell King
2007-06-05 15:21 ` Russell King
2007-06-05 19:27 ` David Miller
2007-06-05 21:25 ` Russell King
2007-06-05 21:38 ` Russell King
2007-06-05 21:48 ` Jeff Garzik
2007-06-05 22:03 ` Russell King
2007-06-05 22:16 ` Jeff Garzik
2007-06-06 0:25 ` Valdis.Kletnieks
2007-06-05 15:41 ` Jeff Garzik
2007-06-05 15:45 ` Russell King
2007-06-05 19:27 ` David Miller
2007-06-05 19:24 ` David Miller
2007-06-05 21:10 ` Chuck Ebbert
2007-06-05 19:23 ` David Miller
2007-06-05 21:20 ` Russell King
2007-06-05 15:50 ` Alan Cox
2007-06-05 15:52 ` Russell King
2007-06-04 7:54 ` Geert Uytterhoeven
2007-06-04 13:30 ` Alan Cox
2007-06-04 21:22 ` David Miller
2007-06-05 0:56 ` William Lee Irwin III
2007-06-05 11:12 ` Alan Cox
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=20070603.174010.41894721.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mroos@linux.ee \
/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