diff options
author | Søren Sandmann Pedersen <ssp@redhat.com> | 2009-01-28 15:07:55 -0500 |
---|---|---|
committer | Søren Sandmann Pedersen <ssp@redhat.com> | 2009-01-28 15:07:55 -0500 |
commit | 75c60beccabbdc10daffe47b3aeca4468c4c9508 (patch) | |
tree | 95e9ff044fda99d3245a478ad83889cb6bdd3066 /TODO | |
parent | 99aca0a6089d8da7872f135579fd560dbbf6aa6d (diff) |
Keep track of physical address of io pages; submit random fill on shadow update
Diffstat (limited to 'TODO')
-rw-r--r-- | TODO | 12 |
1 files changed, 12 insertions, 0 deletions
@@ -5,3 +5,15 @@ - Get rid of qxl_mem.h header; just use qxl.h + +Question: + +- What is the "vram" PCI range used for? + + As I read the Windows driver, it can be mapped with the ioctl + VIDEO_MAP_VIDEO_MEMORY. In driver.c it is mapped as pdev->fb, but + it is then never used for anything as far as I can tell. + + Does Windows itself use that ioctl, and if so, for what. The area + is only 32K in size so it can't really be used for any realistic + bitmaps. |