Re: [PATCH 0/2] staging/android fixes

[Pavel Machek]

Hi!

> > Here is a patch to fix build for android specifics drivers.
> >
> > What we should do next to prevent them from being removed in 2.6.23 ?
> >
> > Is there any chance that all android stuff would be merged one day ?
> > Actually, we got a working 2.6.32 kernel for android here (with wakelock, ashm, etc..):
> > http://git.iksaif.net/?p=android-x86/kernel;a=shortlog;h=refs/heads/android-x86-backport
> 
> Arve's done a few revisions of the wakelock code with the linux-pm
> list, and I know he's planning on trying to work through the remaining
> issues (as I recall there was some discussion on read/write vs ioctl
> interfaces to userspace) in the near future.
> 
> This really is the one piece that has the most impact on everything
> else -- maintaining versions of the various platform hardware drivers
> with and without wakelock support is messy.

It is really not that bad. Yes, it touches most drivers, but it is few
lines per driver and easy to remove.

Waiting for wakelocks (1year plus, AFAICT) before merging hw drivers
seems like very slow way forward.
								Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/