intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Sean Paul <sean@poorly.run>, Dave Airlie <airlied@gmail.com>,
	Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: dri-devel@lists.freedesktop.org,
	Gerd Hoffmann <kraxel@redhat.com>,
	Sam Ravnborg <sam@ravnborg.org>,
	dim-tools@lists.freedesktop.org,
	Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>,
	Steven Price <steven.price@arm.com>,
	Robert Chiras <robert.chiras@nxp.com>,
	Jean-Jacques Hiblot <jjhiblot@ti.com>,
	Lowry Li <Lowry.Li@arm.com>, Jonas Karlman <jonas@kwiboo.se>,
	intel-gfx@lists.freedesktop.org,
	Maxime Ripard <mripard@kernel.org>,
	Ezequiel Garcia <ezequiel@collabora.com>,
	Wen He <wen.he_1@nxp.com>, Simon Ser <contact@emersion.fr>,
	Oleg Vasilev <omrigann@gmail.com>, Qiang Yu <yuq825@gmail.com>,
	Thomas Zimmermann <tzimmermann@suse.de>
Subject: Re: [PULL] drm-misc-next
Date: Fri, 18 Oct 2019 16:45:27 +0300	[thread overview]
Message-ID: <febda9e7-d62b-128c-819a-71c57d9c001d@ti.com> (raw)
In-Reply-To: <20191017192601.GA215957@art_vandelay>

Hi Sean,

On 17/10/2019 22:26, Sean Paul wrote:

> concern for those. The omap OMAP_BO_MEM_* changes though I don't think have
> really reached non-TI eyes. There's no link in the commit message to a UAPI
> implementation and the only reference I could find is libkmsxx which can set
> them through the python bindings. Since this is TI-specific gunk in TI-specific
> headers I'm inclined to let it pass, but I would have liked to have this
> conversation upfront. I figured I'd call this out so you have final say.

There was some discussion about that a few years back when I initially 
sent the patches, but now that I look, the discussion died before really 
even starting.

This is what I said about userspace implementation:

> Yes, unfortunately that is not going to happen. I don't see how this
> could be used in a generic system like Weston or X. It's meant for very
> specific use cases, where you know exactly the requirements of your
> application and the capabilities of the whole system, and optimize based
> on that.
I know this feature is used by customers, but I don't have access to 
their applications.

  Tomi

-- 
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-10-18 13:45 UTC|newest]

Thread overview: 148+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-17 19:26 [PULL] drm-misc-next Sean Paul
2019-10-18 13:45 ` Tomi Valkeinen [this message]
2019-10-18 20:11   ` Sean Paul
2019-10-21  8:09     ` Tomi Valkeinen
2019-10-21 15:48       ` Sean Paul
2019-10-22  2:17         ` [Intel-gfx] " Dave Airlie
2019-10-22  7:01           ` Daniel Vetter
  -- strict thread matches above, loose matches on Subject: below --
2024-04-25 14:39 Maarten Lankhorst
2024-04-19 12:04 Maarten Lankhorst
2024-04-10 14:59 Maarten Lankhorst
2024-04-05 12:36 Maarten Lankhorst
2024-03-28 11:22 Maarten Lankhorst
2024-03-21 13:56 Maarten Lankhorst
2024-02-29  8:48 Thomas Zimmermann
2024-02-22 13:58 Thomas Zimmermann
2024-02-26  9:41 ` Daniel Vetter
2024-02-15 13:26 Thomas Zimmermann
2024-02-09 16:32 Thomas Zimmermann
2024-01-11 15:49 Thomas Zimmermann
2023-12-14  9:34 Maxime Ripard
2019-10-31 19:30 Sean Paul
2019-10-24 15:55 Sean Paul
2019-10-09 15:08 Sean Paul
2019-08-23  8:35 Maxime Ripard
2019-08-19 14:19 Maxime Ripard
2019-08-16 11:32 Maxime Ripard
2019-08-16 11:47 ` Chris Wilson
2019-08-19 14:19   ` Maxime Ripard
2019-08-08 12:14 Maxime Ripard
2019-08-03 10:47 Maxime Ripard
2019-08-06  0:33 ` Dave Airlie
2019-08-06  7:34   ` Daniel Vetter
2019-08-06  9:40     ` Emil Velikov
2019-08-06  9:49       ` Daniel Vetter
2019-08-06  9:54         ` Emil Velikov
2019-08-06  9:58           ` Daniel Vetter
2019-08-06 10:12             ` Daniel Stone
2019-08-06 10:27               ` Emil Velikov
2019-08-06 10:48                 ` Jani Nikula
2019-08-06  9:55         ` Daniel Vetter
2019-08-06 14:25     ` Rob Herring
2019-08-06 14:55       ` Daniel Vetter
2019-08-06 16:01   ` Maxime Ripard
2019-08-06 16:11     ` Daniel Vetter
2019-08-07 12:02       ` Maxime Ripard
2019-08-07 12:30         ` Daniel Vetter
2019-08-08 15:29           ` Maxime Ripard
2019-06-20 15:42 Maarten Lankhorst
2019-06-14  8:57 Maarten Lankhorst
2019-06-14  9:35 ` Daniel Vetter
2019-06-05  9:17 Maarten Lankhorst
2019-05-23 15:47 Maarten Lankhorst
2019-05-23 15:53 ` Sean Paul
2019-05-23 15:55   ` Daniel Vetter
2019-05-23 15:55     ` Daniel Vetter
2019-04-18  9:05 Maarten Lankhorst
2019-04-10 19:49 Sean Paul
2019-04-04 20:10 Sean Paul
2019-03-28 15:33 Sean Paul
2019-03-28 16:03 ` Daniel Vetter
2019-03-21 17:08 Sean Paul
2019-03-25 10:37 ` Daniel Vetter
     [not found] <20190211095220.3oeodszr2dgxrwqq@flea>
