All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Xie, William" <william.xie@intel.com>
Cc: DRI Development <dri-devel@lists.freedesktop.org>
Subject: Re: Help on drmModeSetPlane
Date: Mon, 27 Apr 2015 15:48:09 +0300	[thread overview]
Message-ID: <20150427124809.GD18908@intel.com> (raw)
In-Reply-To: <D95B070D38087A47ADCD55E64CDD74BD0EAB4890@SHSMSX101.ccr.corp.intel.com>

On Mon, Apr 27, 2015 at 09:37:54AM +0000, Xie, William wrote:
> Hello, Syrjälä,
>  For drmModeSetPlane API, regarding the ctrc width, height and src width and heitht,
> Do they must 16 byte aligned?
> For example, for the size of 33x66, will these value be supported?

Depends on the hardware/driver implementation. In general the driver
should fudge things enough that you'll get something reasonably close to
what you requested. For Intel hardware we support pixel accurate
coordinates (well, macropixel in the case of packed YUV 4:2:2).
Sub-pixel accuracy isn't supported on current hardware.

> 
> William
> 
> -----Original Message-----
> From: Ville Syrjälä [mailto:ville.syrjala@linux.intel.com] 
> Sent: Friday, April 17, 2015 6:08 PM
> To: Xie, William
> Cc: DRI Development
> Subject: Re: Help on drmModeSetPlane
> 
> On Fri, Apr 17, 2015 at 09:30:02AM +0000, Xie, William wrote:
> > Hello
> > 
> > Does overlay support alpha?
> 
> Depends on the hardware once more. Also we don't have a proper API for it at this time. You may get lucky if you tell it to use a pixel format with alpha. But there's no guarantee what kind of blend equation you will get.
> 
> Also we don't really have an API for the plane Z order either. Some drivers have a property for that, but I don't think it's really well defined.
> 
> > 
> > William
> > 
> > -----Original Message-----
> > From: Ville Syrjälä [mailto:ville.syrjala@linux.intel.com]
> > Sent: Wednesday, April 15, 2015 10:34 PM
> > To: Xie, William
> > Cc: DRI Development
> > Subject: Re: Help on drmModeSetPlane
> > 
> > On Wed, Apr 15, 2015 at 02:24:14PM +0000, Xie, William wrote:
> > > Oh, I tried it on BDW.
> > > So we need to use other way to scale the video to full screen?
> > 
> > Yes, unfortunately.
> > 
> > > 
> > > William
> > > 
> > > 
> > > -----Original Message-----
> > > From: Ville Syrjälä [mailto:ville.syrjala@linux.intel.com]
> > > Sent: Wednesday, April 15, 2015 7:23 PM
> > > To: Xie, William
> > > Cc: DRI Development
> > > Subject: Re: Help on drmModeSetPlane
> > > 
> > > On Wed, Apr 15, 2015 at 08:49:39AM +0000, Xie, William wrote:
> > > > To make it more specific,
> > > > 
> > > > For example:
> > > > 1: video frame size is 1280x720,
> > > > 2: screen resolution is 3200x1800,
> > > > 
> > > > How can I set crtc and src parameters?
> > > > 
> > > > 1: crtc (0, 0, 3200, 1800)  src (0, 0, 3200<<16, 1800<<16)
> > > > 2: crtc (0, 0, 3200, 1800)  src (0, 0, 1280<<16, 720<<16)
> > > > 
> > > > Which one is correct?
> > > 
> > > 2 is correct.
> > > 
> > > What hardware are you trying this on? Do note that on HSW/BDW/VLV/CHV the hardware lost the plane scaling ability. It's coming back on SKL.
> > > 
> > > > 
> > > > William
> > > > 
> > > > From: Xie, William
> > > > Sent: Wednesday, April 15, 2015 3:55 PM
> > > > To: DRI Development; DRI Development
> > > > Subject: Help on drmModeSetPlane
> > > > 
> > > > Question please, could someone share the meaning of the parameters for drmModeSetPlane in libdrm?
> > > > 
> > > > int drmModeSetPlane(int fd, uint32_t plane_id, uint32_t crtc_id,
> > > >                                     uint32_t fb_id, uint32_t flags,
> > > >                                     int32_t crtc_x, int32_t crtc_y,
> > > >                                     uint32_t crtc_w, uint32_t crtc_h,
> > > >                                     uint32_t src_x, uint32_t src_y,
> > > >                                     uint32_t src_w, uint32_t 
> > > > src_h)
> > > > 
> > > > 
> > > > My problem is, whatever value I set, the video is not full screen 
> > > > mode, Anything I missed?
> > > > 
> > > > Thanks
> > > > William
> > > > 
> > > > 
> > > > 
> > > > 
> > > 
> > > > _______________________________________________
> > > > dri-devel mailing list
> > > > dri-devel@lists.freedesktop.org
> > > > http://lists.freedesktop.org/mailman/listinfo/dri-devel
> > > 
> > > 
> > > --
> > > Ville Syrjälä
> > > Intel OTC
> > 
> > --
> > Ville Syrjälä
> > Intel OTC
> 
> --
> Ville Syrjälä
> Intel OTC

-- 
Ville Syrjälä
Intel OTC
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2015-04-27 12:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-15  8:49 Help on drmModeSetPlane Xie, William
2015-04-15 11:22 ` Ville Syrjälä
2015-04-15 14:24   ` Xie, William
2015-04-15 14:33     ` Ville Syrjälä
2015-04-17  9:30       ` Xie, William
2015-04-17 10:07         ` Ville Syrjälä
2015-04-27  9:37           ` Xie, William
2015-04-27 12:48             ` Ville Syrjälä [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-04-15  8:52 Xie, William
2015-06-04  4:59 ` Xie, William
2015-06-05 17:19   ` Matt Roper
2015-04-15  7:56 Xie, William

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=20150427124809.GD18908@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=william.xie@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 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.