Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1620016 > unrolled thread
| Started by | Pekka Paalanen <ppaalanen@gmail.com> |
|---|---|
| First post | 2017-04-10 17:20 +0200 |
| Last post | 2017-04-18 23:00 +0200 |
| Articles | 1 on this page of 21 — 4 participants |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [RfC PATCH] drm: fourcc byteorder: brings header file comments in line with reality. Pekka Paalanen <ppaalanen@gmail.com> - 2017-04-10 17:20 +0200
Re: [RfC PATCH] drm: fourcc byteorder: brings header file comments in line with reality. Ilia Mirkin <imirkin@alum.mit.edu> - 2017-04-10 18:20 +0200
Re: [RfC PATCH] drm: fourcc byteorder: brings header file comments in line with reality. Pekka Paalanen <ppaalanen@gmail.com> - 2017-04-11 09:40 +0200
Re: [RfC PATCH] drm: fourcc byteorder: brings header file comments in line with reality. Gerd Hoffmann <kraxel@redhat.com> - 2017-04-11 13:30 +0200
Re: [RfC PATCH] drm: fourcc byteorder: brings header file comments in line with reality. Pekka Paalanen <ppaalanen@gmail.com> - 2017-04-13 09:50 +0200
Re: [RfC PATCH] drm: fourcc byteorder: brings header file comments in line with reality. Ilia Mirkin <imirkin@alum.mit.edu> - 2017-04-11 16:20 +0200
Re: [RfC PATCH] drm: fourcc byteorder: brings header file comments in line with reality. Ilia Mirkin <imirkin@alum.mit.edu> - 2017-04-17 08:50 +0200
Re: [RfC PATCH] drm: fourcc byteorder: brings header file comments in line with reality. Michel Dänzer <michel@daenzer.net> - 2017-04-18 05:00 +0200
Re: [RfC PATCH] drm: fourcc byteorder: brings header file comments in line with reality. Ilia Mirkin <imirkin@alum.mit.edu> - 2017-04-18 07:10 +0200
Re: [RfC PATCH] drm: fourcc byteorder: brings header file comments in line with reality. Michel Dänzer <michel@daenzer.net> - 2017-04-18 08:00 +0200
Re: [RfC PATCH] drm: fourcc byteorder: brings header file comments in line with reality. Gerd Hoffmann <kraxel@redhat.com> - 2017-04-18 12:20 +0200
Re: [RfC PATCH] drm: fourcc byteorder: brings header file comments in line with reality. Michel Dänzer <michel@daenzer.net> - 2017-04-19 03:10 +0200
Re: [RfC PATCH] drm: fourcc byteorder: brings header file comments in line with reality. Ilia Mirkin <imirkin@alum.mit.edu> - 2017-04-19 05:20 +0200
Re: [RfC PATCH] drm: fourcc byteorder: brings header file comments in line with reality. Ilia Mirkin <imirkin@alum.mit.edu> - 2017-04-19 05:30 +0200
Re: [RfC PATCH] drm: fourcc byteorder: brings header file comments in line with reality. Pekka Paalanen <ppaalanen@gmail.com> - 2017-04-19 09:20 +0200
Re: [RfC PATCH] drm: fourcc byteorder: brings header file comments in line with reality. Gerd Hoffmann <kraxel@redhat.com> - 2017-04-19 14:40 +0200
Re: [RfC PATCH] drm: fourcc byteorder: brings header file comments in line with reality. Gerd Hoffmann <kraxel@redhat.com> - 2017-04-18 12:10 +0200
Re: [RfC PATCH] drm: fourcc byteorder: brings header file comments in line with reality. Pekka Paalanen <ppaalanen@gmail.com> - 2017-04-18 13:20 +0200
Re: [RfC PATCH] drm: fourcc byteorder: brings header file comments in line with reality. Gerd Hoffmann <kraxel@redhat.com> - 2017-04-18 15:50 +0200
Re: [RfC PATCH] drm: fourcc byteorder: brings header file comments in line with reality. Pekka Paalanen <ppaalanen@gmail.com> - 2017-04-18 16:10 +0200
Re: [RfC PATCH] drm: fourcc byteorder: brings header file comments in line with reality. Gerd Hoffmann <kraxel@redhat.com> - 2017-04-18 23:00 +0200
Page 2 of 2 — ← Prev page 1 [2]
| From | Gerd Hoffmann <kraxel@redhat.com> |
|---|---|
| Date | 2017-04-18 23:00 +0200 |
| Message-ID | <txIoa-2iz-9@gated-at.bofh.it> |
| In reply to | #1625343 |
Hi, > Right. Very nice if we can trust the virtual machine at least getting > things right, gives some chance for people to test anything. Except... > that's a question of what kind of hardware the virtual machine > emulates. The display device defines what endianess it uses on > framebuffers, not the CPU, right? The display device supports switching the endianess for the framebuffer, at least with kernel 3.19+ and qemu 2.2+. Default endianness depends on the machine type, i.e. ppc64 guests get a bigendian framebuffer and pretty much everything else a little endian framebuffer on reset. The bochs-drm driver switches the display into native endian mode, i.e. big endian for ppc64 and little endian for ppc64le kernels. See commit 9ecdb039b7517dc10b8c3e6dbeb40859178ac28e > > Well, I mean color glitches. But it isn't consistent. As if some > > operations operate with the correct byteorder and some don't. > > alpha/blue being swapped is a problem in some areas. > > > > https://www.kraxel.org/tmp/ > > Ooh, yeah, that's definitely bonkers. > > Maybe the 100% blue things are supposed to be a transparent blended > overlays, like highlights. > > The icons look somehow... not completely right to me. Somehow washed > out? > > Opaque gray shades are hard to tell right from wrong. > > gnome-terminal and the wallpaper look right, but those might be the > only things. > > Having a compositing manager complicates things. In some way yes, in some way no. Tried wayland meanwhile (using "gnome-shell --wayland"). Looks pretty much the same. Window decorations look a bit different (good on xorg, broken on wayland), probably because window decorations work completely different. Otherwise it is bug compatible to xorg. Probably because gnome-shell composites everything using llvmpipe, so it's largely the same code running on both xorg and wayland, which then finally scans out to a dumb framebuffer. cheers, Gerd
[toc] | [prev] | [standalone]
Page 2 of 2 — ← Prev page 1 [2]
Back to top | Article view | linux.kernel
csiph-web