public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christof Efkemann <efkemann@uni-bremen.de>
To: Robert Love <rml@tech9.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Intel 830 support for agpgart
Date: Tue, 2 Oct 2001 15:10:51 +0200	[thread overview]
Message-ID: <20011002151051.488306ee.efkemann@uni-bremen.de> (raw)
In-Reply-To: <1001988137.2780.53.camel@phantasy>
In-Reply-To: <20011002033227.6e047544.efkemann@uni-bremen.de> <1001988137.2780.53.camel@phantasy>

On 01 Oct 2001 22:02:08 -0400
Robert Love <rml@tech9.net> wrote:

> You don't need all that code.  If agp_try_unsupported works, then
> intel_generic_setup works, so you don't need an intel_830_setup.
> 
> In other words, if agp_try_unsupported=1 makes everything OK, then you
> just need to add the detection code.
> 
> Thus, the patch becomes the following.  Give that a try.

Yes, that seems to work as well.  Although there are two minor things I
noticed:
- First, intel_generic_setup sets num_aperture_sizes to 7, while the i830
  has only 4 valid values (32 to 256 MB).
- Second, when intel_generic_configure clears the error status register, it
  resets bits 8, 9 and 10.  With an i830 it should clear bits 2, 3 and 4.

So I'm not sure if this works in general, or could it cause errors on other
systems?

-- 
Regards,
Christof Efkemann

  reply	other threads:[~2001-10-02 13:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-02  1:32 [PATCH] Intel 830 support for agpgart Christof Efkemann
2001-10-02  2:02 ` Robert Love
2001-10-02 13:10   ` Christof Efkemann [this message]
2001-10-02 23:45     ` Robert Love
2001-10-03  0:16       ` David Weinehall
2001-10-03  2:20         ` Robert Love
2001-10-03  2:52           ` David Weinehall
2001-10-03 11:55             ` Christof Efkemann
2001-10-06 23:47           ` Paul Mundt
2001-10-07  1:30             ` Wenzhuo Zhang

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=20011002151051.488306ee.efkemann@uni-bremen.de \
    --to=efkemann@uni-bremen.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@tech9.net \
    /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