From: "Richard Purdie" <rpurdie@rpsys.net>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: w100 fb driver
Date: Fri, 19 Nov 2004 16:51:46 -0000 [thread overview]
Message-ID: <021601c4ce58$1111a730$0f01a8c0@max> (raw)
I've been working on creating support for the Sharp SL-C7xx series as part
of a wider effort to create support for the whole Zaurus range of PDAs under
linux 2.6. The C7xx's contain the ATI w100 video chip which doesn't have
mainstream kernel support at present.
Sharp did release a driver against 2.4.18 and I've ported this across to the
2.6 series. I've also made some fairly large changes to the driver to tidy
it up and create support for certain video modes Sharp never enabled.
I'd like to discuss whether it'd be possible to include this driver in a
future kernel? The driver is available at:
http://www.rpsys.net/openzaurus/w100-r1.patch .
I'm aware the corgi_backlight file included above is out of place and it
will be moved into the arch/arm/mach-pxa folder. I'm also aware some fb
changes made in 2.6.10-rc2 need to be applied to this file. Are there any
other problems with the driver as it stands that would prevent its
inclusion, or areas in the driver that it would be advisable to
change/improve?
If the driver would be acceptable, what method of submission is preferred?
(the sourceforge pages seem inactive)
Thanks,
Richard
-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
next reply other threads:[~2004-11-19 16:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-19 16:51 Richard Purdie [this message]
2004-11-19 22:10 ` w100 fb driver Antonino A. Daplas
2004-11-25 15:19 ` Richard Purdie
2004-11-25 19:55 ` Antonino A. Daplas
2004-11-20 9:45 ` Geert Uytterhoeven
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='021601c4ce58$1111a730$0f01a8c0@max' \
--to=rpurdie@rpsys.net \
--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 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).