All of lore.kernel.org
 help / color / mirror / Atom feed
* Tester wanted: Timing management
@ 2010-10-11  9:01 Martin Peres
       [not found] ` <4CB2D281.7010705-Iz16wY1oaNPLSKGbIzaifA@public.gmane.org>
  0 siblings, 1 reply; 3+ messages in thread
From: Martin Peres @ 2010-10-11  9:01 UTC (permalink / raw)
  To: nouveau

  Hi,

Roy Spliet, Emil Velikov and I are working on getting memory timing 
support to nouveau (http://en.wikipedia.org/wiki/Memory_timings).

We badly need your help as the vbios timing table (that stores the 
timings that should be set when we up/down-clock the memory clocks) 
contains a lot of magic.

If you want to help us, please follow this link:
http://github.com/pathscale/pscnv/wiki/TestingTimings

For those who already sent us your info and had a bios table containing 
timing values, please re-read the page, we now also need the strap 
register now (sorry).

Thanking you by advance.

Cheers,

Martin

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Tester wanted: Timing management
       [not found] ` <4CB2D281.7010705-Iz16wY1oaNPLSKGbIzaifA@public.gmane.org>
@ 2010-10-11 21:06   ` Xavier Chantry
  2010-10-16 19:28   ` Martin Peres
  1 sibling, 0 replies; 3+ messages in thread
From: Xavier Chantry @ 2010-10-11 21:06 UTC (permalink / raw)
  To: Martin Peres; +Cc: nouveau

On Mon, Oct 11, 2010 at 11:01 AM, Martin Peres
<martin.peres-Iz16wY1oaNPLSKGbIzaifA@public.gmane.org> wrote:
>  Hi,
>
> Roy Spliet, Emil Velikov and I are working on getting memory timing support
> to nouveau (http://en.wikipedia.org/wiki/Memory_timings).
>
> We badly need your help as the vbios timing table (that stores the timings
> that should be set when we up/down-clock the memory clocks) contains a lot
> of magic.
>
> If you want to help us, please follow this link:
> http://github.com/pathscale/pscnv/wiki/TestingTimings
>
> For those who already sent us your info and had a bios table containing
> timing values, please re-read the page, we now also need the strap register
> now (sorry).
>
> Thanking you by advance.
>

I checked the two regs on my nv84 laptop with nouveau and blob at the
3 perf levels.
On blob, I see that perf level $i seems to correspond to bios entry $i
with i=0,1,2
On nouveau, I always get same value as with blob on max level (2).

So two questions :
1) are you not interested in getting the values for each perf level
while running the blob ?
2) does it mean that the timings set on boot are already the best
ones, at least for my card ?

nouveau perf level 0,1,2
00100220: 09162728 0c01080c 0008080c 1e160909
00100230: 28000808 270c0c09 00320137 04090202
same as blob on level 2

blob
level 0
00100220: 02040606 0b010707 00020102 19160404
00100230: 28000808 06020702 00320132 04040202
similar to entry 0

level 1
00100220: 050a1112 0b010709 00040305 1b160606
00100230: 28000808 11050905 00320134 04060202
similar to entry 1

level 2
00100220: 09162728 0c01080c 0008080c 1e160909
00100230: 28000808 270c0c09 00320137 04090202
similar to entry 2


Timing table at c706. Version 10.
Header:
c706: 10 04 0c 10

12 entries
c70a: 09 05 05 06 00 06 00 04 00 02 02 01 02 08 00 00
Entry 0: RP(6), RAS(6), RFC(4), RC(2)
Registers: 220: 02040606 0b010704 02020102 00000000
           230: 00000808 06020702 00000000 00000000

c71a: 09 05 07 12 00 11 00 0a 00 05 05 03 04 08 00 00
Entry 1: RP(18), RAS(17), RFC(10), RC(5)
Registers: 220: 050a1112 0b010706 04040305 00000000
           230: 00000808 11050705 00000000 00000000

c72a: 0a 06 0a 28 00 27 00 16 00 09 0c 08 08 08 02 00
Entry 2: RP(40), RAS(39), RFC(22), RC(9)
Registers: 220: 09162728 0c010809 0808080c 00000000
           230: 00000808 270c0709 00000000 00000000

c73a: 0a 06 0b 28 00 27 00 16 00 0c 0c 08 08 08 02 00
Entry 3: RP(40), RAS(39), RFC(22), RC(12)
Registers: 220: 0c162728 0c01080a 0808080c 00000000
           230: 00000808 270c070c 00000000 00000000

