public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christof Efkemann <chref@tzi.de>
To: David Weinehall <tao@acc.umu.se>
Cc: Robert Love <rml@tech9.net>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Intel 830 support for agpgart
Date: Wed, 3 Oct 2001 13:55:59 +0200	[thread overview]
Message-ID: <20011003135559.1b11f0c4.chref@tzi.de> (raw)
In-Reply-To: <20011003045257.Q7800@khan.acc.umu.se>
In-Reply-To: <20011002033227.6e047544.efkemann@uni-bremen.de> <1001988137.2780.53.camel@phantasy> <20011002151051.488306ee.efkemann@uni-bremen.de> <1002066345.1003.66.camel@phantasy> <20011003021658.O7800@khan.acc.umu.se> <1002075650.1237.2.camel@phantasy> <20011003045257.Q7800@khan.acc.umu.se>

On Wed, 3 Oct 2001 04:52:57 +0200
David Weinehall <tao@acc.umu.se> wrote:

> On Tue, Oct 02, 2001 at 10:20:43PM -0400, Robert Love wrote:
> > On Tue, 2001-10-02 at 20:16, David Weinehall wrote:
> > > If the only differences between the different cards are the nr of
> > > aperture-sizes and the status-register settings, why not have a struct
> > > which contains all the valid cards, and use a scan-routine?!

There is already such a struct, agp_bridge_info, and a scan-routine,
agp_lookup_host_bridge.  These values could probably be added easily.
Although it would then be necessary for the other chipsets, too.

> Afaik, speed is not really an issue (it's not like you're going to
> notice a difference anyway, even if you had a struct with 100 different
> adapters in it.) As for reapproaching the size of the current
> implementation, the difference is that you get one single function that
> you don't have to change. You just add one single line to the struct
> for each adapter.

Even if it was slower it wouldn't really matter, as this is executed only
once during initialization.

> > There are only 3 possibilities right now (i830, i840, and everything
> > else).

And don't forget the i850 ;-)

-- 
Regards,
Christof Efkemann

  reply	other threads:[~2001-10-05 18:51 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
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 [this message]
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=20011003135559.1b11f0c4.chref@tzi.de \
    --to=chref@tzi.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@tech9.net \
    --cc=tao@acc.umu.se \
    /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