From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Eric Anholt <eric@anholt.net>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
Paulo Zanoni <paulo.r.zanoni@intel.com>
Subject: Re: [RFC] drm: implement DRM_IOCTL_MODE_SETROTATION
Date: Fri, 6 Jan 2012 07:26:37 -0800 [thread overview]
Message-ID: <20120106072637.7ffdaad0@jbarnes-desktop> (raw)
In-Reply-To: <8739btsez0.fsf@eliezer.anholt.net>
On Thu, 05 Jan 2012 19:10:43 -0800
Eric Anholt <eric@anholt.net> wrote:
> On Thu, 5 Jan 2012 14:16:23 -0200, przanoni@gmail.com wrote:
> > From: Paulo Zanoni <paulo.r.zanoni@intel.com>
> >
> > This ioctl is used to signal the drivers that the screen is rotated,
> > not to make the drivers rotate the screen.
> > - add a driver-specific "rotation_set" function
> > - implement Intel's rotation_set by setting the right values to the
> > PIPECONF registers.
> >
> > The idea is that when user-space does rotation, it can call this ioctl
> > to inform the Kernel that we have a rotation. This feature is needed
> > by the KVMr feature of VPro.
>
> So am I following this right, that these register bits are used to
> communicate from one piece of software to another piece of software,
> across the virtualization boundary?
Right, but not for virtualization; these bits are read by the AMT
engine for its built-in KVM functionality.
--
Jesse Barnes, Intel Open Source Technology Center
prev parent reply other threads:[~2012-01-06 15:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 16:16 [RFC] drm: implement DRM_IOCTL_MODE_SETROTATION przanoni
2012-01-05 16:27 ` Daniel Vetter
2012-01-05 16:33 ` Paulo Zanoni
2012-01-05 16:40 ` Jakob Bornecrantz
2012-01-16 19:59 ` Paulo Zanoni
2012-01-16 20:35 ` [Intel-gfx] " Dave Airlie
2012-01-16 20:50 ` Paulo Zanoni
2012-01-05 16:44 ` Chris Wilson
2012-01-06 3:10 ` Eric Anholt
2012-01-06 15:26 ` Jesse Barnes [this message]
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=20120106072637.7ffdaad0@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric@anholt.net \
--cc=intel-gfx@lists.freedesktop.org \
--cc=paulo.r.zanoni@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox