search for: 24bpp

The problem with 24bpp is that it is a rather unusual depth these days, cirrus is pretty much the only relevant device still using that, and it is a endless source of issues. Wayland doesn't support it at all. Bugs in Xorg keep showing up. Typically either 32bpp or 16bpp are used. Using 32bpp would limit the reso...

The problem with 24bpp is that it is a rather unusual depth these days, cirrus is pretty much the only relevant device still using that, and it is a endless source of issues. Wayland doesn't support it at all. Bugs in Xorg keep showing up. Typically either 32bpp or 16bpp are used. Using 32bpp would limit the reso...

This release rolls up a few minor bug fixes since 2.4.0. We now refuse to run on machines with UEFI firmware (on Linux only, patches welcome for other OSes) since it won't work in the general case and you probably have a kernel framebuffer driver running already. We also only attempt to use 24bpp if the alternative would be pseudocolor, but note that since xserver 1.20 24bpp will not work at all. If you'd like to fix that case, please note that it is filed as issue #4: https://gitlab.freedesktop.org/xorg/driver/xf86-video-vesa/-/issues/4 We also notice several cases of running on emul...

cirrus can handle 1024x768 (and slightly higher) with 24bpp depth. cirrus can handle up to 800x600 with 32bpp. The problem with 24bpp is that it is a rather unusual depth these days, cirrus is pretty much the only relevant device still using that, and it is a endless source of issues. Wayland doesn't support it at all. Bugs in Xorg keep showing up....

On Fri, Jul 06, 2018 at 02:35:07PM -0400, Adam Jackson wrote: > On Fri, 2018-07-06 at 11:12 +0200, Gerd Hoffmann wrote: > > cirrus can handle 1024x768 (and slightly higher) with 24bpp depth. > > cirrus can handle up to 800x600 with 32bpp. > > 16bpp is maybe a better choice? Nobody's using cirrus because they care > about color fidelity and it'll use less CPU to update. There's > precedent here, mgag200 defaults to 16bpp on sufficiently memory- >...

...m? : "Half Life need at least a 16bit color depth to run, usually this is "32768" or "65535" colors" I tried many settings in config, and it doesn't work. I have Wine 20010809 from Debian binaries ( other versions don't work too ) and X 4.1.0 with TrueColor (24bpp) color depth on Nvidia card. -- Pozdrawiam Jakub "Kraju" Krajewski | kraju@no-spam.lnet.int.pl | ICQ 15671406 "The greatest warriors are the ones who fight for peace."

Hi, > If not for TTM, what would be the alternative? One VMA manager per > memory region per device? Depends pretty much on the device. The cirrus is a display device with only 4 MB of vram. You can't fit much in there. A single 1024x768 @ 24bpp framebuffer needs more 50% of the video memory already. Which is why the cirrus driver (before the rewrite) had to migrate buffers from/to vram on every page flip[1]. Which is one[2] of the reasons why cirrus (after rewrite) doesn't ttm-manage the vram any more. gem objects are managed with...

Hi, > If not for TTM, what would be the alternative? One VMA manager per > memory region per device? Depends pretty much on the device. The cirrus is a display device with only 4 MB of vram. You can't fit much in there. A single 1024x768 @ 24bpp framebuffer needs more 50% of the video memory already. Which is why the cirrus driver (before the rewrite) had to migrate buffers from/to vram on every page flip[1]. Which is one[2] of the reasons why cirrus (after rewrite) doesn't ttm-manage the vram any more. gem objects are managed with...

...t is called from other players (AFAIK, it just creates a window then asks mplayer to display in it) with mplayer video.ext, I get this: Playing /home/Sam/Video/iMacAd.mp4. Quicktime/MOV file format detected. [mov] Video stream found, -vid 0 [mov] Audio stream found, -aid 1 VIDEO: [mp4v] 320x240 24bpp 24.000 fps 0.0 kbps ( 0.0 kbyte/s) ========================================================================== Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family Selected video codec: [ffodivx] vfm: ffmpeg (FFmpeg MPEG-4) ========================================================...

Hi again. I've got a laptop with an ATI X600 inside, perfectly working xorg with dual head configuration, 2 desktops (without xinerama). I've got 2 xorg.conf files, one for propietary ATI (fglrx) driver, and other to use the open source driver. The difference is very notorious. The problem I have is that I read (Saint Google) that to work with compiz/beryl and dual-head configuration, I

...t handle 30bpp modes (mplayer hates it for > > xv and x11 rendering, aterm bails on shading the root pixmap, probably > > others) > > > > I'm also told that with DP, it should actually send the higher-bpc > > data over the wire. With HDMI, we're still stuck at 24bpp for now > > (although the hardware can do 36bpp as well). This is why my gradient > > result above was still dithered. > > > > Things to do - mostly nouveau specific, but probably some general > > infra needed too: > > - Figure out how to properly expose the 10...

...ot for TTM, what would be the alternative? One VMA manager per > >> memory region per device? > > > > Depends pretty much on the device. > > > > The cirrus is a display device with only 4 MB of vram. You can't fit > > much in there. A single 1024x768 @ 24bpp framebuffer needs more 50% > > of the video memory already. Which is why the cirrus driver (before the > > rewrite) had to migrate buffers from/to vram on every page flip[1]. Which > > is one[2] of the reasons why cirrus (after rewrite) doesn't ttm-manage the > > vram...

...ring / acceleration - lots of X software can't handle 30bpp modes (mplayer hates it for xv and x11 rendering, aterm bails on shading the root pixmap, probably others) I'm also told that with DP, it should actually send the higher-bpc data over the wire. With HDMI, we're still stuck at 24bpp for now (although the hardware can do 36bpp as well). This is why my gradient result above was still dithered. Things to do - mostly nouveau specific, but probably some general infra needed too: - Figure out how to properly expose the 1024-sized LUT - Add fp16 scanout - Stop relying on the max...

...r 1.20. Adam Jackson (8): Default to 32bpp if the console is 8bpp (and we weren't told otherwise) Use own thunk functions instead of fbdevHW*Weak Pass the pci device (if any) through to fbdevhw in probe and preinit Fix shadow fb allocation size (v2) Remove dead pix24bpp variable Use shadowUpdate32to24 at 24bpp Update for 1.20 ABI fbdev 0.5.0 Alan Coopersmith (3): configure: Drop AM_MAINTAINER_MODE autogen.sh: Honor NOCONFIGURE=1 Use #ifdef instead of #if to avoid build error Emil Velikov (1): autogen.sh: use quoted strin...

...> Hi, > > > If not for TTM, what would be the alternative? One VMA manager per > > memory region per device? > > Depends pretty much on the device. > > The cirrus is a display device with only 4 MB of vram. You can't fit > much in there. A single 1024x768 @ 24bpp framebuffer needs more 50% > of the video memory already. Which is why the cirrus driver (before the > rewrite) had to migrate buffers from/to vram on every page flip[1]. Which > is one[2] of the reasons why cirrus (after rewrite) doesn't ttm-manage the > vram any more. gem objec...

...a explorer desktop window, with for ex. wine explorer /desktop=0,1680x1050 "C:\\Program Files\\CCP\\EVE\\eve.exe", my problem is now -> i can not switch in the game eveonline client to the 16bit windowmode (only 24bit are available) ! My Linux Gnome Desktop are running in a 1680x1050 24bpp mode. But if i start the game in fullscreen, i can switch then into 16bit and any resolution. (its weird) i dont now since when this happend, because i updated the nvidia driver and the wine version at the same time. :( i dont know if the nvidia driver or the wine package are responsible for this....

...fine CIR_*_VERSION* using PACKAGE_VERSION_* Dave Airlie (5): cirrus initial pci access support test for 1/4 bpp in case server is configured with them off make dist check pass fixup iomapsize so we only map the 4k not 16k which is an error cirrus: set default depth to 24bpp Matthieu Herrb (1): Makefile.am: nuke RCS Id git tag: xf86-video-cirrus-1.2.0 http://xorg.freedesktop.org/archive/individual/driver/xf86-video-cirrus-1.2.0.tar.bz2 MD5: c8c8cae0f0b6bff0619c679af4ab0159 xf86-video-cirrus-1.2.0.tar.bz2 SHA1: 4e6adc47eca3965b9f6d44590bf3cb5bbce58181 xf86-vi...

...rk through testing other programs). The application starts fine (and seems to actually run OK) - except that the window pane for the model stays resolutely black. With X in 16bpp, we do get a 'floating point exception' and an assertion about a camera being undefined; this does not happen in 24bpp. In either case, no graphics are displayed. As I am not a Wine developer - and indeed have no knowledge of the inner workings of either Wine or windows - I am somewhat at a loss here. I have a _very_ speculative theory: The viewer is written in Borland C++ Builder, and when I've earlier tried...

...: Implement GdipCreateMetafileFromFile. gdiplus: Implement GdipGetMetafileHeaderFromWmf. gdiplus: Implement GdipGetMetafileHeaderFromStream. gdiplus: Implement GdipGetMetafileHeaderFromFile. windowscodecs: Avoid extra conversion step BGR->RGB when converting 32bpp BGRA to 24bpp RGB. windowscodecs: Add support for 32bppGrayFloat format. windowscodecs: Add support for converting to 8bpp grayscale format. windowscodecs: Add support for converting 32bpp grayscale float to 24bpp BGR format. Hans Leidekker (7): webservices: Implement WsWriteArray....

...s (mplayer hates it for >> > xv and x11 rendering, aterm bails on shading the root pixmap, probably >> > others) >> > >> > I'm also told that with DP, it should actually send the higher-bpc >> > data over the wire. With HDMI, we're still stuck at 24bpp for now >> > (although the hardware can do 36bpp as well). This is why my gradient >> > result above was still dithered. >> > >> > Things to do - mostly nouveau specific, but probably some general >> > infra needed too: >> > - Figure out how to...