From: Terence Ripperda <tripperda@nvidia.com>
From: <tripperda@nvidia.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Terence Ripperda <tripperda@nvidia.com>
Subject: 2.6 agpgart and acpi standby/resume
Date: Thu, 22 Jan 2004 12:58:07 -0600 [thread overview]
Message-ID: <20040122185807.GD506@hygelac> (raw)
when working on supporting the 2.6 kernel's acpi support, I ran into some issues on a Dell Inspiron 4100 notebook (w/ Intel Corp. 82830 830 Chipset Host Bridge) when resuming from standby. the basic problem was that agp configuration was lost in the host bridge's pci config space, causing dma problems with our chip.
I checked through the agpgart code (specifically the intel-agp.c driver) and saw that the driver did support acpi resume and attempted to reconfigure the chipset when resuming. but the problem is that the driver only does this if the bridge is using the generic or 845 driver. in my case, the 830mp driver was being used. I hacked in support for my driver and everything worked fine.
I'm curious why support was only added for 2 cases, instead of reconfiguring the chipset in every case. Is this because there were problems with some drivers, or is support added only on an "as-needed" basis?
(in this case, I happen to be testing with 2.6.0, but I see the same problem in the 2.6.1 code)
Thanks,
Terence
this fixed my problem:
--- intel-agp.c.orig 2004-01-22 12:51:31.000000000 -0600
+++ intel-agp.c 2004-01-22 12:51:20.000000000 -0600
@@ -1432,6 +1432,8 @@
intel_configure();
else if (bridge->driver == &intel_845_driver)
intel_845_configure();
+ else if (bridge->driver == &intel_830mp_driver)
+ intel_830mp_configure();
return 0;
}
next reply other threads:[~2004-01-22 18:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-22 18:58 Terence Ripperda, tripperda [this message]
2004-01-22 19:44 ` 2.6 agpgart and acpi standby/resume Dave Jones
2004-01-22 19:53 ` Terence Ripperda, tripperda
2004-01-22 20:06 ` Dave Jones
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=20040122185807.GD506@hygelac \
--to=tripperda@nvidia.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