Ok I noticed but I don't care to be credited for that ... I'll leave it to someone else.
I'm no good at writing C code so even if I had the full LK sources I doubt I could be the one to get it to load kernel from uSD ... besides maybe the code is available bundled up in the android build for IFC6410, hidden in gigabytes of various git clones. I gave up because it used up all the monthly download bandwidth my ISP gives me.
Even at that Inforce is still violating GPL because that code in available only if you agree to their NDA.

I even asked Inforce if I could put up an article showing ho you can get Slackware ARM on the IFC6410 (as in doing that I'd be showing how to use their NDA covered stuff, thus violating it) but I got no reply to that question.

Doing what's right doesn't mean you have to know any certain thing. All you have to do is report it and they'll handle the rest. I'm no fan of the GNU license, but letting a company willfully violate the license isn't right.

Any NDA that circumvents the licenses of Free Open Source Software isn't legal, and would never hold up in arbitration.

I give up on the IFC6410:
linaro don't support snapdragon any more,
Inforce sustains that their latest relase (based on closed source kernel derived from 3.4.0) dating back to October 2014 solves issues bit it does not,
it never even went near supporting all the boot device capabilities advertised,
my IFC6410 model went out of production without ever having worked properly (even with the stock ubuntu shipped with it).

The networking issues that afflict in particular wired networking totally defeat preferring the IFC6410 over a RPI2, what can you do with twice the processing power if you can't connect to anything reliably ?
The RPI3 now has integrated wifi while still costing 1/2 the price of the 75$ offer on the IFC6410. I full price the IFC6410 (or the newer IFC6410PLUS) would get you 4 RPI3.

I think I'd be much happier even with 4 RPI2 then withe the IFC6410 and besides that I cant even get a swap with just one RPI2 or RPI3 for the IFC6410 ... that should ring a bell to Inforce to get their act together and get the damn things to work right.

Concerning the networking issues I've come to discover that it's a subtle issue with wired lan:
From work it's working fine 100mbps full duplex ... but at home I've Gb switches and 100mbps router, although every other household device networks fine the IFC6410 manifests serious throughput issues (often grinding to a halt or crash).
I'll try forcing it 100 full duplex to see if at least that gets me reliability (while still defeating reasons for preferring it over a RPI2/3)

Confirmed: forcing the onboard GB la to work at 100MBPS full duplex gets the link reliability.
I suppose some slower connectivity is better then none

Am I the only one experiencing problems with the onboard GB NIT on my IFC6410 ? is it possible that I've a factory defective GB NIC controller ?
Can anyone confirm sustained and reliable GB link operation with the IFC6410 ?

BTW: even with the latest binary blobs firmware from Inforce the on-board wifi is still unusable for any sustained connectivity.
I suppose forcing the link speed to 1/10 of it's capabilities might get that to work too but 54MBPS is already slow enough I'm not going to bother trying.