All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Aspert <Nicolas.Aspert@epfl.ch>
To: Robert Love <rml@tech9.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH]agp for i820 chipset
Date: Tue, 06 Nov 2001 08:19:31 +0100	[thread overview]
Message-ID: <3BE78F03.2090600@epfl.ch> (raw)
In-Reply-To: <3BE6B50A.5010806@epfl.ch> <1004976089.934.12.camel@phantasy> <3BE6D469.8000407@epfl.ch> <1004991553.806.19.camel@phantasy> <1004998482.2277.0.camel@phantasy>

Robert Love wrote:

>
> 
> Hm, one thing to add is if other Intel chipsets have varying APSIZE
> values, and this is all they differ by, and one has an APSIZE of 8bits,
> then you can cheat and just point to that function.
> 


Hello

Finally back to my computer that contains all the info.

In fact, I just gave a quick look to other Intel chipset specs, and I found out 

that the 830, 840, 845, 850, and of course my beloved 820 chipset have a 8 bits 

APSIZE register ! I think this may be the time to write two 'generic' fetch_size

functions : one for the 8 bits register and one for the 16 bits 
register... unless no intel chipset using the generic 'fetch_size' have 
16 bits APSIZE registers, in which case we could replace it...

I'll try to see what I can do, and I will send an update for my patch.

Nicolas.

-- 
Nicolas Aspert      Signal Processing Laboratory (LTS)
Swiss Federal Institute of Technology (EPFL)


  reply	other threads:[~2001-11-06  7:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-05 15:49 [PATCH]agp for i820 chipset Nicolas Aspert
2001-11-05 16:01 ` Robert Love
2001-11-05 18:03   ` Nicolas Aspert
2001-11-05 20:19     ` Robert Love
2001-11-05 22:14       ` Robert Love
2001-11-06  7:19         ` Nicolas Aspert [this message]
     [not found] <linux.kernel.3BE25263.9080108@epfl.ch>
2001-11-02 11:29 ` [PATCH] agp " Nicolas Aspert
  -- strict thread matches above, loose matches on Subject: below --
2001-11-02  7:59 Nicolas Aspert

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=3BE78F03.2090600@epfl.ch \
    --to=nicolas.aspert@epfl.ch \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.