From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Nicolas Aspert <Nicolas.Aspert@epfl.ch>
Cc: Alessandro Morelli <alex@alphac.it>,
linux-kernel@vger.kernel.org, stilgar2k@wanadoo.fr
Subject: Re: [PATCH,CFT] Tentative fix for mem. corruption caused by intel 815 AGP
Date: 27 May 2002 12:03:06 +0100 [thread overview]
Message-ID: <1022497386.11859.232.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <3CF1FD4B.8060608@epfl.ch>
On Mon, 2002-05-27 at 10:32, Nicolas Aspert wrote:
p to */
> + pci_read_config_dword(agp_bridge.dev, INTEL_APBASE, &temp);
> + agp_bridge.gart_bus_addr = (temp & PCI_BASE_ADDRESS_MEM_MASK);
> +
> + /* attbase - aperture base */
> + /* the Intel 815 chipset spec. says that bits 29-31 in the
> + * ATTBASE register are reserved -> try not to write them */
> + if (agp_bridge.gatt_bus_addr & (~ INTEL_815_ATTBASE_MASK))
> + panic("gatt bus addr too high");
> + addr = agp_bridge.gatt_bus_addr & INTEL_815_ATTBASE_MASK;
You need to add + temp&~INTEL_815_ATTBASE_MASK ..
next prev parent reply other threads:[~2002-05-27 10:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.mm4ng1v.vmenaj@ifi.uio.no>
[not found] ` <fa.gciunnv.cnaf99@ifi.uio.no>
2002-05-27 8:11 ` PROBLEM: memory corruption with i815 chipset variant Nicolas Aspert
2002-05-27 9:51 ` Alan Cox
2002-05-27 8:56 ` Nicolas Aspert
2002-05-27 10:17 ` Alan Cox
2002-05-27 9:32 ` [PATCH,CFT] Tentative fix for mem. corruption caused by intel 815 AGP Nicolas Aspert
2002-05-27 11:03 ` Alan Cox [this message]
2002-05-27 10:09 ` Nicolas Aspert
[not found] ` <1022498304.11859.239.camel@irongate.swansea.linux.org.uk>
2002-05-27 11:11 ` Nicolas Aspert
2002-05-27 14:33 ` Alan Cox
2002-05-27 14:08 ` [PATCH,CFT] Tentative fix for agpgart (writing on 'reserved' bits) Nicolas Aspert
[not found] ` <5.1.0.14.0.20020528103408.02ab1260@shiva.intra.alphac.it>
[not found] ` <5.1.0.14.0.20020530110655.02afbb20@shiva.intra.alphac.it>
2002-05-30 9:41 ` 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=1022497386.11859.232.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Nicolas.Aspert@epfl.ch \
--cc=alex@alphac.it \
--cc=linux-kernel@vger.kernel.org \
--cc=stilgar2k@wanadoo.fr \
/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
all inboxes | Powered by JetHome®