From: Hyungwon Hwang <human.hwang@samsung.com>
To: Pekka Paalanen <ppaalanen@gmail.com>
Cc: Emil Velikov <emil.l.velikov@gmail.com>,
ML dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 3/6] xf86drmMode: Make atomic request structures visible
Date: Fri, 21 Aug 2015 16:35:56 +0900 [thread overview]
Message-ID: <20150821163556.31514e9b@samsung.com> (raw)
In-Reply-To: <20150821094442.7ebc6b39@gmail.com>
Dear,
On Fri, 21 Aug 2015 09:44:42 +0300
Pekka Paalanen <ppaalanen@gmail.com> wrote:
> On Fri, 21 Aug 2015 15:06:58 +0900
> Hyungwon Hwang <human.hwang@samsung.com> wrote:
>
> > Hi Emil,
> >
> > On Thu, 20 Aug 2015 17:23:09 +0100
> > Emil Velikov <emil.l.velikov@gmail.com> wrote:
> >
> > > On 19 August 2015 at 01:58, Hyungwon Hwang
> > > <human.hwang@samsung.com> wrote:
> > > > This patch makes 'struct _drmModeAtomicReqItem' and 'struct
> > > > _drmModeAtomicReq' visible from outside. This is needed for
> > > > userspace applications to use those structures when calling
> > > > drmModeAtomicCommit().
>
> Yeah, this sounds like a very bad idea.
Yes. Making it visible was not good. But then I think that new API for
getting the value of a request item in the request which are not
applied to the kernel. Because for preparing the buffer, the userspace
program needs width and height which are in the request.
The program can get the value before making it as a request. In that
case, the program such as modetest, which does not understand what the
object id or propery id means, have to be modified to understand them
for extracting the needed value.
How do you think about it? Is modetest just a special program for
testing, and is this support not needed for another real program?
>
>
> Thanks,
> pq
>
> > > >
> > > Hmmm what is missing in the current API, that one needs direct
> > > access to the structs ? If we expose these to the user we'll be
> > > putting a (ABI) hedgehog down our pants (i.e. it might be ok, but
> > > will likely result in a very painful experience).
> >
> > I also agree with you. I think I should drop this patch, and find
> > another way for modetest.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-08-21 7:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 0:58 [PATCH 1/6] xf86drmMode: remove the trailing white spaces Hyungwon Hwang
2015-08-19 0:58 ` [PATCH 2/6] xf86drmMode: separate drmModeAtomicCommit() and drmModeAtomicCleanup() Hyungwon Hwang
2015-08-20 16:17 ` Emil Velikov
2015-08-21 4:54 ` Hyungwon Hwang
2015-08-21 6:42 ` Pekka Paalanen
2015-08-21 7:18 ` Hyungwon Hwang
2015-08-21 10:08 ` Pekka Paalanen
2015-08-19 0:58 ` [PATCH 3/6] xf86drmMode: Make atomic request structures visible Hyungwon Hwang
2015-08-20 16:23 ` Emil Velikov
2015-08-21 6:06 ` Hyungwon Hwang
2015-08-21 6:44 ` Pekka Paalanen
2015-08-21 7:35 ` Hyungwon Hwang [this message]
2015-08-19 0:58 ` [PATCH 4/6] modetest: remove the trailing white spaces Hyungwon Hwang
2015-08-19 0:58 ` [PATCH 5/6] modetest: add atomic modeset support Hyungwon Hwang
2015-08-19 0:58 ` [PATCH 6/6] modetest: add atomic page flip support Hyungwon Hwang
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=20150821163556.31514e9b@samsung.com \
--to=human.hwang@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.l.velikov@gmail.com \
--cc=ppaalanen@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 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.