Re: [XFree86] [4.3.0] nv driver: videoram option

2003-03-20 Thread GoTaR
On Mon, Mar 17, 2003 at 15:05:42 -0500, Mark Vojkovich wrote:

  Ramdisk located in video ram would be overwritten if something else (in
  ths case - X) use this video ram.
 
You can't do that.  Not only would you not want to do that 
 because of the horrible performance reading from video ram,

Is the performance worst than hard disk?

 NVIDIA
 hardware has critical state stored in videoram.  The chip will
 hang if it gets corrupted.

It's my risk. Anyway, it doesn't matter - the option shall not end with
sig11.

-- 
GoTaR priv0.onet.pl-gotar
PLD stuff at http://mops.uci.agh.edu.pl/~gotar/
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86


Re: [XFree86] [4.3.0] nv driver: videoram option

2003-03-17 Thread Mark Vojkovich
On Mon, 17 Mar 2003, GoTaR wrote:

 On Sun, Mar 16, 2003 at 16:51:33 -0500, Mark Vojkovich wrote:
 
   I want to reduce memory being used in order to use the rest as a
   ramdisk.
  
 I don't understand that.  What does reducing the amount of
  videoram have to do with a ramdisk?
 
 Ramdisk located in video ram would be overwritten if something else (in
 ths case - X) use this video ram.

   You can't do that.  Not only would you not want to do that 
because of the horrible performance reading from video ram, NVIDIA
hardware has critical state stored in videoram.  The chip will
hang if it gets corrupted.


Mark.   

___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86


Re: [XFree86] [4.3.0] nv driver: videoram option

2003-03-16 Thread Mark Vojkovich
On Sun, 16 Mar 2003, GoTaR wrote:

 Hi!
 
 Setting VideoRam to lowest value than real amount of VRAM is causes:
 
 (WW) NV(0): Failed to set up write-combining range (0xd1f05800,0x400)
 (WW) NV(0): Failed to set up write-combining range (0xd1f05000,0xc00)
 (WW) NV(0): Failed to set up write-combining range (0xd000,0x1f05c00)
 
*** If unresolved symbols were reported above, they might not
*** be the reason for the server aborting.
 
 Fatal server error:
 Caught signal 11.  Server aborting
 
 on my GF2MX200 and ftp://ftp.nest.pld.org.pl/test/athlon/ packages.
 AFAIR in previous versions (4.2.x) it was working fine.
 Is it my soft/hardware problem or anyone else noticed the same reaction?
 
 I want to reduce memory being used in order to use the rest as a
 ramdisk.

   I don't understand that.  What does reducing the amount of
videoram have to do with a ramdisk?

   I see no reason to force VideoRam to lower than what there
actually is, but if you do it's possible that something in 
core XFree86 code requires it to be a power of two.  Write combine
ranges can only be setup on power of two apertures.  Nothing in
the nv driver has changed in this respect.


Mark.

___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86


Re: [XFree86] [4.3.0] nv driver: videoram option

2003-03-16 Thread GoTaR
On Sun, Mar 16, 2003 at 16:51:33 -0500, Mark Vojkovich wrote:

  I want to reduce memory being used in order to use the rest as a
  ramdisk.
 
I don't understand that.  What does reducing the amount of
 videoram have to do with a ramdisk?

Ramdisk located in video ram would be overwritten if something else (in
ths case - X) use this video ram.
I thought the idea up and Michal Schulz gave the solution and detailed
description, which you can find at:
http://hedera.linuxnews.pl/_news/2002/09/03/_long/1445.html
Caution in 5th point misses the true in the last sentence.
Is there another way to say to X not to touch specified region of video
memory?

I see no reason to force VideoRam to lower than what there
 actually is,

As you can see it's good solution for limited memory systems with modern
graphics adapters (up to 128MB of VRAM).

 but if you do it's possible that something in 
 core XFree86 code requires it to be a power of two.  Write combine
 ranges can only be setup on power of two apertures.

I've tried 16384, 8192 and 4096 - these are powers of 2.

 Nothing in the nv driver has changed in this respect.

So where's the bug? Reducing works with tseng driver on my second video
board - ET6100.

-- 
GoTaR priv0.onet.pl-gotar
PLD stuff at http://mops.uci.agh.edu.pl/~gotar/
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86