From: Stefan Monnier <monnier-CRDzTM1onBSWkKpYnGOUKg@public.gmane.org>
To: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-media-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [linux-sunxi] Cedrus driver
Date: Thu, 16 Nov 2017 08:11:29 -0500 [thread overview]
Message-ID: <jwvd14imks9.fsf-monnier+gmane.comp.hardware.netbook.arm.sunxi@gnu.org> (raw)
In-Reply-To: 20171116110204.poakahqjz4sj7pmu@flea
>> Where can I find a list of TODOs to get it ready to be merged?
> Assuming that the request API is in, we'd need to:
> - Finish the MPEG4 support
> - Work on more useful codecs (H264 comes to my mind)
> - Implement the DRM planes support for the custom frame format
> - Implement the DRM planes support for scaling
> - Test it on more SoCs
Are all these really needed before it can be merged?
Stefan
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-11-16 13:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 12:59 [PATCH 1/1] add mali r6p2 dt node Giulio Benetti
2017-11-07 13:02 ` Maxime Ripard
[not found] ` <1510059543-7064-1-git-send-email-giulio.benetti-W14uJ/fiAyBY2hyreNRi6g@public.gmane.org>
2017-11-16 10:13 ` Cedrus driver Giulio Benetti
[not found] ` <6fcdc0d9-d0f8-785a-bb00-b1b41c684e59@imkreisrum.de>
[not found] ` <6fcdc0d9-d0f8-785a-bb00-b1b41c684e59-IaPFKHZio8oZId6A0yLOdQ@public.gmane.org>
2017-11-16 10:37 ` Giulio Benetti
[not found] ` <693e8786-af83-9d77-0fd4-50fa1f6a135f-W14uJ/fiAyBY2hyreNRi6g@public.gmane.org>
2017-11-16 11:02 ` [linux-sunxi] " Maxime Ripard
2017-11-16 13:11 ` Stefan Monnier [this message]
2017-11-16 19:59 ` Nicolas Dufresne
[not found] ` <1510862395.8053.39.camel-dDhyB4GVkw9AFePFGvp55w@public.gmane.org>
2017-11-17 8:01 ` Maxime Ripard
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=jwvd14imks9.fsf-monnier+gmane.comp.hardware.netbook.arm.sunxi@gnu.org \
--to=monnier-crdztm1onbswkkpyngoukg@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-media-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
/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