Philippe,
These are all good questions. Here at the office we make use of both Freescale's LTIB release and the uClinux-dist release. When Freescale releases a new part and matching evaluation board they will release it with a tool chain (from CodeSourcery) and an LTIB that is aware of the new CPU and Board. Kernel ====== Typically the LTIB released kernels for their MMU-less processors are not the most current and may be several version behind the main Linux tree and Greg's uClinux kernel releases. Given the lag in kernel version those that need to use the most recent CPU's may need to use the older LTIB released kernel as Freescales releases are not in sync with Greg uClinux nor Linus's kernel trees. Once forward porting of the CPU and Board support from LTIB's kernel release to the uClinux and Linux trees, it become easier to make use of the uClinux kernel than the older kernel from LTIB. This is also true of some driver support between kernels as well. User Applications ================= The LTIB released user applications are a collection of public packaged user apps that are well used on MMU-full processors ARM/PowerPC etc. In many cases these applications are full featured (read big) and not always optimized to reduce their size and functionality typically needed for embedded use. While you can modify the source, the LTIB frame work takes a far bit to get up to speed with. If you have the opportunity you can contact your Freescale reps and they can point you to a few online resources (Freescale's Virtual FTF is one) that walk you through how to use LTIB to build and deploy images for their evaluation boards. Where as the uClinux-dist has a collection of applications that have for the most part been reduced in functionality and size to fit better on an embedded device. That said their many be a few applications that may be kernel version and C Library specific in their functionality. This is in part as the uClinux-dist had attempted to allow support to earlier 2.0, 2.4 and 2.6 kernels. Tool Chains and Libraries ========================= The C library and build tools such as uClibc, glibc, GCC, etc are all available in source and can be recompiled to enable and disable features as well as allow you to alter install paths. At the office we have used the Freescale release toolchains on both LTIB and the uClinux-dist wish success. That said we do eventually end up changing the configuration, install path etc to keep the compiler, C library and Kernel in sync. Regards, -- Michael Durrant [email protected] Philippe De Muyter wrote: > Hi all, > > I need to install (uc)linux on a in-house designed MCF5484-based board. > I feel comfortable with uc-linux dist, having used it before on m68340 > and mcf5272 based boards. > > I now saw that the MCF5484 development board from freescale comes with > ltib. > > - What's the relation between uclinux-dist and ltib, if any ? > > - Can I use the compiler provided by ltib to compile uclinux-dist ? > > Thanks in advance ? > > Philippe > _______________________________________________ > uClinux-dev mailing list > [email protected] > http://mailman.uclinux.org/mailman/listinfo/uclinux-dev > This message was resent by [email protected] > To unsubscribe see: > http://mailman.uclinux.org/mailman/options/uclinux-dev > > _______________________________________________ uClinux-dev mailing list [email protected] http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by [email protected] To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
