search for: klausm

Hi guys, I just looked over liu's code as of today, and it looks pretty good; obviously you have gotten a huge amount of work done already! However, in the short term, we will most likely not have memory management -- malloc/free -- available in the core (making that possible is part of KlausM's project, but I want to decouple those.) The code currently uses malloc() in disklab.c, which is used from cache.c. The solution there is pretty simple: add a pointer to get getoneblk() prototype for a target buffer, then use a chunk of .bss memory for the cache. As previously discussed, we...

...me aspects of the 3.8x branch.) However, it is now available for people to try out. It is checked into the fsc branch ("filesystems in C") of the main repository. Liu: you probably want to pull this into your tree before doing any further work. This snapshot doesn't include any of KlausM's work on porting the UI to C and switching to ELF dynamic modules. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.

It looks like I managed to screw up the push to the "elflink" branch I did yesterday night. I have fixed it now, and there is a current "elflink" branch which should contain KlausM's work as of last night. Sorry about that, -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.

Just a status update on my progress with ROSH: I now have it able to compile as a COM32 and Linux ELF on the pathbased branch. The main reason I am using the Linux ELF is to test and compile a little easier and faster. At this point, it's approaching a stable, usable state. However, it depends on some changes to libutil, the main COM32 library, and the Syslinux core. I think I have the