From: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
To: Peter Chubb <peterc@gelato.unsw.edu.au>
Cc: akpm@osdl.org, linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Can't disable IDE DMA on 2.6.0-test9 (patch)
Date: Mon, 8 Dec 2003 02:39:58 +0100 [thread overview]
Message-ID: <200312080239.58602.bzolnier@elka.pw.edu.pl> (raw)
In-Reply-To: <16317.18623.912339.111750@wombat.disy.cse.unsw.edu.au>
On Friday 21 of November 2003 00:05, Peter Chubb wrote:
> Hi Folks,
Hi,
> If you try to disable IDE DMA from Kconfig, you'll end up with an
> undefined symbol, ide_hwif_setup_dma().
>
> The attached rather ugly patch fixes the problem by defining a dummy
> function.
Not exactly. Disable IDE DMA and enable support for every PCI chipset.
Now try to compile... welcome to compile time hell :-).
To do this properly you have to fix almost every PCI chipset driver
(by adding many CONFIG_BLK_DEV_IDEDMA_PCI #ifdefs).
--bart
> ===== setup-pci.c 1.19 vs edited =====
> --- 1.19/drivers/ide/setup-pci.c Sat Oct 18 01:22:22 2003
> +++ edited/setup-pci.c Wed Nov 19 13:52:25 2003
> @@ -474,6 +474,11 @@
> * state
> */
>
> +#ifndef CONFIG_BLK_DEV_IDEDMA_PCI
> +static void ide_hwif_setup_dma(struct pci_dev *dev, ide_pci_device_t *d,
> ide_hwif_t *hwif) +{
> +}
> +#else
> static void ide_hwif_setup_dma(struct pci_dev *dev, ide_pci_device_t *d,
> ide_hwif_t *hwif) {
> u16 pcicmd;
> @@ -516,6 +521,7 @@
> }
> }
> }
> +#endif /* CONFIG_BLK_DEV_IDEDMA_PCI*/
>
> /**
> * ide_setup_pci_controller - set up IDE PCI
next prev parent reply other threads:[~2003-12-08 1:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-20 23:05 Can't disable IDE DMA on 2.6.0-test9 (patch) Peter Chubb
2003-12-08 1:39 ` Bartlomiej Zolnierkiewicz [this message]
2003-12-08 2:34 ` Peter Chubb
2003-12-08 3:00 ` Bartlomiej Zolnierkiewicz
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=200312080239.58602.bzolnier@elka.pw.edu.pl \
--to=b.zolnierkiewicz@elka.pw.edu.pl \
--cc=akpm@osdl.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterc@gelato.unsw.edu.au \
/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