From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Paul Mundt <lethal@linux-sh.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [PATCH] fb: epson1355fb: Kill off dead sh support.
Date: Thu, 07 Jun 2007 18:09:26 +0800 [thread overview]
Message-ID: <1181210966.4502.6.camel@daplas> (raw)
In-Reply-To: <20070607095418.GA23002@linux-sh.org>
On Thu, 2007-06-07 at 18:54 +0900, Paul Mundt wrote:
> The SH board that was the only user for this code was removed entirely
> from the kernel quite some time ago, so there's no reason to leave
> the stubs in place. Additionally this driver was completely broken
> anyways, so there's not really a lot of point in fixing it up either.
>
> I can't imagine that this driver gets any testing on ARM either, given
> that FB_BLANK_UNBLANKING doesn't exist, and kills the build regardless
> of which platform is compiling. This fixes that, too.
>
> It wouldn't be a lot of work to finish the platform device conversion
> and go with a generic 8-bit read/write_reg and kill off the architecture
> dependence completely, should someone have any use for this driver.
>
I wonder whether we have users for this driver at all. This hardware is
a pain because it's limited to 16-bit access only.
> Signed-off-by: Paul Mundt <lethal@linux-sh.org>
Acked-by: Antonino Daplas <adaplas@gmail.com>
Tony
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
prev parent reply other threads:[~2007-06-07 10:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-07 9:54 [PATCH] fb: epson1355fb: Kill off dead sh support Paul Mundt
2007-06-07 10:09 ` Antonino A. Daplas [this message]
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=1181210966.4502.6.camel@daplas \
--to=adaplas@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=lethal@linux-sh.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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.