[patch][orion] Update Orion platform to kernel 2.6.35

[maddes]

Got Linux 2.6.35 running on my Linksys WRT350N v2.
Also tried kernel 2.6.36 which unfortunately doesn't boot, so it's only 2.6.35 for now.

There's one big issue left:
Not all packages are build, e.g. all USB packages, although they are selected (319 packages vs. 453 for 2.6.34).
This has to be solved either in the build system or in the platform config.

The kernel grew so much in size, that it doesn't fit into the 1MB mtd partition when compiled with symbols.
Therefore I extended the kernel mtd partition by 128KB (biggest JFFS2 block).
This is very useful when people need readable output on a kernel oops.
Without symbols the kernel still fits into 1MB.

The change consists of two patches:

1. Update Orion platform to 2.6.35
2. Backport of generic 014 patch from kernel 2.6.36 (added 1.4 AMD/Fujitsu CFI version)

Comments:

• CONFIG_CMDLINE_FORCE=y can replace 010 platform patch, but I kept it for now.
• Image makefile and patches can easily be set to new kernel mtd sizes by changing a single line.

[maddes]

-p0 patch for trunk to backport generic 014 patch from kernel 2.6.36 to 2.6.35

[maddes]

It turned out that the package "kmod-pppol2tp" doesn't compile with 2.6.35 on any platform, so this problem got its own ticket #8195.
Therefore upgrading the Orion platform to 2.6.35 is good to go.

A working build of subtarget "generic" is available at:
​ftp://ftp.maddes.net/openwrt/trunk/orion/build_23912/

sysupgrade, firstboot and reboots worked well.

[Nilfred <nilfred@…>]

See r23571 "2.6.36 should be the next target"

[anonymous]

Yes, that's right. But 2.6.36 currently doesn't boot on Linksys WRT350N v2.
That's why Orion should be first upgraded to 2.6.35, which already includes necessary changes for 2.6.36.
After this got to trunk, I would add preliminary 2.6.36 support for Orion to get it to work soon.

[maddes]

I got some comments about the mtd partition size increase.
It should be better to leave the kernel mtd size at 0x0010000 for current trunk inside the image file.
This way more space is available in official builds.
If more space is needed, then a developer can still increase it by only changing three lines in total.
The comment in the makefile should be updated accordingly.

[maddes]

-p0 patch for trunk to allow flexible kernel mtd sizes for Orion

[maddes]

-p0 patch for trunk to update Orion to kernel 2.6.35

[maddes]

While talking to acoul and some others I got the correct solution for the different kernel mtd sizes: an extra config setting accessible via make menuconfig which defaults to 1024KB.
This allows to increase the mtd size for special cases or even allows to decrease it for a totally stripped down kernel.

The old patch for Orion 2.6.35 got removed from the ticket and new patches are attached, therefore the update now consists of three parts:

1. Add support for flexible kernel mtd sizes
2. Update Orion platform to 2.6.35 (change to platform patch 010 also needed for 2.6.36)
3. Backport of generic 014 patch from kernel 2.6.36 (add AMD/Fujitsu CFI version 1.4)

[kaloz]

NAK. The next kernel Orion will get updated to is 2.6.36. As long as that doesn't work, it stays where it is.

[maddes]

I see that you got 2.6.36 working. Great. Thanks a lot.

What about the support for kernel mtd size via make menuconfig?
(trunk_orion_flexible_kernel_mtd_support.patch)

[kaloz]

I hate even like the idea of it ;)