c74a: 09 05 07 06 00 06 00 04 00 02 02 01 02 08 00 00
Entry 4: RP(6), RAS(6), RFC(4), RC(2)
Registers: 220: 02040606 0b010706 02020102 00000000
           230: 00000808 06020702 00000000 00000000

c75a: 0c 07 0b 24 00 2d 00 1a 00 0d 0c 08 08 07 02 00
Entry 5: RP(36), RAS(45), RFC(26), RC(13)
Registers: 220: 0d1a2d24 0e01090a 0808080c 00000000
           230: 00000707 2d0c070d 00000000 00000000

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Tester wanted: Timing management
       [not found] ` <4CB2D281.7010705-Iz16wY1oaNPLSKGbIzaifA@public.gmane.org>
  2010-10-11 21:06   ` Xavier Chantry
@ 2010-10-16 19:28   ` Martin Peres
  1 sibling, 0 replies; 3+ messages in thread
From: Martin Peres @ 2010-10-16 19:28 UTC (permalink / raw)
  To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW

[-- Attachment #1: Type: text/plain, Size: 1885 bytes --]

  Le 11/10/2010 11:01, Martin Peres a écrit :
>  Hi,
>
> Roy Spliet, Emil Velikov and I are working on getting memory timing 
> support to nouveau (http://en.wikipedia.org/wiki/Memory_timings).
>
> We badly need your help as the vbios timing table (that stores the 
> timings that should be set when we up/down-clock the memory clocks) 
> contains a lot of magic.
>
> If you want to help us, please follow this link:
> http://github.com/pathscale/pscnv/wiki/TestingTimings
>
> For those who already sent us your info and had a bios table 
> containing timing values, please re-read the page, we now also need 
> the strap register now (sorry).
>
> Thanking you by advance.
>
> Cheers,
>
> Martin
Hi,

5 days later, I've finally processed all the vbios I received (more than 
300 mails, 275 vbios in the end).

I first received a bit more than 80 mails because of phoronix 
(http://www.phoronix.com/scan.php?page=news_item&px=ODY2Nw and 
http://www.phoronix.com/scan.php?page=news_item&px=ODY3Mw 
<http://www.phoronix.com/scan.php?page=news_item&px=ODY3Mw>) and then, I 
received a lot, lot, lot more all of a sudden. It happens that a Russian 
linux website has relayed the call 
(http://www.linux.org.ru/news/hardware/5438270).
I would like to thank them both for relaying my little call, I wasn't 
expecting such a big response!

I created a private git repository to store them all and make them 
accessible to some devs. If anyone has a problem with that, please let 
me know.

Also, with almost 300 vbios in the database, I thought it would be cool 
to make some stats on the userbase who answered to our call.
The diagrams speak for themselves. You'll find them enclosed in a pdf 
(for the diagrams), a csv (for raw data) or an ods (for both).

Thanks again to all of you who sent the information on your card!

Cheers,

Martin

[-- Attachment #2: stats.pdf --]
[-- Type: application/pdf, Size: 35030 bytes --]

[-- Attachment #3: stats.ods --]
[-- Type: application/vnd.oasis.opendocument.spreadsheet, Size: 21587 bytes --]

[-- Attachment #4: stats.csv --]
[-- Type: text/csv, Size: 464 bytes --]

"Chipset","All","nv40","nv42","nv43","nv44","nv45","nv46","nv47","nv49","nv4a","nv4b","nv4c","nv4e","nv50","nv67","nv68","nv84","nv86","nv92","nv94","nv96","nv98","nva0","nva3","nva5","nva8","nvaa","nvac","nvc0","nvc4"
"vbios count",275,1,1,12,2,1,7,3,7,2,17,1,3,3,1,1,32,38,40,12,17,16,6,10,11,18,3,8,1,1
,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
"Chipset Generation","All","nv40","nv50","nvc0",,,,,,,,,,,,,,,,,,,,,,,,,,
"vbios count",275,59,214,2,,,,,,,,,,,,,,,,,,,,,,,,,,

[-- Attachment #5: Type: text/plain, Size: 181 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2010-10-16 19:28 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-10-11  9:01 Tester wanted: Timing management Martin Peres
     [not found] ` <4CB2D281.7010705-Iz16wY1oaNPLSKGbIzaifA@public.gmane.org>
2010-10-11 21:06   ` Xavier Chantry
2010-10-16 19:28   ` Martin Peres

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.