Displaying 4 results from an estimated 4 matches for "cur_part".
2010 Jul 24
0
[PATCH] chain.c: allocation fixes
1) At the end of main, there's attempt to free cur_part->record, which
rarely comes from malloc. Only valid case is if gpt handover was performed
and chaining was not successful (cur_part->record is overwritten with gpt
specifc handover record). Freeing the handover area has been adjusted.
2) If our current iterator is ebr, parent wouldn't be...
2010 Aug 08
1
PATCH/RFC chain.c: update iterator code, yank from chain.c, move both to separate directory
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
2010 Jul 26
5
[RFC/PATCH] New chainloading functionality
This patch introduces extra functionality to chain.c, mainly with reference to
BPB adjustments, but not only that. It expects 3 small patches I sent earlier
(they are included for easy reference, patches 1-3/4).
The changes introduced are:
1) file and boot sector use separate options to control load address and jump
address (if applicable). Options are as described below:
*
2010 Jul 20
1
Possible improvements for chain.c
...Patch should be straightforward. A side "bonus" to that would be a
capability to chainload DOSes from drive > 0x80 without a stub. I have
one question though:
if (!opt.loadfile || data[0].base >= 0x7c00 + SECTOR) {
/* Actually read the boot sector */
if (!cur_part) {
data[ndata].data = mbr;
Both freedos/msdos/pcdos option implicitly assume sethidden, but
considering their data[0].base - the condition will always be false (and
rightly so as the kernel overlaps with bootsector), so sethidden will
not work here.
Also, looking at freedos bootse...