From: Gerd Hoffmann <kraxel@redhat.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: lvivier@redhat.com, open list <linux-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org,
"open list:VIRTIO GPU DRIVER"
<virtualization@lists.linux-foundation.org>
Subject: Re: [PATCH 1/2] drm: virtio: add virtio_gpu_translate_format
Date: Mon, 03 Apr 2017 11:05:28 +0200 [thread overview]
Message-ID: <1491210328.17505.34.camel@redhat.com> (raw)
In-Reply-To: <20170403075110.besn4qv53nhwlrhu@phenom.ffwll.local>
On Mo, 2017-04-03 at 09:51 +0200, Daniel Vetter wrote:
> On Mon, Apr 03, 2017 at 09:08:44AM +0200, Gerd Hoffmann wrote:
> > Factors out code, no functional change.
> >
> > Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
>
> Ugh on the big endian define, I guess we'll never managed to figure this
> aspect of drm pixel formats out correctly - they're supposed to encode
> endinaness.
Oh, ok. (reading your patch replies out-of-order).
Yep, in that case it maybe is a good idea to discuss fourcc
semantics ...
cheers,
Gerd
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Gerd Hoffmann <kraxel@redhat.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: dri-devel@lists.freedesktop.org, lvivier@redhat.com,
open list <linux-kernel@vger.kernel.org>,
"open list:VIRTIO GPU DRIVER"
<virtualization@lists.linux-foundation.org>
Subject: Re: [PATCH 1/2] drm: virtio: add virtio_gpu_translate_format
Date: Mon, 03 Apr 2017 11:05:28 +0200 [thread overview]
Message-ID: <1491210328.17505.34.camel@redhat.com> (raw)
In-Reply-To: <20170403075110.besn4qv53nhwlrhu@phenom.ffwll.local>
On Mo, 2017-04-03 at 09:51 +0200, Daniel Vetter wrote:
> On Mon, Apr 03, 2017 at 09:08:44AM +0200, Gerd Hoffmann wrote:
> > Factors out code, no functional change.
> >
> > Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
>
> Ugh on the big endian define, I guess we'll never managed to figure this
> aspect of drm pixel formats out correctly - they're supposed to encode
> endinaness.
Oh, ok. (reading your patch replies out-of-order).
Yep, in that case it maybe is a good idea to discuss fourcc
semantics ...
cheers,
Gerd
next prev parent reply other threads:[~2017-04-03 9:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 7:08 [PATCH 0/2] virtio: fix virtio_gpu_mode_dumb_create Gerd Hoffmann
2017-04-03 7:08 ` [PATCH 1/2] drm: virtio: add virtio_gpu_translate_format Gerd Hoffmann
2017-04-03 7:08 ` Gerd Hoffmann
2017-04-03 7:51 ` Daniel Vetter
2017-04-03 7:51 ` Daniel Vetter
2017-04-03 7:51 ` Daniel Vetter
2017-04-03 9:05 ` Gerd Hoffmann
2017-04-03 9:05 ` Gerd Hoffmann [this message]
2017-04-03 9:05 ` Gerd Hoffmann
2017-04-03 7:08 ` [PATCH 2/2] drm: virtio: fix virtio_gpu_mode_dumb_create Gerd Hoffmann
2017-04-03 7:08 ` Gerd Hoffmann
2017-04-03 7:45 ` Dave Airlie
2017-04-03 7:45 ` Dave Airlie
2017-04-03 7:53 ` Daniel Vetter
2017-04-03 7:53 ` Daniel Vetter
2017-04-03 9:02 ` Gerd Hoffmann
2017-04-03 9:02 ` Gerd Hoffmann
2017-04-03 9:02 ` Gerd Hoffmann
2017-04-03 7:53 ` Daniel Vetter
2017-04-03 7:08 ` Gerd Hoffmann
2017-04-03 8:31 ` [PATCH 0/2] " Laurent Vivier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1491210328.17505.34.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvivier@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.