search for: 32bpp

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. So using 32bpp by default is the better choice IMO...

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- > impaired devices. Yeah nouveau does the same fallback to 1...

...EC_STRING> for configuring virtual frame buffer devices Sets the amount of RAM which the emulated video card will contain, which in turn limits the resolutions and bit depths which will be available. -The default amount of video ram for stdvga is 8MB which is sufficient -for e.g. 1600x1200 at 32bpp and videoram option is currently working -only when using the qemu-xen-traditional device-model. - -When using the emulated Cirrus graphics card (B<vga="cirrus">) -the amount of video ram is fixed at 4MB which is sufficient -for 1024x768 at 32 bpp and videoram option is currently wo...

...OK, well that makes a *ton* of sense (8bpp being broken). > > I think the idea of bpp reduction is that when you're on your shiny > new Riva TNT with 16MB of VRAM, you don't want to go crazy allocating > all that to a pinned fbcon - almost half of that would go to a single > 32bpp 1600x1200 buffer, more for 1920x1200. You want to be able to > have at least a few fb-sized buffers for backbuffer rendering, etc. > > The specific limits could probably use tweaking - I think they only > consider VRAM size, not the fb size. > > I guess 8bpp worked prior to the ch...

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 resolution to 800x600 due to hardware constrains. So lets go with 16bpp. Also use the default depth for the framebuffer console. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- drivers/gpu/drm/cirrus/cirrus_drv.c | 4 ++-- drivers/...

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 resolution to 800x600 due to hardware constrains. So lets go with 16bpp. Also use the default depth for the framebuffer console and mode_info->preferred_depth. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- drivers/gpu/drm/cirrus...

...16,18 @@ Sets the amount of RAM which the emulated video card will contain, which in turn limits the resolutions and bit depths which will be available. This option is only available when using the B<stdvga> -option (see below). The default is 8MB which is sufficient for -e.g. 1600x1200 at 32bpp. When not using the B<stdvga> option the -amount of video ram is fixed at 4MB which is sufficient for 1024x768 -at 32 bpp. +option (see below). +The default amount of video ram for stdvga is 8MB which is sufficient +for e.g. 1600x1200 at 32bpp. + +When using the emulated Cirrus graphics car...

...t; > This might be the big sticking point, this is a userspace regression > > for a feature that was explicitly added a few years ago, can we really > > get away without it? > > Well, I can reintroduce the module option. I don't see any other > reasonable way to support 32bpp. If the driver reports XR24 as > supported and also adds the higher resolutions (which work with RG16 > only) to the mode list userspace will of course try the higher > resolutions with XR24 and struggle ... Maybe atomic userspace is better (it should be, it can do TEST_ONLY), but I'...

...t; > This might be the big sticking point, this is a userspace regression > > for a feature that was explicitly added a few years ago, can we really > > get away without it? > > Well, I can reintroduce the module option. I don't see any other > reasonable way to support 32bpp. If the driver reports XR24 as > supported and also adds the higher resolutions (which work with RG16 > only) to the mode list userspace will of course try the higher > resolutions with XR24 and struggle ... Maybe atomic userspace is better (it should be, it can do TEST_ONLY), but I'...

...bpp being broken). >>> >>> I think the idea of bpp reduction is that when you're on your shiny >>> new Riva TNT with 16MB of VRAM, you don't want to go crazy allocating >>> all that to a pinned fbcon - almost half of that would go to a single >>> 32bpp 1600x1200 buffer, more for 1920x1200. You want to be able to >>> have at least a few fb-sized buffers for backbuffer rendering, etc. >>> >>> The specific limits could probably use tweaking - I think they only >>> consider VRAM size, not the fb size. >>>...

...bpp being broken). >>> >>> I think the idea of bpp reduction is that when you're on your shiny >>> new Riva TNT with 16MB of VRAM, you don't want to go crazy allocating >>> all that to a pinned fbcon - almost half of that would go to a single >>> 32bpp 1600x1200 buffer, more for 1920x1200. You want to be able to >>> have at least a few fb-sized buffers for backbuffer rendering, etc. >>> >>> The specific limits could probably use tweaking - I think they only >>> consider VRAM size, not the fb size. >>>...

On Fri, Apr 07, 2017 at 10:29:00AM +0200, Gerd Hoffmann wrote: > Hi, > > > Hmm. Maybe it's still possible to salvage something by redefining the > > BIG_ENDIAN format bit to mean the "the other endianness". Ugly but it > > might still result in something usable. > > Also at least for the virtual machine use case this doesn't buy us much. > The

On Fri, Apr 07, 2017 at 10:29:00AM +0200, Gerd Hoffmann wrote: > Hi, > > > Hmm. Maybe it's still possible to salvage something by redefining the > > BIG_ENDIAN format bit to mean the "the other endianness". Ugly but it > > might still result in something usable. > > Also at least for the virtual machine use case this doesn't buy us much. > The

Hi, I have been using syslinux on my portable disk with success on many types of machines (both bios boot and EFI boot) I however hit a small issue recently If I use menu.c32, on some UEFI systems (HP) the menu does not appear after the vendor splash screen. The system however goes ahead and after the timeout configured in the menu system syslinux boots the kernel. I can then (after kernel

...epth 24. CConn: Using pixel format depth 6 (8bpp) rgb222 CConn: Using ZRLE encoding Mon Jul 7 10:42:26 2008 CConn: Throughput 20000 kbit/s - changing to hextile encoding CConn: Throughput 20000 kbit/s - changing to full colour CConn: Using pixel format depth 24 (32bpp) little-endian rgb888 CConn: Using hextile encoding .... Everything progresses as expected during the install and the install completes normally. After installation, I am using the following syntax from a python file to start up the domU: # cat solhvm.py name = "solhvm" vcpus...

...ugh I doubt they are following it. Their > input / comments might be helpful, not only for this particular case > but for others, and for improving both, the UEFI implementations in HP > machines and (vesa)menu.c32 under UEFI. > > Regards, > Ady. > > PS: MS requires 1024x768 32bpp as minimum GOP mode in WHQL. I would not > be surprised if some UEFI Class 3 systems end up not supporting > 640x480. > > >> _______________________________________________ >> Syslinux mailing list >> Submissions to Syslinux at zytor.com >> Unsubscribe or set opt...

CS is now launching. This is an log from console: Code: ~$ wine c:\\CS16v26\\hl.exe -32bpp fixme:win:EnumDisplayDevicesW ((null),0,0x32f524,0x00000000), stub! fixme:gl_compat:add_gl_compat_wrappers GL implementation supports GL_ARB_fragment_program but not GL_EXT_fog_coord fixme:gl_compat:add_gl_compat_wrappers The fog coord emulation will most likely fail E: shm.c: mmap() failed: Cannot...

http://bugs.winehq.org/show_bug.cgi?id=1984 I think this deserves some attention. NetStorm tries to switch from 32bpp to 8bpp, but can't, even though X does have 8bpp configured.

...bpp reduction is weird. OK, well that makes a *ton* of sense (8bpp being broken). I think the idea of bpp reduction is that when you're on your shiny new Riva TNT with 16MB of VRAM, you don't want to go crazy allocating all that to a pinned fbcon - almost half of that would go to a single 32bpp 1600x1200 buffer, more for 1920x1200. You want to be able to have at least a few fb-sized buffers for backbuffer rendering, etc. The specific limits could probably use tweaking - I think they only consider VRAM size, not the fb size. I guess 8bpp worked prior to the change you bisected though, so...