Re: [Prex-devel] Anyone still around?
Status: Beta
Brought to you by:
kohtani
From: Eli H. <eh...@ve...> - 2015-01-03 17:50:44
|
Hello Richard, It is good to hear that someone is still interested in Prex. I'm also wanting to use Prex for embedded projects using a micro kernel architecture similar to Minix. I will take a look at ELCC. I am still working on the layers above and considering if I can use LLVM to provide a base for a language like Erlang/Elixir that will run on atop a bare metal type of kernel as you described, possibly Prex or a heavily modified Minix kernel (if it comes to it). Keep on exploring and let's keep the channel open for mor dialogues. Eli > On Jan 3, 2015, at 02:51, Richard Pennington <ri...@pe...> wrote: > > Hi, > > I know this list was been quiet for some time, but I thought that there > might still be some interest is some Prex related work that I've been doing. > I have been developing a cross compilation tool chain based on > clang/LLVM for ARM, Mips, PowerPC, and x86 processors. I call the > project ELLCC (pronounced "elk") http://ellcc.org > The project currently fully supports C and C++ compilation for all the > target processors running Linux. I also want to support bare metal > development on all the targets, so I started a sub-project called ELK > ("Embedded Little Kernel") for that purpose. The goal of ELK is to use > the same C/C++ run-time libraries (using the BSD or BSD-like licensed > libc++, musl, and compiler-rt) for both the Linux and ELK environments > and it has been coming along very well. > About a month and a half ago I decided I wanted to add file system > support to ELK and after some googling I stumbled across Prex. I was > very impressed by the design and clarity of the code, so I decided to > borrow some of it for my ELK project. I won't go into too much detail > here, but here's what I've done so far: > * Incorporated the Prex file system, console/tty and VM code (both MMU > and non-MMU). > * Cleaned up a few minor design issues (e.g. vnode locks can be read > only or R/W, no schedule_lock(), finer grained locking) > This week I added networking support by incorporating the LwIP TCP/IP > stack. (It currently can only communicate on 127.0.0.1 because I haven't > added Ethernet drivers yet.) > > The current incarnation of ELK only runs on ARM. I'd like to add the > glue for the other targets soon as time allows. > > Just thought you'd like to know that Prex lives on. > > -Rich > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming! The Go Parallel Website, > sponsored by Intel and developed in partnership with Slashdot Media, is your > hub for all things parallel software development, from weekly thought > leadership blogs to news, videos, case studies, tutorials and more. Take a > look and join the conversation now. http://goparallel.sourceforge.net > _______________________________________________ > Prex-devel mailing list > Pre...@li... > https://lists.sourceforge.net/lists/listinfo/prex-devel |