On 01/10/2015 02:11 PM, Dr. H. Nikolaus Schaller wrote:
Hi, I have seen there has been a recent discussion on IRC:
<aTc> yeah, im compiling a kernel <aTc> and it failed <aTc> what a surprise
why did you expect that?
since the last few kernels had the same problem.
what do you mean with “reliable”?
That it "just works".
Another problem is that your kernel seems very unstable. (for 3.18.0, and 3.19-rc3 as well) Most obvious problems were random segfaults when using xorg (almost immediately), and make when compiling a kernel (takes a while to show up there, but when resuming the compile everything works fine) Using the exact same version (and using the same compiler) of the other kernel, and everything was rock solid.
It also isn't very clear which kernel is the one that's supposed to be used,and in what state it is. So I prefer to use one that's at least a bit "known good" than one where someone else is in the middle of fixing/adding things.
<aTc> which is what i use
So in summary, please give me a favour and ask me (e.g. by private mail or by inviting me to IRC or here on this list) before you spread FUD and question my reputation or the reliability of my work in public. Especially as it was quite some work to get it to the state where it already is.
I do have to keep up my grumpy reputation on irc, so i tend to make things sound a lot worse than they really are, which most people there are well aware of. Out of context it sounds a lot ruder than it was meant :) And it was mostly just a bit of background ranting while messing about with the stuff. Trying to dig up the source of the problem takes a lot more time and effort than quickly writing "blah, this doesn't work" on irc.
Compiling should go the following:
checkout 3.19-rc3 use gta04_defconfig copy omap5-pyra*.dtb on the boot partition copy modules to the rootfs partition
You can even beta-test a very new tool:
http://projects.goldelico.com/p/gta04-makesd/
run ./makesd pyra -k http://url-for-your/uImage -d http://url-for-your/device-tree.tbz
Handling different panels connected to the EVM it is a little tricky. There is a panelselect script in GTA04/root which can be installed on the Pyra rootfs and allows to overwrite the default omap5-pyra.dtb by a panel specific variant.
This allows to select a different panel, power off, connect the different panel and reboot. This will of course not become the long-term standard for a complete Pyra device but is very helpful in the current phase of HW development.
Which one do you recommend for using with the plain devboard with hdmi output. omap5-uevm seemed to work best, fb0 doesn't show up when using omap5-pyra
Do you use any special kernel cmdline ?
In summary I would prefer to get help for the gta04-kernel to be tested and stabilized instead of complaining that it is not good and others are much better.
I'm not that great with kernels, and certainly not at devicetrees, where , unfortunately, most of the major problems seem to come from.
BR, Nikolaus
PS: I have tested eSATA and it works for me (as a secondary drive besides the uSD). I do not yet know if we can boot from eSATA.
Works fine, but does need "SCSI disk support" and "TI PIPE3 PHY Driver " compiled in, instead of the module your config is currently set to.