From: Dave Jones <davej@redhat.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] AGP_AMD64 must depend on PCI
Date: Wed, 28 Jun 2006 13:02:22 -0400 [thread overview]
Message-ID: <20060628170222.GA23396@redhat.com> (raw)
In-Reply-To: <20060628165529.GI13915@stusta.de>
On Wed, Jun 28, 2006 at 06:55:30PM +0200, Adrian Bunk wrote:
> This patch fixes the following compile error:
>
> <-- snip -->
>
> ...
> CC arch/i386/kernel/../../x86_64/kernel/k8.o
> arch/i386/kernel/../../x86_64/kernel/k8.c: In function ‘next_k8_northbridge’:
> arch/i386/kernel/../../x86_64/kernel/k8.c:34: error: implicit declaration of function ‘pci_match_id’
>
> <-- snip -->
>
> Signed-off-by: Adrian Bunk <bunk@stusta.de>
>
> --- linux-2.6.17-mm3-full/drivers/char/agp/Kconfig.old 2006-06-28 12:56:20.000000000 +0200
> +++ linux-2.6.17-mm3-full/drivers/char/agp/Kconfig 2006-06-28 12:56:55.000000000 +0200
> @@ -56,7 +56,7 @@
>
> config AGP_AMD64
> tristate "AMD Opteron/Athlon64 on-CPU GART support" if !IOMMU
> - depends on AGP && X86
> + depends on AGP && PCI && X86
> default y if IOMMU
> help
> This option gives you AGP support for the GLX component of
What makes this driver special ? The other AGP drivers also use
various PCI functions, and don't have a similar dependancy.
Adding depends on PCI to 'AGP' may make more sense than adding
it to the individual drivers, especially as the core AGP code also
uses the pci layer. As AGP is just a bastardised variant of PCI
anyway, adding an explicit dependancy should be sane on all archs,
even alpha with its wierdo 'faked pci bridge'.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-06-28 17:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-28 16:55 [2.6 patch] AGP_AMD64 must depend on PCI Adrian Bunk
2006-06-28 17:02 ` Dave Jones [this message]
2006-06-28 17:20 ` Adrian Bunk
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=20060628170222.GA23396@redhat.com \
--to=davej@redhat.com \
--cc=bunk@stusta.de \
--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