All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marcin Kościelnicki" <koriakin-mP9o5jsk0RY@public.gmane.org>
To: Emil Velikov
	<emil.l.velikov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	Fernando Negro <fernando.negro-aPYA7nAdAYY@public.gmane.org>,
	nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: Should I dump my Nvidia card from the less known brand "Gainward"?
Date: Sat, 11 Jan 2014 14:26:45 +0100	[thread overview]
Message-ID: <52D14695.30709@0x04.net> (raw)
In-Reply-To: <52D0C155.1030902-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>


> * there is some missmatch between the reported amount of VRAM vs the one
> calculated
> [ 2.132258] [drm] nouveau 0000:02:00.0: memory controller reports 512MiB
> VRAM
> [ 2.132264] [drm] nouveau 0000:02:00.0: we calculated 1024MiB VRAM
>

I can explain that one: nouveau doesn't know about single-subpartition 
[ie. 32-bit bus width per partition] GT21x parts. While that causes an 
error in memory calculations, the calculations err on the safe side 
(reordering block is 2x larger than it needs to be), and there should be 
no negative consequences.

I'll prepare a fix for that bug once I finish my research on dual-rank 
tesla cards (which likely involve a calculation error that falls on the 
*un*safe side), but for the moment it's nothing to worry about.

Marcin Kościelnicki

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2014-01-11 13:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-10 12:36 Should I dump my Nvidia card from the less known brand "Gainward"? Fernando Negro
     [not found] ` <1389357412.986013756-6x1OHWEv9lxsdVUOrk1QfQ@public.gmane.org>
2014-01-11  3:58   ` Emil Velikov
     [not found]     ` <52D0C155.1030902-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-01-11 13:26       ` Marcin Kościelnicki [this message]
2014-01-11 23:48       ` Fernando Negro

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=52D14695.30709@0x04.net \
    --to=koriakin-mp9o5jsk0ry@public.gmane.org \
    --cc=emil.l.velikov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=fernando.negro-aPYA7nAdAYY@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.