> I am interested in working on embedded Linux and contribute to the on going > development. I am a new user of Linux. I have gone through lot of web > surfing on the related topics including the LRP. Most of the info is related > from the end user's perspective. I am more interested in knowing how the > things are working behind the scene. i.e systems programming. and back to > the basics of the Linux kernel and its porting. I am working on an > architecture .. a processor that is different from the x86 architecure. Its > mainly targeted for the embedded application, such as routers, firewalls, > high performance, signal processing applications. etc. I guess the Linux > will be the choice as the embedded OS. any kind of help will be highly > appreciated.. I have to start from the basics...
As mentioned, you should subscribe to (and browse the archives of) the leaf-devel list. While it's not particularly easy at the moment to compile all of a LEAF system from source (we've collected lots of bits and pieces from here and there over the years), there's currently work ongoing to migrate to the 2.4 kernel and a newer glibc version. I would very much like to see a clean compile environment allowing a new user/developer to fairly easily compile the entire project from source, and possibly even support for other architectures (kind of depends on how my business life goes...I may have a need to run linux on an embedded PowerPC or ARM chip, in which case I would likely do something based on LEAF, in the process documenting what needs to happen to get running on a non-x86 architecture). NOTE: I currently do *NOT* plan on trying to create or support a cross-compile environment for LEAF...I'm looking at a "psuedo" cross-compile environment similar to what we are currently doing with LEAF. In other words, if you want to compile to an embedded PowerPC 405, you'd host your compile environment on a Mac (or other PPC based system), so you're compiling on the same CPU architecture as your target environment. If you really want a cross-compile environment for linux, and are working on a commercial product, you should really consider purchasing a development environment from one of the many embedded linux providers...especially if your target archetcture is not commonly found in desktop class systems. Otherwise, you'll have a lot of work ahead of you, creating a cross-compile environment and manually configuring packages to compile properly (most of the autoconfigure scripts assume you're compiling on the same system that will eventually run the code they're configuring...lots of manual make-file tweaks & header editing that varies between packages if you're not). Charles Steinkuehler http://lrp.steinkuehler.net http://c0wz.steinkuehler.net (lrp.c0wz.com mirror) _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
