public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Hartmann <jhartmann@valinux.com>
To: Charles McLachlan <cim20@mrao.cam.ac.uk>
Cc: linux-kernel@vger.kernel.org, Petr Vandrovec <VANDROVE@vc.cvut.cz>
Subject: Re: [PATCH] 2.4.0 agpgart with i815 and external card.
Date: Wed, 10 Jan 2001 12:03:10 -0700	[thread overview]
Message-ID: <3A5CB1EE.5060400@valinux.com> (raw)
In-Reply-To: <Pine.SOL.4.30.0101101704070.9183-200000@mraosd.ra.phy.cam.ac.uk>

Charles McLachlan wrote:

> My problem was that I didn't pay enough attention to the configuration
> options. I opted for *both* the 440LX/BX/GX, 815, 840, 850 support
> (CONFIG_AGP_INTEL) *and* I810/I815 (on-board) support (CONFIG_AGP_I810).
> 
> The latter was taking precedence over the former, and getting confused.
> 
> Petr Vandrovec has made the very good point that, to stop others from
> getting as confused as me, agpgart should default to generic intel if it
> can't find the onboard i815 video card.
> 
> It's a very small patch (one line really) which I present for your
> consideration.
> 
> Thanks to Alan Cox and Petr for putting me right.
> 
> Charlie - Queens' College - Cavendish Astrophysics - 07866 636318
> 
> 
> ------------------------------------------------------------------------
> 
> --- drivers/char/agp/agpgart_be_original.c	Wed Jan 10 16:59:35 2001
> +++ drivers/char/agp/agpgart_be.c	Wed Jan 10 17:00:54 2001
> @@ -2373,9 +2373,9 @@
>  			if (i810_dev == NULL) {
>  				printk(KERN_ERR PFX "agpgart: Detected an "
>  				       "Intel i815, but could not find the"
> -				       " secondary device.\n");
> -				agp_bridge.type = NOT_SUPPORTED;
> -				return -ENODEV;
> +				       " secondary device. Assuming a "
> +				       "non-integrated video card.\n");
> +				break;
>  			}
>  			printk(KERN_INFO PFX "agpgart: Detected an Intel i815 "
>  			       "Chipset.\n");
> agppatch
> 
> Content-Type:
> 
> TEXT/PLAIN
> Content-Encoding:
> 
> BASE64

This looks reasonable, and it will probably avoid alot of people from 
emailing me. ;)  It has my vote for 2.4.1.

-Jeff

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

      reply	other threads:[~2001-01-10 20:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-10 17:16 Anybody got 2.4.0 running on a 386 ? Petr Vandrovec
2001-01-10 17:13 ` [PATCH] 2.4.0 agpgart with i815 and external card Charles McLachlan
2001-01-10 19:03   ` Jeff Hartmann [this message]

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=3A5CB1EE.5060400@valinux.com \
    --to=jhartmann@valinux.com \
    --cc=VANDROVE@vc.cvut.cz \
    --cc=cim20@mrao.cam.ac.uk \
    --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