Received: by 10.192.165.148 with SMTP id m20csp4164497imm; Mon, 30 Apr 2018 13:01:06 -0700 (PDT) X-Google-Smtp-Source: AB8JxZqZIfG9mF+Y9zp2fJnXYqQZVnLvW6IJaaxDxNOSoR3lBSu3Y38EdBx8qyL9hW6MwW1VJ+nK X-Received: by 2002:a63:25c4:: with SMTP id l187-v6mr11065104pgl.221.1525118466586; Mon, 30 Apr 2018 13:01:06 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525118466; cv=none; d=google.com; s=arc-20160816; b=aHFTmbZuppO8Ox3MygEWn4AQZPMKwVxB2Y4ZiXf1gQthujD0x8/Sgy9dAItxl+KCJ3 UrhkXZhUiYHNLMCSSY8qSr/pWC/ywHgdzKlAT7fKduV2yvcFb+QDgzwvrrDFUf/Puys+ pokHCu13FkLyBWGhf4lpaHGMJRU1KNEjuKDVo9/LgBtLFRxl7/KlFKnQox72TFPSLXbI 7bkHO480c2liERx4EQL28Ml+65vJXqPjRydz7mx+MNyOmDhuQj519qCvErFzO/GFJ+pK fAgm4mJ//dw9BvAP7EDD3cStJbtEd1kriRKb8i9dGzYqCtC3QZ5AC7R52PUrjzFBExBn mHjw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=OyBvv2EfLcoQyROK1wouX7ERcGT13249RGty5kbRRSM=; b=X7F8V3kKwcxdJVQYBa5vlB6F/X2pvNfxNaR517YZIjCaLjkvIcKmegBH36+kddOHWH gLe3npzo6lKIIwzX1QWpNpljfSekDkOaTsmuTDr42E3IsBVJyuMeIEsQANsp5D11i/h1 BQalo+dU6VMCPmhCfJEEE1N7vWKrefQgs+qD+ury62ylyao3Kf8QCuCxGOvo9zKisTIB 8fIgBVAVl6KmqqcrLgu5qZF8+MLw74T+6eM9H9e3tXcHxw8JPJ79kFQHw+riiLpdTygk jAI5vusQX73atWh+p4Pp6o2aef/JsA0trbzNcI/5l5FAr1kkvvxAXq1SGjSrWQG3btjg peAA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f35-v6si7845826plh.193.2018.04.30.13.00.52; Mon, 30 Apr 2018 13:01:06 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756182AbeD3T7h (ORCPT + 99 others); Mon, 30 Apr 2018 15:59:37 -0400 Received: from emh01.mail.saunalahti.fi ([62.142.5.107]:57134 "EHLO emh01.mail.saunalahti.fi" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756061AbeD3T7f (ORCPT ); Mon, 30 Apr 2018 15:59:35 -0400 Received: from t60.musicnaut.iki.fi (85-76-162-39-nat.elisa-mobile.fi [85.76.162.39]) by emh01.mail.saunalahti.fi (Postfix) with ESMTP id 0F7BC20052; Mon, 30 Apr 2018 22:59:31 +0300 (EEST) Date: Mon, 30 Apr 2018 22:59:31 +0300 From: Aaro Koskinen To: Tomi Valkeinen , Bartlomiej Zolnierkiewicz Cc: Laurent Pinchart , linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org, linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org, Tony Lindgren Subject: Re: [PATCH] video: fbdev: omap2: remove rfbi Message-ID: <20180430195931.GC2456@t60.musicnaut.iki.fi> References: <2238944.jilJcacc6d@amdc3058> <20180427174714.bdvvlljk3txwu2bo@darkstar.musicnaut.iki.fi> <2055912.iuafLNK0IC@amdc3058> <20180427181243.o7ro63l6z7yatey7@darkstar.musicnaut.iki.fi> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On Mon, Apr 30, 2018 at 10:06:11AM +0300, Tomi Valkeinen wrote: > On 27/04/18 21:12, Aaro Koskinen wrote: > >> You should be targeting omapdrm driver instead, fbdev subsystem is closed > >> for the new hardware support. > > > > AFAIK, based on N950 display support discussion, it's impossible to get > > anything new into omapdrm for a long time. And based on Tomi's comments, > > restoring RFBI support with omapfb should be a minor thing. > > I was perhaps a bit vague, but I didn't say it should be a minor thing. > I meant that there should be no architectural obstacles in omapfb, and I > think all the generic plumbing to enable N800 display is there in omapfb. > > That said, it still needs a real amount of work with the rfbi driver, > the encoder driver and the panel driver on N800 (the encoder and the > panel driver are not in mainline anymore). Let's see first if I get anything working. After that we can evaluate the impact properly once we see the actual patches needed. A.