public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Carl D. Blake" <carl@boeckeler.com>
To: linux-kernel@vger.kernel.org
Subject: Re: nforce2 and agpgart
Date: 26 Dec 2002 11:55:16 -0700	[thread overview]
Message-ID: <1040928916.6372.32.camel@vulcan> (raw)
In-Reply-To: <1040685553.2739.30.camel@localhost.localdomain>

On Mon, 2002-12-23 at 16:19, Bongani Hlope wrote:
...snip...
> 
> It was once posted on this list that the NForce is similar to some
> existing hardware. hence the sound driver uses the Intel i810 audio
> driver. I guess if you can search through the archive you might find
> that discussion. If you do find it and _are_ clued-up enough, then you
> can look at drivers/char/agp/agpgart_be.c approximately line 3900 they
> start defining which drivers to use for which bus.
> 
This sounds like a possibility.  However, I cannot find any discussion
about what hardware the nforce2 chipset is similar to.  I just need to
know if the agp portion of the chipset is similar to something else. 
Can anybody point to that information?  From what I can determine the
device that is used is the host bridge.

> So you need to
> 1. Find the id for the AGP bus for the NForce and define it in agp.h
> (lspci should do the trick IIRC on my PC 00:01.0 is the agp bus)
> 2. Find out which hardware the bus is similar to, then add the support
> for the NForce using the setup for that driver
> e.g.
> 
> agp.h
> 
> add
> #ifndef PCI_DEVICE_ID_NVIDIA_NFORCORCE_2   //I'm not sure about the
> naming standard
> #define PCI_DEVICE_ID_NVIDIA_NFORCORCE_2	0x(Hex value from lspci)
> #endif
> 
> the in agpgart_be.c
> 
> add (for example lets say the bus is similar to Intel's i860 agp bus
> then)
> 
> #ifdef CONFIG_AGP_INTEL
> ...
> 
> { PCI_DEVICE_ID_NVIDIA_NFORCORCE_2,
>                 PCI_VENDOR_ID_NVIDIA,
>                 INTEL_I860,
>                 "NVidia",
>                 "NForce2",
>                 intel_860_setup },
> 
> ....
> #endif /* CONFIG_AGP_INTEL */
> 
> DISCLAIMER : I do not know anything about the agp code, except for what
> I have read when trying to find a solution for you. The examples above
> are from what my eyes came across at 1:00 am without prio knowledge to
> the agp code. So if you implement these examples you do it at you own
> (and maybe your pets) risk. The examples come with.... you should now
> how the rest goes ;) 
> 
> -- 
> For future reference - don't anybody else try to send patches as vi
> scripts, please. Yes, it's manly, but let's face it, so is
> bungee-jumping with the cord tied to your testicles.
> 
>                 -- Linus
-- 
Carl D. Blake
Director of Engineering
Boeckeler Instruments, Inc.
4650 S. Butterfield Dr.
Tucson, AZ  85714

Phone: 520-745-0001
FAX: 520-745-0004
email: carl@boeckeler.com

.com


  reply	other threads:[~2002-12-26 18:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-23 18:50 nforce2 and agpgart Carl D. Blake
2002-12-23 21:16 ` Bongani Hlope
2002-12-23 22:40   ` Carl D. Blake
2002-12-23 23:19     ` Bongani Hlope
2002-12-26 18:55       ` Carl D. Blake [this message]
2002-12-23 23:59     ` Jeff Nguyen
2002-12-26 18:55       ` Carl D. Blake
     [not found]       ` <1040928705.6372.27.camel@vulcan>
     [not found]         ` <086101c2ad18$46fea8b0$6502a8c0@jeff>
2002-12-26 20:09           ` Carl D. Blake

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=1040928916.6372.32.camel@vulcan \
    --to=carl@boeckeler.com \
    --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