I'm not quite ready to post the next pieces, but thought you might like to see where I've got to:
running XFCE 4.8 here.
I'm not quite ready to post the next pieces, but thought you might like to see where I've got to:
running XFCE 4.8 here.
Not yet 
I'm still working through it myself, trying to document things as I go. Watch out for my blog posts in the RIoTboard area as I walk through the various different steps.
Great work!
I´m really looking forward to your documentation.
Mainly because I didn´t get the mainline Kernel to work by now.
By the way. What Image of Debian did you use?
For that I used one of Robert Nelsons minimal filesystem builds from his wandboard page, then did the update from 7.4 to 7.5 and installed xfce, mostly as a proof of concept and to show that there is light at the end of the tunnel 
I'm running through how to do it myself using debootstrap now in an effort to get less junk and more useful things installed. I'm not very familiar with Debian installs, so it's a bit of trial and error right now.
Daniel Tralamazza wrote:
I meant build_kernel.sh from Robert Nelson's wandboard tutorial (with his armv7 generic kernel).
Ok, I don't use that, and I won't. I respect Robert for a lot of the work he does, but IMHO that's the wrong way to do things.
I have your u-boot fork working, I just need to understand now how u-boot finds the kernel to boot? is it a fixed address? is that what that LOADADDR in the uImage build is for?
Don't use uImage... It's unnecessary and gives you a double problem in recent kernels where you appear to have to specify the load address in several places and then the kernel will ignore it all regardless.
I'm also trying your linux fork, btw the riotboard-dts2 branch has a bug in arch/arm/boot/dts/Makefile line 207 is missing the suffix "imx6s-riotboard.dtb"
Yes it does doesn't it. I was wondering if anyone would notice 
Next steps on kernel build are here http://www.element14.com/community/community/knode/single-board_computers/riotboard/blog/2014/05/04/part-3-building-mainline-linux-kernel-for-riotboard
If you're using my u-boot version, then it simply looks for a file called /bootscript in the root of the first partition on each of J6, J7 & eMMC, loads the content into the environment and runs the environment variable called 'doboot'. The idea is to punt as much of the decisions as possible to the script instead of the hard-coded part inside u-boot.
I'll attached the current /bootscript I'm using here in a minute - I don't seem to have the option in this editor. It loads a zImage not a uImage at 0x12000000 from the same mmc device that /bootscript was loaded from.
It has some issues in that you might have an SD card installed that doesn't have /bootscript, so end up loading the kernel from eMMC, but then by having /dev/mmcblk0p1 hard-coded you'll get your root partition from the SD card. I'll sort that out later - it's why I modified my u-boot build to include the part command.
