public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Val Henson <val@nmt.edu>
To: "Victoria W." <wicki@terror.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: agpgart.o and intel i810-chipset
Date: Thu, 23 Aug 2001 11:50:24 -0600	[thread overview]
Message-ID: <20010823115024.L16829@boardwalk> (raw)
In-Reply-To: <Pine.LNX.4.10.10108210734370.27906-100000@csb.terror.de>
In-Reply-To: <Pine.LNX.4.10.10108210734370.27906-100000@csb.terror.de>; from wicki@terror.de on Tue, Aug 21, 2001 at 07:59:43AM +0200

When you do figure out what's wrong, you might want to add your
solution to Toby Russell's i810 howto:

http://www.linuxdoc.org/HOWTO/i810-HOWTO/

-VAL

On Tue, Aug 21, 2001 at 07:59:43AM +0200, Victoria W. wrote:
> hi all,
> 
> since 2 weeks I can't get the agpgrat-module working on my
> intel-i810-chipset:
> 
> 00:00.0 Host bridge: Intel Corporation: Unknown device 7124 (rev 03)
> 00:01.0 VGA compatible controller: Intel Corporation: Unknown device 7125
> (rev 03)
> 
> I can't find the reason of the initial-error while loading agpgart.
> ("no supported devices found"). I made some tests and changes to
> the module-source but I need some background-information and don't know
> where to find them.
> 
> In the driver, there is no case-statement for 
> "PCI_DEVICE_ID_INTEL_810_E_1" like the
> one for "PCI_DEVICE_ID_INTEL_810_E_0" but the one for "810_E_0" searches
> for "PCI_DEVICE_ID_INTEL_810_E_1".
> 
>                 case PCI_DEVICE_ID_INTEL_810_E_0:
>                         i810_dev = pci_find_device(PCI_VENDOR_ID_INTEL,
>                                              PCI_DEVICE_ID_INTEL_810_E_1,
>                                                    NULL);
> 
> I copied this to a new case-statement:
> 
>         case PCI_DEVICE_ID_INTEL_810_E_1:
>         .....   
>         return intel_i810_setup(i810_dev);
> 
> but on loading of the module I get a kernel-oops in
> 
>       if ((INREG32(intel_i810_private.registers, I810_DRAM_CTL)
>            & I810_DRAM_ROW_0) == I810_DRAM_ROW_0_SDRAM) {
>         ....
> 
> 
> Do you have any hints for me?
> I have no experience in kernel-driver development but I'll try to get the
> driver working. 
> Can you tell me, where to find some other usefull information? (I have the
> intel-datasheets, but I'm not shure, if it is a chipset-problem, a bug
> or just a typo in the driver).
> Is here anybody who has an i810-chipset with a working agpgart-driver?
> Please send me an "lspci-listing" an the messages while loading the
> driver. I want to find out the difference to my chipset.
> 
> Thank you in advance
> 
> best regards
> wicki
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

      parent reply	other threads:[~2001-08-23 17:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-21  5:59 agpgart.o and intel i810-chipset Victoria W.
2001-08-21  7:14 ` Chirag Kantharia
2001-08-21 14:10 ` Alan Cox
2001-08-23 17:50 ` Val Henson [this message]

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=20010823115024.L16829@boardwalk \
    --to=val@nmt.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wicki@terror.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