Like most so called 'help' here, this does not answer the question really.
The current SDK that Freescale puts out, is YOCTO, not LTIB, and so, whatever may be in the LTIB sources, is at least 3-4 years old.
I personally was reluctant to 'sign up' for a Freescale chip, the p1020, in the first place, and the way the 'support' for the WLAN board has gone, it confirmed my suspicions about Freescale.
Having spent the better part of the last 2 weeks getting my 'debian' up to a point were the Yocto based SDK would install and build, I'm pretty irritated about the whole process.
The LTIB package wasn't an easy install, and there were significant differences between LTIB from Freescale, and LTIB activity outside of Freescale. As I recall, some chunks of the Freescale package referred to internal servers which were not accessible by the outside world. It's been a while so memory has faded on the details.
But never fear, Freescale has provided a Yocto environment which is equally obscur for important features of how sources are taken from the original development line, patched with needful items for use with the Freescale ppc processors, and placed in the hierarchy.
To contrast, I've used OpenWRT for my actual deliverables, and have never had the problems with installing, compiling and getting a working kernel+commandline tools up and running.
Heck, I've had better success getting the entire FreeBSD OS compiled completely and working on my P1020-WLAN board than getting 'u-boot' correctly compiled under Yocto.
That's because the expectations of OpenWRT are far more minimalistic, namely a reasonable distribution and host gcc, or in the case of FreeBSD, a FreeBSD host, but there are easy to use installation disks, and once that is done, generating the target system uses a minimal host configuration as well.
