From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Sebastian Frias <sf84@laposte.net>, Frans Klaver <fransklaver@gmail.com>
Cc: "Jean-Christophe Plagniol-Villard" <plagnioj@jcrosoft.com>,
linux-fbdev@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
mason <slash.tmp@free.fr>, "Måns Rullgård" <mans@mansr.com>
Subject: Re: [RFC PATCH] fbdev: add support for Sigma Designs' smp8xxxfb.ko
Date: Wed, 30 Dec 2015 08:06:36 +0000 [thread overview]
Message-ID: <5683908C.5040001@ti.com> (raw)
In-Reply-To: <5682BA0B.9060001@laposte.net>
[-- Attachment #1: Type: text/plain, Size: 977 bytes --]
Hi,
On 29/12/15 18:51, Sebastian Frias wrote:
> On 12/29/2015 03:16 PM, Frans Klaver wrote:
>> On Tue, Dec 29, 2015 at 3:06 PM, Sebastian Frias <sf84@laposte.net>
>> wrote:
>>> Right now we don't know if the driver will be upstreamed.
>>> Let me rephrase my question:
>>>
>>> - how would you recommend enabling FB_CFB_FILLRECT, FB_CFB_COPYAREA and
>>> FB_CFB_IMAGEBLIT for a driver that is not included in the kernel's tree?
>>>
>>> If that is not possible, I guess we will have to keep a forked tree
>>> until
>>> the driver is upstreamed, but we would like to avoid that, hence the
>>> question.
>>
>> I guess you'll have to keep on doing that indeed. I'm not aware of any
>> location where out-of-tree drivers are considered. You should try
>> again when you have some actual code to upstream.
>>
>
> Ok, thanks.
Also note that I don't want new fbdev drivers into the mainline kernel.
You should implement a DRM based driver instead.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Sebastian Frias <sf84@laposte.net>, Frans Klaver <fransklaver@gmail.com>
Cc: "Jean-Christophe Plagniol-Villard" <plagnioj@jcrosoft.com>,
linux-fbdev@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
mason <slash.tmp@free.fr>, "Måns Rullgård" <mans@mansr.com>
Subject: Re: [RFC PATCH] fbdev: add support for Sigma Designs' smp8xxxfb.ko
Date: Wed, 30 Dec 2015 10:06:36 +0200 [thread overview]
Message-ID: <5683908C.5040001@ti.com> (raw)
In-Reply-To: <5682BA0B.9060001@laposte.net>
[-- Attachment #1: Type: text/plain, Size: 977 bytes --]
Hi,
On 29/12/15 18:51, Sebastian Frias wrote:
> On 12/29/2015 03:16 PM, Frans Klaver wrote:
>> On Tue, Dec 29, 2015 at 3:06 PM, Sebastian Frias <sf84@laposte.net>
>> wrote:
>>> Right now we don't know if the driver will be upstreamed.
>>> Let me rephrase my question:
>>>
>>> - how would you recommend enabling FB_CFB_FILLRECT, FB_CFB_COPYAREA and
>>> FB_CFB_IMAGEBLIT for a driver that is not included in the kernel's tree?
>>>
>>> If that is not possible, I guess we will have to keep a forked tree
>>> until
>>> the driver is upstreamed, but we would like to avoid that, hence the
>>> question.
>>
>> I guess you'll have to keep on doing that indeed. I'm not aware of any
>> location where out-of-tree drivers are considered. You should try
>> again when you have some actual code to upstream.
>>
>
> Ok, thanks.
Also note that I don't want new fbdev drivers into the mainline kernel.
You should implement a DRM based driver instead.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-12-30 8:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-29 13:15 [RFC PATCH] fbdev: add support for Sigma Designs' smp8xxxfb.ko Sebastian Frias
2015-12-29 13:15 ` Sebastian Frias
2015-12-29 13:49 ` Frans Klaver
2015-12-29 13:49 ` Frans Klaver
2015-12-29 14:06 ` Sebastian Frias
2015-12-29 14:06 ` Sebastian Frias
2015-12-29 14:16 ` Frans Klaver
2015-12-29 14:16 ` Frans Klaver
2015-12-29 16:51 ` Sebastian Frias
2015-12-29 16:51 ` Sebastian Frias
2015-12-30 8:06 ` Tomi Valkeinen [this message]
2015-12-30 8:06 ` Tomi Valkeinen
2015-12-30 9:31 ` Sebastian Frias
2015-12-30 9:31 ` Sebastian Frias
2015-12-30 10:32 ` Tomi Valkeinen
2015-12-30 10:32 ` Tomi Valkeinen
2015-12-30 10:32 ` Tomi Valkeinen
2016-01-04 7:08 ` Daniel Vetter
2016-01-04 7:08 ` Daniel Vetter
2016-01-04 7:08 ` Daniel Vetter
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=5683908C.5040001@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=fransklaver@gmail.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mans@mansr.com \
--cc=plagnioj@jcrosoft.com \
--cc=sf84@laposte.net \
--cc=slash.tmp@free.fr \
/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.