The logic for dealing with non-CPU accessible memory still needs to be added. It's on the todo list.
Just tested the code on F12. I think this kind of works. There is some corruption, but I don't see the driCannotAllocateTexture messages. So, is the logic in place now. Any other way I can test it?
So, is the logic in place now. Any other way I can test it?
Not yet. However, with KMS the CPU accessible memory is a shared pool so any client that needs it can access it. Prior to KMS, memory was statically allocated to certain things.
Not yet. However, with KMS the CPU accessible memory is a shared pool so any client that needs it can access it. Prior to KMS, memory was statically allocated to certain things.
Just got F13. Still see the same behavior as F12. So, I assume its not fully done yet?
Wow! Does this mean the phram module can be used to access the whole vram (and not only the prefetchable one lspci reports)? Thanks
To my understand phram can only use mappable memory, so no phram won't be able to access beyond bar size. That being said using vram as swap or other thing like that is one of the badest idea you can come up with, it would be lot better if you just buy more ram.
To my understand phram can only use mappable memory, so no phram won't be able to access beyond bar size. That being said using vram as swap or other thing like that is one of the badest idea you can come up with, it would be lot better if you just buy more ram.
Sorry, can you explain me why? Having 2 video cards the second one is wasted when I don't need two monitors, so using it at least for its memory would be good IMHO.