N800

Overview

This page is about adding Nokia N800/N810 support to Linux mainline kernels. N800/N810 (from now on called just n8x0) has been in linux-omap tree far too long, we need to get it finally to mainline. There has been discussions on the linux-omap mailing list about this:

• Re: N810: latest linux-omap-2.6.git master
• OMAP support in mainline?
• Re: Things to do after 2.6.29 gets released

All the information about n8x0 mainline inclusion is scattered and the purpose of this page is to collect them into one place. As this is a wiki, it's encouraged for the people to improve the page based on their knowledge.

Patches

Current patches are available from:

http://www.valot.fi/kalle/n8x0/patches/

The patches are against latest Linus' tree. This is to make merge to the mainline as easy as possible.

The compilation instructions:

make ARCH=arm CROSS_COMPILE=arm-linux- n8x0_defconfig
make ARCH=arm CROSS_COMPILE=arm-linux-
flasher -k arch/arm/boot/zImage -f -b

The patches have been, at least, tested with Sourcery G++ Lite 2008q3-66.

Communication

All discussion should happen at <linux-omap@vger.kernel.org> (subscription instructions). Kalle Valo <kalle.valo@iki.fi> coordinates all this, so you might want to contact him in case there's something private you want to discuss and CC on all n8x0 related patches. The public communication in the mailing list is the preferred method.

The Plan

This a a draft and very much work in progress!

Most of the drivers needed by n8x0 should be already in mainline, notably exception being the Nokia's proprietary cbus support. But this must be checked.

1. platform data support for omap serial driver
2. n8x0 board file
   1. serial port
   2. onenand
   3. display
   4. touchscreen
   5. keyboard
   6. wlan
   7. usb
3. cbus
   • should be converted to use spi framework and send to inclusion for mainline
4. retu
   • should use new cbus driver
5. tahvo
   • should use new cbus driver

User space interfaces

Diablo user space components use non-standard kernel interfaces and most likely the interfaces are not acceptable to mainline. If we want to get diablo running with latest mainline kernels, this needs to be solved somehow. (Do we really want that or instead focus, for example, on Mer?)

Identified non-standard interfaces:

• watchdog interface used by dsme
• bme interface
• private Wireless Extension calls used by wlancond/eapd
• audio and DSP in general
• maybe also display control

In theory it might be possible to implement an out-of-tree module or separate patchset which