I'm trying to figure out how /dev/sam/gfx0 and /dev/sam/gfx3d0 is working..
I thought we could create a thread here where we share our "interersing addresses" in the files. (Regarding everything)
What i'm currently looking at is 009426C4 (T-CHU7DEUC 3000.G, exeDSP), here it seems to open the gfx0 device, maybe we can find a way to communicate to the device from this.
.text:009426BC LDR R0, =aDevSamGfx0 ; "/dev/sam/gfx0"
.text:009426C0 LDR R1, =0x1002 ; oflag
.text:009426C4 BL open
Found something else really interesting. Here it creates alot of Chelsea controller objects for everything cool, everything form teletext to video processors
.text:006C9FFC ; TDBuilder::Build(void)
.text:006C9FFC EXPORT _ZN9TDBuilder5BuildEv
.text:006C9FFC _ZN9TDBuilder5BuildEv ; CODE XREF: CFastBoot::Initialize(void)+24p
interesting thing is that US A650,A750 like models and few others (that from 2008) has samsung.ko full implemented. that kernel could do all lower things including 2d, 3d, scaling, jpeg, x264 decoding, however samsung it seems dropped that way in later in 2009 tv and moved almost everthing into exeDSP. so no way implement custom app on kernel driver using /dev/sam/*.
In current samsung.ko there is some left over audio codecs stuff including dts support.
RE how hardware tv works will be very difficult due complexity.