From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
linux-fbdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
sparclinux@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Bhumika Goyal <bhumirks@gmail.com>
Subject: Re: [PATCH] video: fbdev: remove dead igafb driver
Date: Wed, 18 Oct 2017 13:14:27 +0000 [thread overview]
Message-ID: <62038aaa-7245-25be-a5db-7253eaad5cc3@physik.fu-berlin.de> (raw)
In-Reply-To: <1709588.9HyCXSDUyM@amdc3058>
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.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2017-10-18 13:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20171018125650epcas1p40c181757104f1cb73b1a41596a63b465@epcas1p4.samsung.com>
2017-10-18 12:56 ` [PATCH] video: fbdev: remove dead igafb driver Bartlomiej Zolnierkiewicz
2017-10-18 13:14 ` John Paul Adrian Glaubitz [this message]
2017-10-18 13:22 ` David Miller
2017-10-18 14:45 ` Ondrej Zary
2017-11-09 13:41 ` Bartlomiej Zolnierkiewicz
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=62038aaa-7245-25be-a5db-7253eaad5cc3@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=b.zolnierkie@samsung.com \
--cc=bhumirks@gmail.com \
--cc=davem@davemloft.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).