From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH 0/3] Hisilicon graphic driver
Date: Tue, 10 Nov 2015 11:38:58 +0000 [thread overview]
Message-ID: <5641D752.6060302@ti.com> (raw)
In-Reply-To: <BLU437-SMTP248CA33D65A31EAE12675CC32B0@phx.gbl>
[-- Attachment #1: Type: text/plain, Size: 378 bytes --]
Hi,
On 03/11/15 15:54, Rongrong Zou wrote:
> From: Rongrong Zou <rongrongchau@163.com>
>
> Hi1710 chip have a graphic modue with 2d acceleration, this driver support
> the graphic module.
I'm not merging new fbdev drivers if there are no special reasons for it
(fb for non-MMU platforms is the only reason I know).
Instead, please write a DRM driver.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-11-10 11:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 13:54 [PATCH 0/3] Hisilicon graphic driver Rongrong Zou
2015-11-08 7:55 ` Hanjun Guo
2015-11-08 8:01 ` Hanjun Guo
2015-11-10 11:38 ` Tomi Valkeinen [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=5641D752.6060302@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=linux-fbdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).