2019-02-14 13:07 ` Daniel Vetter
2019-02-01 14:47 Maxime Ripard
2019-01-23 11:03 Maxime Ripard
2019-01-16 20:04 Maxime Ripard
2019-01-15 10:56 Maxime Ripard
2019-01-16  9:36 ` Daniel Vetter
2019-01-07 18:03 Maxime Ripard
2018-12-06  9:44 Maarten Lankhorst
2018-11-28  9:36 Maarten Lankhorst
2018-11-21 10:44 Maarten Lankhorst
2018-11-08 16:05 Maarten Lankhorst
2018-11-07 11:58 Maarten Lankhorst
2018-11-07 20:18 ` Daniel Vetter
2018-11-07 20:29   ` Sean Paul
2018-11-07 20:31     ` Daniel Vetter
2018-11-07 20:48       ` Sean Paul
2018-11-08  7:56         ` Christian König
2018-11-08  8:05           ` Daniel Vetter
2018-11-08  8:37         ` Maarten Lankhorst
2018-09-27  9:39 Sean Paul
2018-09-19 20:03 Sean Paul
2018-09-13 13:02 Sean Paul
2018-09-05 20:22 Sean Paul
2018-07-18 20:08 Gustavo Padovan
2018-07-12  1:11 Gustavo Padovan
2018-07-04 23:46 Gustavo Padovan
2018-06-28  1:00 Gustavo Padovan
2018-06-21 10:54 Gustavo Padovan
2018-06-21  0:58 Gustavo Padovan
2018-06-21 10:01 ` Christian König
2018-05-15  8:17 Maarten Lankhorst
2018-05-11  7:43 Maarten Lankhorst
2018-05-11 20:25 ` Eric Anholt
2018-05-04  9:54 Maarten Lankhorst
2018-04-26 10:53 Maarten Lankhorst
2018-06-06  3:37 ` Dave Airlie
2018-06-06  7:49   ` Maarten Lankhorst
2018-03-21 14:49 Sean Paul
2018-03-09 18:04 Sean Paul
2018-02-28 20:34 Sean Paul
2018-03-02 21:22 ` Sean Paul
2018-03-05  8:10   ` Daniel Vetter
2018-03-05 23:20     ` Sean Paul
2018-03-06  6:42       ` Daniel Vetter
2018-03-06 19:01         ` Sean Paul
2018-03-06 19:07           ` Ville Syrjälä
2018-03-06 19:20             ` Sean Paul
2018-03-07  8:19               ` Daniel Vetter
2018-02-21 20:36 Sean Paul
2018-01-08 13:45 Gustavo Padovan
2017-12-21 17:04 Gustavo Padovan
2017-12-14 17:46 Gustavo Padovan
2017-12-07 11:06 Gustavo Padovan
2017-10-20 13:39 Daniel Vetter
2017-10-16  9:35 Daniel Vetter
2017-10-12 12:05 Daniel Vetter
2017-10-13 14:08 ` Maarten Lankhorst
2017-10-13 14:24   ` Benjamin Gaignard
2017-10-05  5:36 Daniel Vetter
2017-09-20 17:33 Daniel Vetter
2017-09-20 18:42 ` Daniel Vetter
2017-08-18 17:00 Sean Paul
2017-08-16 20:42 Sean Paul
2017-08-08 19:50 Sean Paul
2017-07-18 18:42 Sean Paul
2017-07-18 18:49 ` Sean Paul
2017-06-15 20:52 Sean Paul
2017-06-02 20:55 Sean Paul
2017-05-26 20:58 Sean Paul
2017-05-29  6:57 ` Daniel Vetter
2017-05-16 14:55 Sean Paul
2017-03-31 15:23 Sean Paul
2017-03-21  9:06 Daniel Vetter
2017-03-20 15:30 Daniel Vetter
2017-03-21  7:23 ` Daniel Vetter
2017-03-12 12:57 Daniel Vetter
2017-03-06  9:54 Daniel Vetter
2017-01-30  8:58 Daniel Vetter
2017-01-23  7:35 Daniel Vetter
2017-01-09 19:15 Daniel Vetter
2016-12-30 10:35 Daniel Vetter
2016-12-08 10:16 Daniel Vetter
2016-11-29 10:13 Daniel Vetter
2016-11-29 11:17 ` Daniel Vetter
2016-11-29 21:01   ` Stephen Rothwell
2016-11-16 17:11 Daniel Vetter

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=febda9e7-d62b-128c-819a-71c57d9c001d@ti.com \
    --to=tomi.valkeinen@ti.com \
    --cc=Lowry.Li@arm.com \
    --cc=Rodrigo.Siqueira@amd.com \
    --cc=airlied@gmail.com \
    --cc=contact@emersion.fr \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dim-tools@lists.freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=ezequiel@collabora.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jjhiblot@ti.com \
    --cc=jonas@kwiboo.se \
    --cc=kraxel@redhat.com \
    --cc=mripard@kernel.org \
    --cc=omrigann@gmail.com \
    --cc=robert.chiras@nxp.com \
    --cc=sam@ravnborg.org \
    --cc=sean@poorly.run \
    --cc=steven.price@arm.com \
    --cc=tzimmermann@suse.de \
    --cc=wen.he_1@nxp.com \
    --cc=yuq825@gmail.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;
as well as URLs for NNTP newsgroup(s).