We are using the hacked vesafb driver to inherit the bootloader's framebuffer, keyboard and a USB network card work. ❋ Ben Barren (2006)
It is being cached and manipulated in volatile framebuffer or main RAM, which disappears the moment the device is powered off and is not comparable to the way deleted data can be recovered from persistent storage. ❋ Unknown (2008)
This is why the hack required custom firmware, presumably the hacked firmware sucks the thumbnail out of RAM or the framebuffer and saves it to flash. ❋ Unknown (2008)
"This is why the hack required custom firmware, presumably the hacked firmware sucks the thumbnail out of RAM or the framebuffer and saves it to flash." ❋ Unknown (2008)
The framebuffer. png had to be set as wallpaper, then the overflow. tif file had to be placed in the PHOTO directory on the Memory Stick. ❋ Unknown (2005)
Spent half my morning trying to help one of the random emeritus professors fix his linux setup (hint: loadlin and framebuffer drivers may not mix well). ❋ Unknown (2003)
The framebuffer.png had to be set as wallpaper, then the overflow.tif file had to be placed in the PHOTO directory on the Memory Stick. ❋ Unknown (2005)
Multisampling increases the cost of some stages along this pipeline (notably rasterization, depth/stencil testing, and framebuffer writes), but it does not affect the areas that are most often performance bottlenecks (vertex fetch, vertex shading, texture fetch, and pixel shading). ❋ Shawn Hargreaves - MSFT (2011)
Even if you are bottlenecked by framebuffer bandwidth, hardware designers are clever and can pull all sorts of neat silicon tricks to make multisampling efficient, taking advantage of the coherency where the same color value is usually written many times in a row. ❋ Shawn Hargreaves - MSFT (2011)
Four times as many texture fetches and pixel shader computations, not to mention four times the amount of framebuffer and depth buffer memory, leaves your GPU performing at roughly quarter speed. ❋ Shawn Hargreaves - MSFT (2011)
They used some graphics code originally developed by the One Laptop Per Child OLPC project to do framebuffer rendering. ❋ Ryan Paul (2011)
Distribution: Arch, Gentoo, FreeBSD xorg and framebuffer issues with high resolutions ❋ Slightlystoopid (2010)
First, the console: vesafb, uvesafb, and nvidiafb all fail at delivering a useable framebuffer greater than 1280x1024. vesafb flat out denies anything beyond 795 (0x31B). uvesafb and nvidiafb will fall back on 1280x1024@75Hz, which causes text to flash all over the screen and requires a reboot to remedy. ❋ Slightlystoopid (2010)
The package includes libraries for encryption (AES128/196/256); framebuffer and graphics; ❋ Unknown (2010)
(II) RADEON (0): [drm] framebuffer handle = 0xe0000000 (II) RADEON (0): [drm] ❋ Veeall (2010)
Stefan Dösinger (5): d3d9: Nvidia drivers don't like unused output formats. d3d9: Pass count = 0 when clearing the whole surface. d3d9: Ignore a Windows 7 failure in the d3d9 depth clamp test. d3d9: Windows7 doesn't draw with Viewports bigger than the framebuffer. d3d9: Use color_match in the coissue tests. ❋ Unknown (2010)
Similarly, I ran into problems a few weeks ago in Crux where mplayer playing against the framebuffer was causing hard lockups when the terminal went to blank mode. ❋ K.Mandla (2010)
In other words, after watching a DVD rip for about 20 minutes, when the blank timeout expired, instead of shifting to an all-black screen with the movie overlaid on the framebuffer, the screen went black everywhere, the system locked and there was no recourse except to power down completely. ❋ K.Mandla (2010)
Sync Range: 55-75 Hz Hor. Sync Range: 30-85 kHz Bandwidth: 148 MHz Config Status: cfg = new, avail = yes, need = no, active = unknown Supposedly, the framebuffer should be able to support 1400x1050, but I can't get it, possibly because it's not listed as monitor supported. ❋ Slightlystoopid (2010)
