Quote:
Originally Posted by elRicharD
I really want to discover what is wrong. If you happen to build a nice environment to test this please document it the best you can, I will gladly follow and update any documentation you might generate, it would be of great use for the community for sure. Thanks!
|
Slowly but surely working on it. This answers the "what compiler" question (/bin/umount in KT-5.1.0 image):
Code:
bin $ objdump -sx umount
. . . .
Contents of section .comment:
0000 4743433a 20284c69 6e61726f 20474343 GCC: (Linaro GCC
0010 20342e35 2d323031 312e3035 2d302920 4.5-2011.05-0)
0020 342e352e 34203230 31313035 30352028 4.5.4 20110505 (
0030 70726572 656c6561 73652900 4743433a prerelease).GCC:
0040 20285562 756e7475 2f4c696e 61726f20 (Ubuntu/Linaro
0050 342e342e 342d3134 7562756e 74753129 4.4.4-14ubuntu1)
0060 20342e34 2e352032 30313030 39303920 4.4.5 20100909
0070 28707265 72656c65 61736529 00 (prerelease).
. . . .
And it is built agains the Kernel Headers version 2.6.16 not against the 2.6.31-rt kernel version that is running the KT.
(This is not an 'error' - __Linux__ maintains backwards compatibility - regardless of what lab126 likes to do to the e-ink drivers).