Differences between revisions 5 and 6
Revision 5 as of 2009-01-09 17:32:00
Size: 2361
Editor: sconklin
Revision 6 as of 2009-01-09 17:33:05
Size: 2361
Editor: sconklin
Deletions are marked like this. Additions are marked like this.
Line 33: Line 33:
|| Adding drivers || probably in kernel, may not want all of them || need to be added to LUM ||
Line 36: Line 37:
|| Adding drivers || probably in kernel, may not want all of them || need to be added to LUM ||

Management of LPIA Kernel Trees


DISTRO == standard Ubuntu distribution

MID == Mobile Internet Device

The Current Situation

LPIA kernel trees are being maintained in multiple git repositories.


The Hardy MID LPIA tree is located here: git://kernel.ubuntu.com/mid-team/hardy-netbook.git

The Hardy DISTRO tree is here: git://kernel.ubuntu.com/ubuntu/ubuntu-hardy.git

MID deliverables are currently all based off of the Hardy release

Note: Netbooks are LPIA but not MIDs ??

Do we need a third column in this table? DISTRO, NETBOOK, MID

These trees have the following differences:

Hardy LPIA kernel differences




High Mem support

No HM support

Requires HM support

ALSA patches

Hardy baseline

Has backports from later kernels

frequency of releases

seldom | sometimes multiple times per day

Adding drivers

probably in kernel, may not want all of them

need to be added to LUM

Menlow/Non Menlow support



ALSA as a LUM module


must build both in-kernel DRM and PSB DRM module, select at boot time

Statements that I can't resolve into the above framework:

config (Netbooks are LPIA arch but not MIDS)

  • This means enabling HIGHMEM, SECURITY, and other support that is

not in the default LPIA kernel.

Desired Outcome

We would like to bring all the kernels into one repository. The purposes are:

  1. to improve maintainability by making security and other patches easily available to all
  2. to bring the fast-moving development for mid devices into the distro

Which flavours are required

Should we maintain separate flavours for netbook and other builds with different requriements? Is proliferation of flavours a problem?

How branches are managed

With everything in one tree, we can branch as needed to meet the frequent release requirements for netbooks, and pull all branches back into the main distro branch when convenient.

Application to other releases and archs

Whatever is decided should be applicable to moving MID/netbook builds to Jaunty, and also apply to the ARM arch, as we will soon have a number or ARM variants to deal with.

KernelTeam/LpiaTrees (last edited 2009-01-09 17:33:05 by sconklin)