Displaying 3 results from an estimated 3 matches for "gk1xx".
Did you mean:
gk10x
2014 Apr 21
2
[PATCH v2 09/10] drm/nouveau: support GK20A in nouveau_accel_init()
...e methods
> are not yet supported.
How is GK20A different from a nvc0+ card that lacks PDISPLAY (like all
the 3D Controller ones, and I guess even some that come up as VGA
controller in PCI but don't have any outputs in their VBIOS)? i.e.
what's wrong with just doing the same thing that GK1xx does? Note that
there are sw methods that don't deal with display as well.
-ilia
>
> Signed-off-by: Alexandre Courbot <acourbot at nvidia.com>
> ---
> drivers/gpu/drm/nouveau/nouveau_drm.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/gpu/...
2014 Apr 21
13
[PATCH v2 00/10] drm/nouveau: support for GK20A, cont'd
Hi everyone,
Way overdue v2 of the final patches that enable basic GK20A support. Hopefully
all the issues raised with v1 have been addressed.
Changes since v1:
- Use gk20a clock driver by Ben instead of twiddling nv04's
- Name new classes after gk20a instead of nvea
- Addressed comments about BAR initialization code factorization
- Removed non-essential code which only purpose was to avoid
2014 Mar 23
0
[PATCH] drm/nouveau: allow nv04/nv50/nvc0+ parts of the driver to be separated
...GeForce4
+ GeForce FX
+ GeForce 6
+ GeForce 7
+
+config DRM_NOUVEAU_NV50
+ bool "NV50:NVC0 (G80+, GT215+)"
+ default y
+ help
+ Builds support for all Tesla cards:
+
+ GeForce 8
+ GeForce 9
+ GeForce 200
+ GeForce 300
+
+config DRM_NOUVEAU_NVC0
+ bool "NVC0+ (GF1xx, GK1xx, GK2xx)"
+ default y
+ help
+ Builds support for all Fermi and Kepler cards:
+
+ GeForce 400
+ GeForce 500
+ GeForce 600
+ GeForce 700
+
config NOUVEAU_DEBUG
int "Maximum debug level"
- depends on DRM_NOUVEAU
range 0 7
default 5
help
@@ -48,7 +86,6 @@ config NOUVEA...