loading packages...
resolving dependencies...
looking for inter-conflicts...
:: linux-kirkwood-dt and linux-kirkwood are in conflict (linux). Remove linux-kirkwood? [y/N] y
:: linux-headers-kirkwood-dt and linux-headers-kirkwood are in conflict (kernel26-headers). Remove linux-headers-kirkwood? [y/N] y
Targets (5): linux-headers-kirkwood-3.6.1-0 [removal]
linux-kirkwood-3.6.1-0 [removal] uboot-env-2009.11-4
linux-headers-kirkwood-dt-next.20121011-0
linux-kirkwood-dt-next.20121011-0
Total Download Size: 0.01 MiB
Total Installed Size: 19.57 MiB
Net Upgrade Size: 0.24 MiB
Proceed with installation? [Y/n] y
:: Retrieving packages from alarm...
uboot-env-2009.11-4-arm 7.3 KiB 198K/s 00:00 [######################] 100%
(1/3) checking package integrity [######################] 100%
(1/3) loading package files [######################] 100%
(3/3) checking for file conflicts [######################] 100%
(5/5) checking available disk space [######################] 100%
(1/2) removing linux-kirkwood [######################] 100%
(2/2) removing linux-headers-kirkwood [######################] 100%
(1/3) installing uboot-env [######################] 100%
>>> To print u-boot env please use fw_printenv
>> Configuration file located at /etc/fw_env.config
(2/3) installing linux-kirkwood-dt [######################] 100%
>>> Updating module dependencies. Please wait ...
**********************************************************************
WARNING! This kernel package will NOT boot without user intervention.
A Kirkwood Flattened Device Tree supporting zImage is
placed in /boot and all mainline supported .dtb and .dts
files are in /boot/dtb for you to prep as appropriate.
Depending on your particular device, you may need to upgrade
your installed U-Boot version, and/or modify your boot env.
Some platforms may need to append the appropriate .dtb to the
end of the zImage and make a uImage from the resulting blob.
You may need to update the .dts with your kernel boot args
and compile your own .dtb from it, /usr/local/sbin/dtc has
been included to assist in this.
If you are not familiar with the care and feeding of a DT
enabled kernel for your device, uninstall this package and
continue to use linux or linux-kirkwood for now.
**********************************************************************
Optional dependencies for linux-kirkwood-dt
crda: to set the correct wireless channels of your country
(3/3) installing linux-headers-kirkwood-dt [######################] 100%
[root@alarm linux-kirkwood-dt]# cd /boot/
[root@alarm boot]# ls
dtb uImage-dt zImage
[root@alarm boot]# cd dtb
[root@alarm dtb]# ls
kirkwood-dns320.dtb kirkwood-goflexnet.dts kirkwood-lsxhl.dtb
kirkwood-dns320.dts kirkwood-ib62x0.dtb kirkwood-lsxhl.dts
kirkwood-dns325.dtb kirkwood-ib62x0.dts kirkwood-lsxl.dtsi
kirkwood-dns325.dts kirkwood-iconnect.dtb kirkwood-ts219-6281.dtb
kirkwood-dnskw.dtsi kirkwood-iconnect.dts kirkwood-ts219-6281.dts
kirkwood-dockstar.dtb kirkwood-iomega_ix2_200.dtb kirkwood-ts219-6282.dtb
kirkwood-dockstar.dts kirkwood-iomega_ix2_200.dts kirkwood-ts219-6282.dts
kirkwood-dreamplug.dtb kirkwood-km_kirkwood.dtb kirkwood-ts219.dtsi
kirkwood-dreamplug.dts kirkwood-km_kirkwood.dts skeleton.dtsi
kirkwood.dtsi kirkwood-lschlv2.dtb
kirkwood-goflexnet.dtb kirkwood-lschlv2.dts
[root@alarm dtb]# cd ..
[root@alarm boot]# cp zImage zImage-GoFlexNet
[root@alarm boot]# cat dtb/kirkwood-goflexnet.dtb >> zImage-GoFlexNet
[root@alarm boot]# mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-next -d zImage-GoFlexNet uImage
Image Name: Linux-next
Created: Thu Oct 11 16:19:34 2012
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3147183 Bytes = 3073.42 kB = 3.00 MB
Load Address: 0x00008000
Entry Point: 0x00008000
[root@alarm boot]# reboot')
A few tense seconds later...
$this->bbcode_second_pass_code('', '[root@alarm ~]# uname -a
Linux alarm 3.6.0-0-next-20121011-ARCH+ #1 PREEMPT Thu Oct 11 14:46:02 EDT 2012 armv5tel GNU/Linux')
So far the only tweak to my box is I had to add an entry for / to my /etc/fstab as it wasn't getting automounted rw like it does with earlier kernels?
I'll be posting this to the ALARM github shortly, once I clean up a couple more things in the build and determine why we normally go through great pains to avoid doing a 'make headers-install' and instead manually copy things into place... things that move with every kernel release making it a PITA to keep the headers package working...
---===UPDATED v3.9-rc2===---
This kernel package currently supports:
- Dreamplug
Guruplug
D-Link DNS-320 & DNS-325
Iomega I-Connect & StorCenter ix2-200
Seagate GoFlex Net & Dockstar
QNAP TS-110, TS-119, TS-119P+, TS-210, TS-219, TS-219P, TS-219P+, TS-419
Buffalo Linkstation LS-XHL & LS-CHLv2
Keymile Kirkwood Reference Design
RaidSonic IB-NAS6210, IB-NAS6220
LaCie Network Space [Max, Lite, Mini, Vanilla] v2 NAS & Internet Space v2 NAS
MPL CEC4
Plat'Home OpenBlocks A6
USI Topkick
ZyXEL NSA-310
As you can see from my install walk through, it is not a simple matter of installing and forgetting. Installing just places the building blocks in place, as well as removing your old, safe copy of uImage. (You'll want to backup a copy of that before playing.) You need to determine if your version of uBoot supports loading DT zImages and .dtb blobs directly, or if you need to use a legacy uImage like my GoFlex Net. I don't suggest contemplating this if you don't have a working serial console and an interest in potentially bricking your device. If you don't know how your plug actually boots, this kernel package is not for you.
This kernel package includes a DT compiler should you need to include kernel boot arguments directly as well.
This kernel does not have AUFS3 support which is present in linux-kirkwood.
You do gain a few things however, besides being on the bleeding edge of kernel development...
- Updated AES and SHA1 ASM routines in kernel for those skipping cryptodev support
Improved use of GCC optimizations particularly when dealing with kernel structs that may or may not be properly aligned
I'll update once I push this upstream.
