From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753924AbdJRN3H (ORCPT ); Wed, 18 Oct 2017 09:29:07 -0400 Received: from shards.monkeyblade.net ([184.105.139.130]:33154 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752657AbdJRNW0 (ORCPT ); Wed, 18 Oct 2017 09:22:26 -0400 Date: Wed, 18 Oct 2017 14:22:14 +0100 (WEST) Message-Id: <20171018.142214.436255812332803507.davem@davemloft.net> To: glaubitz@physik.fu-berlin.de Cc: b.zolnierkie@samsung.com, linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, sparclinux@vger.kernel.org, bhumirks@gmail.com Subject: Re: [PATCH] video: fbdev: remove dead igafb driver From: David Miller In-Reply-To: <62038aaa-7245-25be-a5db-7253eaad5cc3@physik.fu-berlin.de> References: <1709588.9HyCXSDUyM@amdc3058> <62038aaa-7245-25be-a5db-7253eaad5cc3@physik.fu-berlin.de> X-Mailer: Mew version 6.7 on Emacs 25.3 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Wed, 18 Oct 2017 06:22:22 -0700 (PDT) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: John Paul Adrian Glaubitz Date: Wed, 18 Oct 2017 15:14:27 +0200 > Hi Bartlomiej! > > On 10/18/2017 02:56 PM, Bartlomiej Zolnierkiewicz wrote: >> igafb driver hasn't compiled since at least kernel v2.6.34 as >> commit 6016a363f6b5 ("of: unify phandle name in struct device_node") >> missed updating igafb.c to use dp->phandle instead of dp->node. > Would it take a lot of work to port the driver to the new interface? > > I'm not sure which SPARC machines use this particular framebuffer, but > my plans are to fix up all these old framebuffer drivers. I have > already > received several Amiga (Zorro) graphics cards for testing the updated > drivers on Amiga. > > It could be that I actually have this particular SPARC framebuffer in > my hardware collection. Unless you have a 32-bit sparc laptop, you don't have a machine that will use this driver.