search for: load_base

...t_area = NULL, *file_area = NULL; + struct part_entry *hand_area = NULL; + struct syslinux_rm_regs regs; char *drivename, *partition; int hd, drive, whichpart = 0; /* MBR by default */ @@ -1523,6 +1531,7 @@ int main(int argc, char *argv[]) goto bail; } data[ndata].base = load_base; + file_area = (void *)data[ndata].data; load_base = 0x7c00; /* If we also load a boot sector */ /* Create boot info table: needed when you want to chainload @@ -1701,7 +1710,9 @@ int main(int argc, char *argv[]) } else if (!(data[ndata].data = read_sectors(cur_part->lba_data, 1))) {...

...loaded. To retain compatibility with older configs simple invocation such as seg=0x60 is perfectly valid. Only potential incompatibilities here, is if someone used decimal values (e.g. seg=96) or if someone used seg= to actually control boot sector address/jump (extremely unlikely). Old logic of load_base used first for file, then for sector is no longer present. 2) Overlapping regions are checked very carefully. File takes precedence over boot sector, and boot sector over handover area - see the patch, near boot sector loading and handover area creation. 3) bsnomap option allows reading/adjusting...

1) code split and move Iterator related functionality is yanked from chain.c and moved to iterator.{c,h}. Both are moved to com32/chain and this way chain.c is ready for further splitting. Alternatively, partiter could be moved to com32/lib at any time in the future. It's potentially useful for other modules (e.g. if someone wanted to code partition dumper or editor). 2) Iterator updates

From: Matt Fleming <matt.fleming at linux.intel.com> This series fixes some bugs and switches the elflink branch to be entirely ELF modules. It applies on top of, http://syslinux.zytor.com/archives/2011-April/016369.html The deletions in the diff stat below are mainly from deleting com32/elflink/modules (finally!). Now there should be no duplicate code because we don't need COM32 and