Buffalo NAS-Central Forums

3.8.2007 Kernel 2.6.22 for arm9 boxes ready for test. Unstable

As all the major reported bugs seem to have been resolved (with the exception of XFS), the kernel is now available for the general community to test. Please be advised, this kernel is still a work in progress, and by no means should be used in a work environment until declared stable.

Unlike other projects, the kernel source will no longer be placed in the Development Section of downloads. However, pre-built binaries will only be placed in either svn (will move to git shortly), or in the Development Section until the kernel is stable. Two reasons are given for this: the first is that it is too difficult to build binaries for every revision, as revisions are constantly being made, the second being that we want to discourage unexperienced users from using this kernel. If you know how to build the kernel, you probably are knowledgeable enough to fix problems that might arise. Of course, this policy is subject to change, and the entire community will be encouraged to try the kernels, as the project moves into it's final stable stage.

Note: By using the kernels from svn, users are still subject to the LinkstationWiki BetaTesters ToS and Disclaimer: http://buffalo.nas-central.org/index.php/BetaTesters (Not trying to scare people, just warning newbies).

Bugs ought to be posted in the bugtracker, developmental posts should continue to be posted here.


Standardization Phase

The arm9 kernel is being prepared for standard vanilla submission, however much work is still needed. Developers are encouraged to focus on 2.6.22, unless major bugs arise, in an effort to make the standardization process more efficient. Note, Tzachi from Marvell is preparing the mv88f5182 vanilla support package, and changes in the svn version will reflect those changes as they are made.

The Standardization Process should follow these guidelines:

1) Break apart the Marvell LSP Drivers, and place them in the proper locations.
2) Move board specific defines to a single board header (i.e. linkstation.h or maxtor.h).
3) Drivers ought to be board (not necessarily arch) independent as possible. If the drivers truly will only work for the Marvell board, the drivers should then be marked accordingly in the kconfigs (i.e. depends on config_mv88fxx81).
4) Irrelevant garbage from other Marvell boards ought to be removed. If someone wants to add standard support for another board (i.e. mv881151, let them do it properly).
5) Rewrite Marvell style of driver coding, i.e. MV_ type registers. See the appropriate linux mailing lists for more details.

Extra Details

* The kernel is expected to work on the LSPro/Live, Kurobox Pro, and Terastation Pro, however only the LSPro/Live are known to be fully supported.
* Luca has reported an XFS issue, that must be verified. XFS for Logical Partitions is not yet verified to be bug free. EDIT: This bug is an arm compiler/eabi bug, not a Linkstation/Kurobox specific bug. Please use another filesystem, i.e. JFS instead, until SGI XFS or the Linux Kernel Mailing List is able to resolve the issue. Both mailing lists are aware of the problem.
* The i2c driver, for which the Real Time Clock (RTC) depends on is incomplete. Developers are requested to help finish the driver.
* The Kurobox Pro requires a modified U-Boot environment in order to boot. The stock flash appears to prohibits the booting of newer kernels. Check this thread for updates.
* Kernel is reported to have booted on the Maxtor MSS-II.
* Need verification if kernel works on the TSPv2.

Sources

* Current kernel sources: http://linkstationwiki.svn.sourceforge. ... ux-2.6.22/
* Current configs (make sure to use the right ones): http://linkstationwiki.svn.sourceforge. ... k/configs/

Compilation Instructions

1) Obtain the sources: svn co https://linkstationwiki.svn.sourceforge ... ux-2.6.22/
2) Copy config to the toplevel source directory, and rename to .config.
3) Install either a native or cross toolchain. Cross-compiling with a Codesourcery toolchain is recommended. Change the toplevel Makefile var "CROSS_COMPILE" to equal the full path of your toolchain, i.e.
Code:
CROSS_COMPILE ?=/home/jon/toolchain/arm-2006q3/arm-none-linux-eabi-

4) download mkimage to somewhere in your path:
http://buffalo.nas-central.org/download/LSPro_ ... ns/mkimage
5) Run the following command to make any changes to the config file:

Code:
make menuconfig

6) Run
Code:
make uImage

7) After kernel is finished compiling, find it in /arch/arm/boot/uImage and copy to your /boot directory on the Linkstation/Kuro. Make sure to rename it to uImage.buffalo.
8) Please report in the poll here, if the kernel worked or not.

Contacts

Current developers include lb_worm, lyakh, and myself. Please contact one of us if you're interested in joining the efforts.

Where You Can Help

* We need c coders to help assist in the cleanup of /arch/arm/mach-mv88fxx81 and /include/asm-arm/arch-mv88fxx81
* We need help in creating a Kernel Project Roadmap, including what's been done, and what needs to be done (lyakh's request). Also, a description of buffalo specific drivers, in both the kernel and firmwares is needed.
* We need a volunteer developer to help recode a standard uboot for the LSPro/Live/KuroboxPro/TSPv2. It should be based on LNI's ppc builds, in terms of "EM Mode" setup.

Good Luck, and Regards,

Jon a.k.a. jonli447

original post: viewtopic.php?f=18&t=1548&start=810

_________________
http://www.opifer.net

More testers needed please.

_________________
http://www.opifer.net

Just attached prebuilt kernel along with modules. It is highly advised to compile the kernel yourself, but if you really cannot do this, please test the pre-compiled ones.

_________________
http://www.opifer.net