Thanks a lot John and Allen for the help. I understood the difference between the two methods
-Sankar ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Adamson, John Sent: Thursday, October 16, 2008 8:28 PM To: uClinux development list Subject: [uClinux-dev] RE: Kernal patches for MCF5329 Sankar, My opinion (and I'm very new to uClinux) is that you have two choices for uClinux development on the 5329EVB platform: 1) Use the Freescale LTIB (Linux Target Image Builder) iso images available from the Freescale site which include snapshots of the uClinux distribution. As Allen has already said, the LTIB has been updated since the release of the appnote and should contain all the patches referred to in the appnote. If you have a reason to use 2.6.17 and the 2006 LTIB, then the files toward the end of http://forums.freescale.com/freescale/board/message?board.id=CFCOMM&thread.id=4860&view=by_date_ascending&page=2 may help. Or not. 2) Use the uClinux distributions directly. The first option is intended to be easier on the first time user and succeeds in many ways, but at the same time adds a layer of abstraction that must be learned and dealt with when you want to do something beyond the canned demos. You may get more help with the LTIB distributions on the Freescale forums or the LTIB list. The second option (in my opinion) gets you closer to the most recent patches and strips away some of the layers of abstraction, at the price of a slightly steeper learning curve. Each appears to have its own methods for doing things like creating your own rc files or including your applications in the image build. At the moment, I'm using the direct distribution for M5272C3 development (although I did get coerce the 5329 LTIB into building a M5272C3 image) and I use the 5329 LTIB for MCF5329EVB development. It drives me nuts to change back and forth between the two, and I'll probably switch over to the direct distribution for both if I can ever figure out why 5329 USB support seems to be broken (or uses different configuration techniques) after 2.6.17. Michael, in some working environments we are required to have that long disclaimer at the end of our email messages. It has been inserted in our email configuration by the IT folks, and remembering to delete it every time is not only tedious, but hazardous to our continued employment. I suspect that it has little or no legal effect and adds millions of bits to emails every second, but nevertheless there it is, and we can't do a darn thing about it. May I humbly suggest that instead of taking offense where none is intended, that you thank the higher power of your choice (God, Linus, Yourself, etc) that you don't have to work in such an environment? John **************** CAUTION - Disclaimer ***************** This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system. ***INFOSYS******** End of Disclaimer ********INFOSYS***
_______________________________________________ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
