public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Christoph Hellwig <hch@lst.de>
Cc: davej@codemonkey.org.uk, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix CONFIG_AGP depencies
Date: Sun, 16 Jan 2005 13:05:50 +0100	[thread overview]
Message-ID: <20050116120550.GQ4274@stusta.de> (raw)
In-Reply-To: <20050116114457.GA13506@lst.de>

On Sun, Jan 16, 2005 at 12:44:57PM +0100, Christoph Hellwig wrote:

> When I did an allmodconfig on ppc64 it selected agp although ppc64
> doesn't support agp and has not agp.h so the build failed.
> 
> This patch makes CONFIG_AGP depend on the architectures that actually
> support agp.
> 
> 
> --- 1.39/drivers/char/agp/Kconfig	2005-01-08 01:15:52 +01:00
> +++ edited/drivers/char/agp/Kconfig	2005-01-16 11:39:56 +01:00
> @@ -1,5 +1,6 @@
>  config AGP
> -	tristate "/dev/agpgart (AGP Support)" if !GART_IOMMU && !M68K && !ARM
> +	tristate "/dev/agpgart (AGP Support)" if !GART_IOMMU
> +	depends on ALPHA || IA64 || PPC || X86
>  	default y if GART_IOMMU
>  	---help---
>  	  AGP (Accelerated Graphics Port) is a bus system mainly used to

This doesn't seem to achieve what you want:
PPC is defined on ppc64...

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2005-01-16 12:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-16 11:44 [PATCH] fix CONFIG_AGP depencies Christoph Hellwig
2005-01-16 12:05 ` Adrian Bunk [this message]
2005-01-16 12:09   ` Christoph Hellwig
  -- strict thread matches above, loose matches on Subject: below --
2005-01-16 15:37 Mikael Pettersson
2005-01-16 15:47 ` Christoph Hellwig
2005-01-16 16:59 Mikael Pettersson

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=20050116120550.GQ4274@stusta.de \
    --to=bunk@stusta.de \
    --cc=davej@codemonkey.org.uk \
    --cc=hch@lst.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