From: Rui Salvaterra <rsalvaterra@gmail.com>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: "Christian König" <ckoenig.leichtzumerken@gmail.com>,
"debian-powerpc@lists.debian.org"
<debian-powerpc@lists.debian.org>,
"Maling list - DRI developers" <dri-devel@lists.freedesktop.org>,
"John Paul Adrian Glaubitz" <glaubitz@physik.fu-berlin.de>
Subject: Re: [RFC] Remove AGP support from Radeon/Nouveau/TTM
Date: Mon, 11 May 2020 21:25:06 +0100 [thread overview]
Message-ID: <CALjTZvZcg60rgDux7+Kh3zaMBkd-OiqoJ7GyYrLxfvnwgc4Xng@mail.gmail.com> (raw)
In-Reply-To: <CADnq5_NkD4+AMbNJceOJVSeBbJNQ3KDJq-kb7aHyF2jW8Y6dOA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 559 bytes --]
A segunda, 11/05/2020, 21:21, Alex Deucher <alexdeucher@gmail.com> escreveu:
>
>
> Note there is no loss of functionality here, at least on radeon
> hardware. It just comes down to which MMU gets used for access to
> system memory, the AGP MMU on the chipset or the MMU built into the
> GPU. On powerpc hardware, AGP has been particularly unstable, and
> IIRC, AGP has been disabled by default on radeon on powerpc for a
> while.
>
So this basically just drops support for the AGP GART? What happens to the
AGP signalling rates (beyond the base rate)?
>
[-- Attachment #1.2: Type: text/html, Size: 1076 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-05-11 22:52 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 19:55 [RFC] Remove AGP support from Radeon/Nouveau/TTM John Paul Adrian Glaubitz
2020-05-11 20:05 ` Alex Deucher
2020-05-11 20:25 ` Rui Salvaterra [this message]
2020-05-11 20:51 ` Alex Deucher
2020-05-12 7:57 ` Michel Dänzer
2020-05-12 9:21 ` Rui Salvaterra
2020-05-12 9:40 ` Karoly Balogh (Charlie/SGR)
2020-05-12 13:22 ` Alex Deucher
2020-05-12 16:37 ` Daniel Vetter
2020-05-12 17:02 ` Rui Salvaterra
2020-05-12 18:21 ` Alex Deucher
2020-05-12 20:12 ` Dave Airlie
2020-05-13 7:26 ` Christian König
2020-05-12 18:22 ` Alex Deucher
2020-05-13 7:19 ` Daniel Vetter
2020-05-13 7:55 ` Christian König
2020-05-13 10:25 ` Daniel Vetter
2020-05-13 9:28 ` Rui Salvaterra
2020-05-13 10:26 ` Michel Dänzer
2020-05-13 10:29 ` Daniel Vetter
2020-05-13 10:32 ` Michel Dänzer
2020-05-13 10:39 ` Rui Salvaterra
2020-05-13 10:57 ` Michel Dänzer
2020-05-13 11:07 ` Rui Salvaterra
2020-05-13 13:44 ` Christian Zigotzky
2020-05-13 14:01 ` John Paul Adrian Glaubitz
2020-05-13 14:01 ` Rui Salvaterra
2020-05-13 20:19 ` Bertrand Dekoninck
2020-05-13 20:36 ` Rui Salvaterra
2020-05-11 20:41 ` John Paul Adrian Glaubitz
2020-05-11 20:46 ` Alex Deucher
2020-05-11 21:50 ` John Paul Adrian Glaubitz
2020-05-12 7:43 ` Christian König
2020-05-11 20:12 ` Christian König
2020-05-11 20:24 ` John Paul Adrian Glaubitz
2020-05-11 20:48 ` Gerhard Pircher
2020-05-12 5:04 ` David VANTYGHEM
2020-05-12 9:20 ` John Paul Adrian Glaubitz
-- strict thread matches above, loose matches on Subject: below --
2020-05-11 17:17 Christian König
2020-05-11 20:14 ` Al Dunsmuir
2020-05-11 20:27 ` Alex Deucher
2020-05-11 20:43 ` Dave Airlie
2020-05-11 20:56 ` Al Dunsmuir
2020-05-12 8:11 ` Christian König
2020-05-11 20:59 ` Emil Velikov
2020-05-11 20:46 ` Al Dunsmuir
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=CALjTZvZcg60rgDux7+Kh3zaMBkd-OiqoJ7GyYrLxfvnwgc4Xng@mail.gmail.com \
--to=rsalvaterra@gmail.com \
--cc=alexdeucher@gmail.com \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=debian-powerpc@lists.debian.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=glaubitz@physik.fu-berlin.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;
as well as URLs for NNTP newsgroup(s).