From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Stuvart S <lovelinuxdeeply@gmail.com>
Cc: linux-renesas-soc@vger.kernel.org
Subject: Re: About Rcar Du
Date: Thu, 19 Jan 2017 20:37:15 +0200 [thread overview]
Message-ID: <2868417.013uUPaKtK@avalon> (raw)
In-Reply-To: <CAAMGra6pVHm7RUth2L2R=Vu3fut4MyPkOgzqwxzM4DWXv81s=Q@mail.gmail.com>
Hellu Stuvart,
On Thursday 19 Jan 2017 23:06:08 Stuvart S wrote:
> Hi Laurent,
>
> Thank you for that information. I am not meaning to capture the
> frames to memory but, I have my own C code snippet to alter image to
> some other forms which reads from a frame buffer ..here I am going to
> do the tapping of image data from DU and modify according to my code
> and write back to same location so that I expect the DU output will
> alter..Actually there should be the image data which is get transfered
> through DU unit to various DU outputs right?
>
> or should I Concentrate on framebuffer?...I Could see a file named
> framebuffer.c in /driver/gpu/drm/ in the stable kernel release which I
> Could not in older versions..I don't know what is the reason of that..
I think you need to learn more about the DRM/KMS API. At this point this isn't
a DU-specific issue, and what you want to do isn't how the display APIs in
Linux operate.
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2017-01-19 18:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAMGra4__ZZWocyP=Yyhgz=8Xb_aDyuEKAn_3+X54Wp0oKwmAQ@mail.gmail.com>
2017-01-19 9:15 ` About Rcar Du Laurent Pinchart
[not found] ` <CAAMGra4bptV2sNXoLPP9xRBmR+OiO=JqmqTfPtiSCiWudLPpoA@mail.gmail.com>
2017-01-19 12:42 ` Laurent Pinchart
2017-01-19 17:36 ` Stuvart S
2017-01-19 18:37 ` Laurent Pinchart [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=2868417.013uUPaKtK@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=lovelinuxdeeply@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.