Out of curiosity, I downloaded the firmware upgrade and pulled it apart, let's call it 'firmware teardown time'
It contains a file called firmware.img which is an image of a ext2 filesystem, inside that is a bunch of stuff related to updating the firmware and the actual firmware 'filesystem.img' which is a tarball of the root filesystem. As you may have noticed so far, this thing runs linux. In particular a rather old version:
$ file kernel.img
kernel.img: u-boot legacy uImage, Linux-2.4.20_mvl31-885ads, Linux/PowerPC, Multi-File Image (gzip), 1278107 bytes, Tue Apr 26 23:48:14 2011, Load Address: 0x00000000, Entry Point: 0x00000000, Header CRC: 0xD3039EC6, Data CRC: 0x6FAE0CDF
We also see that it's using a PowerPC CPU rather than an ARM compared to the MDO3000 or so. IIRC the older Tek scopes used power PC as well.
We also find the main app blob, but this one turns to be out rather boring, there's one more interesting bit, the kernel driver for the hardware, named "tek.o".
Some interesting strings from it:
author=Tim Sauerwein, Tektronix, Inc.
ADG420 delay value, ADG420 -- seems to be some frontend thing (
http://www.afc-ingenieros.com/uploads/Afc/Productos/Tektronix/Manuales/Osciloscopios%20TPS2000/TPS2000%20Service%20Manual%20-%20077-0306-00.pdf)
ADC08D1020 delay value -- so it looks like the ADCs are rebadged COTS
With the knowledge of the ADG420 frontend, I took a look at the main app again, close the occurence of ADG420, there's this: BW_18MHZ,BW_20MHZ,BW_23MHZ,BW_26MHZ,BW_39MHZ,BW_45MHZ,BW_51MHZ,BW_61MHZ,BW_60MHZ,BW_73MHZ,BW_89MHZ,BW_122MHZ,BW_200MHZ,BW_240MHZ,BW_260MHZ,BW_NONE
So you should probably look at the two ICs on the frontend board when trying to upgrade the bandwidth.