Hardware/Nexus S/MainlineKernelStatus

Introduction

Android drivers are mostly non-standard(for instance their power management is non-standard). And the mainline kernel is standard(it guarantees standard kernel<->userland interfaces).

So running a mainline kenrel or a kenrel derived from mainline is a good idea.

Driver status

Driver	Mainline or in linux-next	problems in android	mainline completness	import possible from android to mainline?	import possible from mainline to android?
Architecture(mach-s5pv210)	Yes, limited?	?	?	?	?
Board(mach-herring.c)	No	?	N/A	Would require a serial cable	N/A
Generic parts of the Sound driver	Yes, sound/soc/samsung	?	lack the board driver, unknown	?	?
Board specific parts of the Sound driver	No	yes, only hw:0 works(no plughw,bad mmap handling etc...)	lack the board driver, unknown	N/A	needs rewrite, android driver is too much hackish
touchscreen driver	Yes,driver/input/touchscreen/atmel_mxt_ts.c	according to morphis it doesn't respect the multitouch protocol(and so it fails to work with xf86-input-mtev: it register a first click but never releases it)	?	?	?
bcm4329(android) and brcm80211(mainline)	Yes	non-standard WEXT	?	N/A	Yes with compat wireless, however it needs some activator
framebuffer (s3cfb)	Yes, however completness unknown	works fine	?	unknown	N/A
Driver	Mainline or in linux-next	problems in android	mainline completness	import possible from android to mainline?	import possible from mainline to android?