The kernels I compiled are available at Edited: now at:ftp://ftp.dmik.org/pub/common/buffalo/lspro/duncan_h
There are 4 variants (the tar archives contain uImage and all modules and config files)
(just unpack the tar archive in the / directory, then go to /boot, move uImage.buffalo to (say) uImage.old, and make uImage.buffalo a symbolic link to the new uImage file; see the README-220.127.116.11-lsp_xabi-dh_vx file)
eabi : cross-compiled (2005q3 toolchain) EABI kernel with legacy OABI support.
oabi: natively-compiled OABI kernel (maybe iptables will work with FreeLink using an OABI kernel?, ALSA sound too, maybe; FreeLink is debian-arm which is OABI="old ABI" binary format)
v1: ext3 and xfs file systems have ACL and security label support
v2: ext3 and xfs support is compiled exactly as in the stock buffalo kernels.
the config is based on 1.10 Buffalo Linkstation kernels, with lots of extra modules for usb and serial devices (these can be attached with a usb-to-serial cable), as well as modules for other filesystem types.
For rebuilders, the patch to the buffalo GPL source that updates 18.104.22.168 to 22.214.171.124, and a native arm OABI mkimage executable are also posted. The patch adds squashfs support too.
Thanks to dmik for hosting these while ftp uploads at nas-central are not working.
These LinkStation Live/Pro kernels also work on a Kurobox Pro, but don't support its extra features.
Which format, EABI or OABI to use? With Freelink (debian-arm)there is no advantage (and there are disadvantages) in using an EABI kernel (with OABI legacy support), except that Buffalo kernels are EABI, and may have better-tested ext3 and xfs filesystem support. With a debian-armel distribution (SID, not stable), use EABI kernels.