forward porting drivers of s3c-based ebook reader platform

[Heiko Stübner]

[please keep the cc to Alexander, thanks]

Am Mittwoch 05 Januar 2011, 17:07:45 schrieben Sie:
> On Wed, Jan 5, 2011 at 4:06 PM, Heiko Stübner <mmind at debian.org> wrote:
> > 
> > - one would need a sane scheme on how to handle the differences between
> > the submodels. At the moment they use clauses like "if modelX || modelY
> > ... else ... endif" where each respective model is listed
> 
> This could be board dependent or all boards are same?
they seem to differ in small parts. Examples from what I've seen so far:
- some devices have a microphone input whose code is wrapped in ifs
- some expect a "headset_pin_stat" to be true instead of 0

and I didn't dare look at the s3c-keypad-qisda.c closely yet

> > Implementing the power/regulator stuff might be easy (or not) because
> > similar chips seem to be in the kernel i.e. charger bq24022 in kernel
> > vs. bq24075 in the devices. But one would need the knowledge about these
> > things :-) . [Also many tps6502XX regulator drivers are in the mainline
> > kernel but not the specific TPS650240]
> 
> Not experienced in regulator but if similar drivers exist in kernel
> it's just question of passing
> some platform data ;). Do you have some spare devices for testing?
now I'm frightened :-) - what do you mean with "spare".  I have exactly one 
Oyo which I'd like to keep functional.

But we want to try to get people to donate broken devices (i.e. broken screens 
but otherwise intact) which we can distribute to others.