From: Andrew Morton <akpm@linux-foundation.org>
To: Jerome Glisse <jglisse@redhat.com>
Cc: airlied@gmail.com, dri-devel@lists.sf.net,
linux-kernel@vger.kernel.org, jglisse@redhat.com
Subject: Re: [PATCH] drm/radeon/kms: R3XX/R4XX AGP asic use PCI GART not PCIE GART
Date: Mon, 14 Sep 2009 15:49:38 -0700 [thread overview]
Message-ID: <20090914154938.5d847481.akpm@linux-foundation.org> (raw)
In-Reply-To: <1252583229-13754-1-git-send-email-jglisse@redhat.com>
On Thu, 10 Sep 2009 13:47:09 +0200
Jerome Glisse <jglisse@redhat.com> wrote:
> R3XX/R4XX AGP asic use the old PCI GART block, not the new PCIE GART.
> Make sure we pick the right GART when disabling AGP.
>
This patch doesn't apply to 2.6.31. It's not completely trivial to fix
either - these declarations
+ void r100_pci_gart_tlb_flush(struct radeon_device *rdev);
+ int r100_pci_gart_enable(struct radeon_device *rdev);
+ void r100_pci_gart_disable(struct radeon_device *rdev);
+ int r100_pci_gart_set_page(struct radeon_device *rdev, int i, uint64_t addr);
would naturally lie in radeon_asic.h but we can't do that because some
stupidhead went and put this:
static struct radeon_asic r100_asic = {
into a .h file, making that header file unusable for the things which
header files are used for.
So please have another go.
If you believe that the the patch is suitable for backporting into 2.6.31.x
then please
- cc stable@kernel.org on the patch
- add a `Cc: <stable@kernel.org>' to the changelog
- ensure that the changelog text explains to the -stable maintainers why
this patch should be backported.
Thanks.
next prev parent reply other threads:[~2009-09-14 22:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-10 11:47 Jerome Glisse
2009-09-10 15:28 ` Alex Deucher
2009-09-14 22:49 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-09-09 20:24 Jerome Glisse
2009-09-09 22:05 ` Alex Deucher
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=20090914154938.5d847481.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.sf.net \
--cc=jglisse@redhat.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
all inboxes | Powered by JetHome®