I'm a bit stuck! It seems that patches for a more modern kernel for usi topkick are meant to use a flattened device tree, and while I can get the kernel to compile and load, the u-boot bootm process fails with not recognising the device number (4101).
Marvell>> run bootcmd_sata
Reset IDE:
Marvell Serial ATA Adapter
Integrated Sata device found
[0 0 0]: Enable DMA mode (6)
Device 0 @ 0 0:
Model: Hitachi HTS541010A9E680 Firm: JA0OA480 Ser#: J8300076G17LTD
Type: Hard Disk
Supports 48-bit addressing
Capacity: 953869.7 MB = 931.5 GB (1953525168 x 512)
3089768 bytes read
## Booting image at 00800000 ...
Image Name: Linux-3.7.2
Created: 2013-01-28 23:32:23 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3089704 Bytes = 2.9 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
Error: unrecognized/unsupported machine ID (r1 = 0x00001005).
Available machine support:
ID (hex) NAME
00000690 Marvell DB-88F6281-BP Development Board
00000691 Marvell RD-88F6192-NAS Development Board
00000692 Marvell RD-88F6281 Reference Board
0000078c Marvell 88F6281 GTW GE Board
00000a76 Marvell eSATA SheevaPlug Reference Board
00000831 Marvell SheevaPlug Reference Board
00000a63 Marvell GuruPlug Reference Board
00000bb6 Seagate FreeAgent DockStar
0000085b QNAP TS-119/TS-219
000009c6 QNAP TS-41x
00000b44 Marvell OpenRD Ultimate Board
00000939 Marvell OpenRD Client Board
00000915 Marvell OpenRD Base Board
0000089a LaCie Network Space Max v2
000008a0 LaCie Internet Space v2
00000899 LaCie Network Space v2
0000089b LaCie d2 Network v2
0000089e LaCie 5Big Network v2
0000089c LaCie 2Big Network v2
00000b1e HP t5325 Thin Client
ffffffff Marvell Kirkwood (Flattened Device Tree)
Please check your kernel config and/or bootloader.
Although there were quite a number of Kernel Flattened Device Tree devices specified in the .config file (e.g. the Dreamplug) through 'make menuconfig', none appear as seen above. I can see that the compiled kernel does have the dtsi stuff in it (the system.map), the u-boot doesn't like it. I can see that the u-boot site has catered for FDT in at least the latest version.
OK, fine and I can do something about compiling a new u-boot (2013.01). However the current version is Marvell's 3.4.27 based on the old u-boot 1.1.4. Since I don't think the TP2 has an accessible JTAG port, I am reluctant to try flashing a new u-boot with the likleyhood of it failing and bricking the box.
I think I will give up on TP2's and use something more modern.