From: Adam Mercer <ramercer@gmail.com>
To: Eyal Lebedinsky <eyal@eyal.emu.id.au>
Cc: list linux-kernel <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: 2.6.10-ac3 compile failure
Date: Wed, 5 Jan 2005 09:35:15 +0000 [thread overview]
Message-ID: <799406d6050105013552d3e87b@mail.gmail.com> (raw)
In-Reply-To: <41DB3733.3060002@eyal.emu.id.au>
[-- Attachment #1: Type: text/plain, Size: 377 bytes --]
On Wed, 05 Jan 2005 11:39:15 +1100, Eyal Lebedinsky <eyal@eyal.emu.id.au> wrote:
> CC [M] drivers/char/agp/intel-agp.o
> drivers/char/agp/intel-agp.c: In function `intel_i915_configure':
> drivers/char/agp/intel-agp.c:640: error: too many arguments to function `writel'
> make[3]: *** [drivers/char/agp/intel-agp.o] Error 1
Applying this patch worked for me
Cheers
Adam
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: intel-agp-2.6.10-ac3.patch --]
[-- Type: text/x-patch; name="intel-agp-2.6.10-ac3.patch", Size: 612 bytes --]
--- drivers/char/agp/intel-agp.c-orig 2005-01-04 19:59:59.000000000 +0000
+++ drivers/char/agp/intel-agp.c 2005-01-04 19:50:56.000000000 +0000
@@ -637,7 +637,7 @@
gmch_ctrl |= I830_GMCH_ENABLED;
pci_write_config_word(agp_bridge->dev,I830_GMCH_CTRL,gmch_ctrl);
- writel(agp_bridge->gatt_bus_addr | I810_PGETBL_ENABLED, intel_i830_private.registers,I810_PGETBL_CTL);
+ writel(agp_bridge->gatt_bus_addr | I810_PGETBL_ENABLED, intel_i830_private.registers+I810_PGETBL_CTL);
readl(intel_i830_private.registers+I810_PGETBL_CTL); /* PCI Posting. */
if (agp_bridge->driver->needs_scratch_page) {
next prev parent reply other threads:[~2005-01-05 9:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-05 0:39 2.6.10-ac3 compile failure Eyal Lebedinsky
2005-01-05 9:35 ` Adam Mercer [this message]
2005-01-06 12:41 ` Alan Cox
2005-01-06 16:27 ` Cal Peake
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=799406d6050105013552d3e87b@mail.gmail.com \
--to=ramercer@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=eyal@eyal.emu.id.au \
--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 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.