[patch] w100fb platform independence

[Richard Purdie <rpurdie@rpsys.net>]

The code w100fb was based on was horribly Sharp Zaurus Corgi specific
and there was little I could do about this as I had no access to
anything else with a w100 in it. There is no real documentation about
this chipset available.

Ian Molton has access to other platforms with the w100 (Toshiba
e-series) and so between us, we've been able to improve the w100fb
driver and make it platform independent. Ian Molton has then added
support for the very similar 3220 and w3200 chipsets.

This driver has been extensively tested and is being used in preference
to the original driver in the Zaurus community. I'd therefore like to
update the mainline code to reflect this.

Initially, I'm just posting a link to the patch as one is quite large
(140kb). I've split the patch into two parts - the first for the w100
core changes and the second to add the corgi support code.

http://www.rpsys.net/openzaurus/patches/w100_core-r0.patch
http://www.rpsys.net/openzaurus/patches/w100_corgi-r0.patch

After any comments I'll cc them in full to the list as I submit them.
There is a slight further complication as the corgi patch is dependent
on some changes I've recently submitted to the input people in the corgi
touchscreen driver...

I apologise for the white space changes in the patch. I did try and keep
them separate but the patches became unmanageable. If this is a major
problem, I can try and separate those changes out again...

Richard



-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click