From: Sebastian Frias <sf84@laposte.net>
To: Frans Klaver <fransklaver@gmail.com>
Cc: "Jean-Christophe Plagniol-Villard" <plagnioj@jcrosoft.com>,
"Tomi Valkeinen" <tomi.valkeinen@ti.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: Tue, 29 Dec 2015 16:51:23 +0000 [thread overview]
Message-ID: <5682BA0B.9060001@laposte.net> (raw)
In-Reply-To: <CAH6sp9OvJB+OPDPMWkEyNADcwO19N2=8U-5q49GrCmQTYObb_A@mail.gmail.com>
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.
WARNING: multiple messages have this Message-ID (diff)
From: Sebastian Frias <sf84@laposte.net>
To: Frans Klaver <fransklaver@gmail.com>
Cc: "Jean-Christophe Plagniol-Villard" <plagnioj@jcrosoft.com>,
"Tomi Valkeinen" <tomi.valkeinen@ti.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: Tue, 29 Dec 2015 17:51:23 +0100 [thread overview]
Message-ID: <5682BA0B.9060001@laposte.net> (raw)
In-Reply-To: <CAH6sp9OvJB+OPDPMWkEyNADcwO19N2=8U-5q49GrCmQTYObb_A@mail.gmail.com>
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.
next prev parent reply other threads:[~2015-12-29 16:51 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 [this message]
2015-12-29 16:51 ` Sebastian Frias
2015-12-30 8:06 ` Tomi Valkeinen
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=5682BA0B.9060001@laposte.net \
--to=sf84@laposte.net \
--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=slash.tmp@free.fr \
--cc=tomi.valkeinen@ti.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.