From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: "Honza Petrouš" <jpetrous@gmail.com>
Cc: Sebastien LEDUC <sebastien.leduc@st.com>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: mediacontroller for framebuffer
Date: Fri, 22 Jan 2016 18:17:43 +0200 [thread overview]
Message-ID: <145372199.rVcaveV4h8@avalon> (raw)
In-Reply-To: <CAJbz7-3ffWJTD-NH=JWAsUVWKGbuBm7g_OTEZ1R010X5aS_VbQ@mail.gmail.com>
Hi Honza,
On Friday 22 January 2016 08:23:44 Honza Petrouš wrote:
> Hi Laurent
>
> >> I have seen that a long time ago you had done some prototyping work for
> >> exposing framebuffer devices as media entities:
> >> http://www.spinics.net/lists/linux-fbdev/msg04408.html
> >>
> >> What did happen to this prototyping ?
> >> Seems it has never been merged, so could you please explain why ?
> >>
> >> We have some similar needs, so I'd like to understand the right way to go
> >
> > The prototype has been dropped as the framebuffer subsystem got
> > deprecated. Display drivers should now use DRM/KMS.
>
> FB is deprecated? Can you, please, provide some links regarding such talk?
https://lkml.org/lkml/2015/9/24/253
> Sorry for my ignorance, I was never so deep in DRM/KMS (as I treat that
> as big gun for my small embedded systems I was working on) and I'm
> still happy with simple FB support which I get from kernel.
DRM/KMS might be a bit complex for simple display controllers, but helpers
that simplify driver development would certainly be welcome. All it will take
is someone to write them :-)
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2016-01-22 16:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 13:52 mediacontroller for framebuffer Sebastien LEDUC
2016-01-21 22:26 ` Laurent Pinchart
2016-01-22 7:23 ` Honza Petrouš
2016-01-22 16:17 ` 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=145372199.rVcaveV4h8@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=jpetrous@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=sebastien.leduc@st.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.