public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@suse.de>
To: Nicolas ASPERT <Nicolas.Aspert@epfl.ch>
Cc: Margit Schubert-While <margitsw@t-online.de>,
	linux-kernel@vger.kernel.org, faith@redhat.com,
	dri-devel@lists.sourceforge.net
Subject: Re: 2.4.20 AGP for I845 wrong ?
Date: Wed, 11 Dec 2002 13:20:59 +0100	[thread overview]
Message-ID: <20021211132059.C11689@suse.de> (raw)
In-Reply-To: <3DF72A91.5080804@epfl.ch>; from Nicolas.Aspert@epfl.ch on Wed, Dec 11, 2002 at 01:07:45PM +0100

On Wed, Dec 11, 2002 at 01:07:45PM +0100, Nicolas ASPERT wrote:
 > IIRC, the 845G is a "new" version of the 830MP chipset (it had been
 > added by Abraham vd Merwe & Graeme Fisher some months ago), but acts
 > basically just as the 830MP. Therefore the entry is correct.... Or maybe
 > if it gets confusing adding a comment would not hurt...

I'll check the chipset docs when I get time, and add a comment if
necessary. No-one seems to be complaining that it isn't working,
so I'm inclined to believe your diagnosis is correct.

 > > Also in drivers/char/drm/drm_agpsupport.h, the switch statement at 262 
 > > is missing the
 > > cases for INTEL_I830_M, INTEL_I845_G.
 > That's true. It is also missing in 2.5.51.
 > I attach two patches, one for 2.4.21-pre1 and one for 2.5.51 that should 
 > fix this.
 > diff -ru linux-2.5.51.clean/drivers/char/drm/drm_agpsupport.h linux-2.5.51/drivers/char/drm/drm_agpsupport.h
 > --- linux-2.5.51.clean/drivers/char/drm/drm_agpsupport.h	Tue Dec 10 03:45:39 2002
 > +++ linux-2.5.51/drivers/char/drm/drm_agpsupport.h	Wed Dec 11 12:55:08 2002
 > @@ -271,10 +271,12 @@
 >  #if LINUX_VERSION_CODE >= 0x02040f /* KERNEL_VERSION(2,4,15) */
 >  	 	case INTEL_I820:	head->chipset = "Intel i820";	 break;
 >  #endif
 > +		case INTEL_I830_M:	head->chipset = "Intel i830M";	 break;
 >  		case INTEL_I840:	head->chipset = "Intel i840";    break;
 >  #if LINUX_VERSION_CODE >= 0x02040f /* KERNEL_VERSION(2,4,15) */
 >  		case INTEL_I845:	head->chipset = "Intel i845";    break;
 >  #endif
 > +		case INTEL_I845:	head->chipset = "Intel i845G";	 break;
 >  		case INTEL_I850:	head->chipset = "Intel i850";	 break;
 >  		case INTEL_460GX:	head->chipset = "Intel 460GX";	 break;

DRI folks, this seems like duplication given that this data is available
in agpgart. How about changing this to read whatever agpgart has set in
.chipset_name ?

Keeping these two lists in sync seems somewhat pointless.

        Dave

-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs

  reply	other threads:[~2002-12-11 12:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.jjk71mv.1kja10g@ifi.uio.no>
2002-12-11 12:07 ` 2.4.20 AGP for I845 wrong ? Nicolas ASPERT
2002-12-11 12:20   ` Dave Jones [this message]
2002-12-11 12:26     ` Nicolas ASPERT
2002-12-11 12:38     ` [Dri-devel] " Keith Whitwell
2002-12-11 12:45     ` Keith Whitwell
2002-12-11 13:05       ` Dave Jones
2002-12-11 13:40         ` Keith Whitwell
2002-12-12  1:58   ` David Dawes
2002-12-12  8:57     ` Nicolas ASPERT
2002-12-11 12:16 ` Nicolas ASPERT
2002-12-20 15:09 Margit Schubert-While
  -- strict thread matches above, loose matches on Subject: below --
2002-12-10 18:42 Margit Schubert-While

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=20021211132059.C11689@suse.de \
    --to=davej@suse.de \
    --cc=Nicolas.Aspert@epfl.ch \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=faith@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=margitsw@t-online.de \
    /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