All right! So I should have heeded Texy's council on the v4 TFT setup:

It is recommended to use the latest raspbian image dated 2015-02-16, to configure using an SSH session remotely, with no TV/Monitor connected to the HDMI port, and to connect the 2.8" Display board right from the start prior to connecting power to the Pi.

If I don't hook up to the HDMI port, everything works great and Kodi now shows on the TFT! Now I can try to figure out how to get this to work even when HDMI is hooked up. Thanks,

Sorry for the delayed response. At first I thought notro doesn't support your device with his framebuffer driver (see here). Then I noticed his note that the list is not complete and that his source should be referenced. It looks like his last submission added support for a Waveshare TFT, not sure if it is the V4 though.

Keep in mind that there are 2 ways to load your driver, using the device (modprobe) and using the device overlay. If your TFT uses the fb_ili9340 driver, you may be able to modprobe the adafruit22a device with the correct parameters since the Adafruit 2.2 TFT uses the same driver as yours. If you want to make it work with with the device tree, it appears you will need to manually add the correct overlay as I don't think it is included in the kernel (my pi is not hooked up so I can't verify). A few promising links:

This will break some functionality, such as the OSMC splash screen, WiFi driver support. If someone submits a PR to OSMC's GitHub repository I will accept this driver in to our kernel, then you will not need to rpi-update.

Definitely a good idea. We call our own init (not /sbin/init) via a kernel patch and we have a few other patches. While WiFi is still working, you are using in-tree drivers, and we prefer out of tree with some of our patches to improve performance and stability.

If you're happy with upstream kernel that's great, but as I say we're keen (and see no reason not) to support this and it should make things easier for other users as a result.