search for: aloginov

Greetings, As a Google Summer of Code student for the SYSLINUX project, I had the chance to learn many interesting things from hpa regarding the internals of SYSLINUX. So besides my main task of implementing ELF modules loading & linking, I decided to put down in the wiki all the information I found concerning SYSLINUX development. In this regard, I have created a special category on the

Hello, I was browsing the code for memdisk (I want to adjust it to my hardware) and noticed a couple of things that I am struggling to understand. I would appreciate if someone could clarify the following mysteries to me: 1) _binary_memdisk_bin_start[], _binary_memdisk_bin_end[] and _binary_memdisk_bin_size[]; These variables are declared (as extern const chat in 'setup.c')

Hello, As it is known, Syslinux loads COM32 modules to 0x101000 (the PM IDT is at 0x100000). Unfortunately, in my project this area of memory is already occupied by another program that I need to preserve for a while (specifically, until Syslinux's COM32 module boots up the OS kernel). In other words, I need to load and execute COM32 modules from other than 0x101000 area of memory (for

Hello, I would like to access Memdisk (as a RAM disk) from my application in pure protected mode. "Pure" means that I don't' want to have any switches to real mode even if these switches are automatically handled by Memdisk interrupt stubs. The reason is that my application is running on top of Virtual Machine Monitor (VMM). This virtualization layer is quite simple and

Hello, I am using Syslinux as a bootloader for a PC-based embedded system. I need to load my ELF applications to the top of the available physical memory. By the way, they have no any relations to klibc or Syslinux since they are compiled with a special embedded C-library. Since different PCs may have a different amount of installed RAM, I may need to load those ELF files to different locations.

Hello, I have noticed that Peter wanted to port newlib to syslinux project some time ago. It seems that the porting was not finished. Peter mentioned (http://syslinux.zytor.com/archives/2004-February/003168.html) that sucj job would require a lot of efforts. At the same time newlib is usually regarded as a "highly portable C-library". I am wondering what are the major