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@xxxxxxxxxxx> >> 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:
signature.asc
Description: OpenPGP digital signature
