@Ait, Thanks for jumping the I2c Bus 0 signals from R42/43 on the Rev 2 Model B, and getting the Display to work
The Rev 1 Model B is a little different, as R42/43, and the Camera port is connected to I2c Bus 1!
solutions come to mind, and may be worth trying:
1. With R42/43 connected onto the Display I2c pins, try enabling the camera in raspi-config. This might get the GPU to use I2c Bus 1, and talk to the Display, or,
2. Just try connecting GPIO pins 3 (SDA) and pin 5 (SCL) from the Pi to the Display. On a Rev 1, this is I2c Bus 0.
I have noticed that Gordon Hollingworth's Display Blog talks about hardware and software
mods to get the Display to work with a Model B, as @rpdom pointed out above.
As I understand it, either or both I2c Buses can be controlled by the VideoCore GPU, or the ARM CPU. This is set in the device-tree software. Much of the code controlling both the Display and the Camera seem to run in the GPU, therefor the I2c Bus used to talk to these devices is controlled by the GPU. Due to the difficulty of getting at the 'normal' GPU I2c Bus (soldering onto R42/43, etc.), my fear is that the Foundation's solution will be to control both I2c Buses with the GPU. This would make it easy to connect the Display (jump GPIO pins to the Display), but would mean no I2c for the user. I need an I2c Bus to talk to my Arduino and a Real Time Clock. The Original Poster ( il_diavolo), wishes to use both the PiCamera and the Display on a Rev 2 Model B.
I look forward to seeing the Foundation's solution to getting the Display to work with Revisions 1 & 2 of the old Models A & B.
Thanks to @Ait's conformation that the Display will work by connecting R42/43 to the display, I know now that I can make the Display work with my Model B Rev 2, even if I have to use some of the Model B+ device-tree overlay.