I searched for this here and on Google but I found no results for it. So in digging for information about new Advance Format 4K drives and using them in TiVos I was digging into the TiVo Linux kernel information. http://www.tivo.com/linux/ We have a S1, S2, S3, & S4 so I know what software versions to expect. Well I noticed version 16 available on the TiVo Linux page so I opened it up and started prodding. This is Linux kernel 2.6.31, I'm not exactly sure yet what the version 14 runs as it's not as apparent in the code as this version 16. One of the biggest changes I'm seeing is all of the Broadcom 740x CPU code has been removed which is the CPU in the S3 devices. Also the Gen06D device data has been removed as well (S3 as well). The Gen07 code is untouched but now there's a Gen07C & Gen07P set of folders that are mostly empty. Lots of updates to the base kernel code for SATA, PCI, CPU handlers, USB, 2D video, etc type of stuff you expect to see in new kernels. Digging into the TiVo specific stuff there's some references to GraphicsSurfacePoolSize for all the existing Gen07 devices I see across multiple other code sections. Seems to be a 60MB region of the 512mb now being set aside for specific graphics reasons. Then in those TiVo config files is more references to the Gen07C & Gen07P which their real names are Gen07C-Gimbal & Gen07P-Picasso which deeper in their info shows they have "/* Second bmem region: Cable Modem */" so I'm betting these are the TiVo Premiere Q & it's streaming box. I'm betting the Gimbal is the Q because it has more memory allocated to the Cable portion than the Picasso. The Gimbal name for the Q makes sense too as a gimbal is "a pivoted support that allows the rotation of an object about a single axis (WikiPedia)" in essence it's the point everything else is based on where Picasso, duh, is a painter showing what he sees (non-tuner TiVo). It's nice to see some good movement forward on the kernel level at least. Of note the line in the kernel denoting the 2nd CPU is disabled on boot is gone now too. I had stumbled on it in the old code but now I can't find it again, but I'll keep hunting.