delta/syslinux.git/memdisk, branch syslinux-3.85-pre10 git.kernel.org: pub/scm/boot/syslinux/syslinux.git memdisk: make "nopass" type-specific, add "nopassany" 2010-02-08T17:13:11+00:00 H. Peter Anvin hpa@zytor.com 2010-02-08T17:13:11+00:00 48d026fb89dee478f8e3a580b5298594331cc890 Make "nopass" specific to the current drive type. Add new option "nopassany", which also clobbers the drive counts of both types. Signed-off-by: H. Peter Anvin <hpa@zytor.com> 
Make "nopass" specific to the current drive type.  Add new option
"nopassany", which also clobbers the drive counts of both types.

Signed-off-by: H. Peter Anvin <hpa@zytor.com>
memdisk: fix non-prototype function declaration 2010-01-10T20:54:24+00:00 H. Peter Anvin hpa@zytor.com 2010-01-10T20:54:24+00:00 aeace38fa079d56b46898385a926df5356146b1d () is not a prototype, use (void) Signed-off-by: H. Peter Anvin <hpa@zytor.com> 
() is not a prototype, use (void)

Signed-off-by: H. Peter Anvin <hpa@zytor.com>
Makefile: replace -W -Wall with centralized $(GCCWARN) 2010-01-10T20:49:30+00:00 H. Peter Anvin hpa@zytor.com 2010-01-10T20:48:06+00:00 71d20885019564586d5f4d316af220cdae2900f5 Replace -W -Wall hardcoded into a bunch of Makefiles with $(GCCWARN), a centralized variable defined in the root MCONFIG. Add -Wstrict-prototypes to the list of global warnings: we should never have non-prototyped declarations. Signed-off-by: H. Peter Anvin <hpa@zytor.com> 
Replace -W -Wall hardcoded into a bunch of Makefiles with $(GCCWARN),
a centralized variable defined in the root MCONFIG.  Add
-Wstrict-prototypes to the list of global warnings: we should never
have non-prototyped declarations.

Signed-off-by: H. Peter Anvin <hpa@zytor.com>
memdisk: Fix "might be used uninitialized" warning 2009-12-11T18:53:16+00:00 Shao Miller shao.miller@yrdsb.edu.on.ca 2009-12-11T18:53:16+00:00 cd5188bc5c189b6d374ccd4cd5eeba0d9f718ae1 Impact: Initializing variables The checksum_buf function was providing an incorrect checksum on at least one build. 
Impact: Initializing variables

The checksum_buf function was providing an incorrect checksum
on at least one build.
memdisk: Fix mBFT alignment 2009-12-11T18:52:15+00:00 Shao Miller shao.miller@yrdsb.edu.on.ca 2009-12-11T18:52:15+00:00 50e8504edee547ad9c9e8900550ec5c85b77435e Impact: Fixing mBFT alignment It was previously possible that the mBFT might not be 16-byte aligned because the .data section was not. 
Impact: Fixing mBFT alignment

It was previously possible that the mBFT might not be 16-byte
aligned because the .data section was not.
memdisk: slight cleanup of the "safe hook" structure 2009-12-07T23:02:14+00:00 H. Peter Anvin hpa@zytor.com 2009-12-07T23:02:14+00:00 6b588d85fe96f91b90035c897c6f015553e0d213 Make the "safe hook" structure code a bit more readable. Signed-off-by: H. Peter Anvin <hpa@zytor.com> 
Make the "safe hook" structure code a bit more readable.

Signed-off-by: H. Peter Anvin <hpa@zytor.com>
memdisk: "safe hook" and mBFT 2009-12-07T23:00:54+00:00 Shao Miller Shao.Miller@yrdsb.edu.on.ca 2009-12-07T04:03:43+00:00 569a7aa11d6ec9f93fb513fd55287afc785f2d9c Two additions to MEMDISK to support OS drivers. The "safe hook" structure ("Safe Master Boot Record INT 13h Hook Routines") is a means for an OS driver to follow a chain of INT 13h hooks, examining the hooks' vendors and assuming responsibility for hook functionality along the way. For MEMDISK, we guarantee an additional field which holds the physical address for the mBFT. The mBFT is an ACPI table which an OS driver can scan for. The mBFT contains the official MEMDISK Info structure (MDI) which itself includes parameters the OS will want to know about. The mBFT points back at the "safe hook" structure's physical address so that an OS supporting both "safe hook" chain-walking as well as mBFT-scanning can know that both refer to the same MEMDISK instance. Signed-off-by: Shao Miller <shao.miller@yrdsb.edu.on.ca> Signed-off-by: H. Peter Anvin <hpa@zytor.com> 
Two additions to MEMDISK to support OS drivers.

The "safe hook" structure ("Safe Master Boot Record INT 13h Hook Routines")
is a means for an OS driver to follow a chain of INT 13h hooks, examining
the hooks' vendors and assuming responsibility for hook functionality along
the way.  For MEMDISK, we guarantee an additional field which holds the
physical address for the mBFT.

The mBFT is an ACPI table which an OS driver can scan for.  The mBFT
contains the official MEMDISK Info structure (MDI) which itself includes
parameters the OS will want to know about.  The mBFT points back at the
"safe hook" structure's physical address so that an OS supporting both
"safe hook" chain-walking as well as mBFT-scanning can know that both
refer to the same MEMDISK instance.

Signed-off-by: Shao Miller <shao.miller@yrdsb.edu.on.ca>
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
memdisk: pptr->cd_pkt.sect_count is in virtual sectors 2009-11-20T04:17:43+00:00 H. Peter Anvin hpa@zytor.com 2009-11-20T04:17:43+00:00 a0dae108231cdd929aff1f6551fcb70c806c0f99 Per the El Torito spec, pptr->cd_pkt.sect_count are in virtual sectors, i.e. 512-byte sectors. Signed-off-by: H. Peter Anvin <hpa@zytor.com> 
Per the El Torito spec, pptr->cd_pkt.sect_count are in virtual
sectors, i.e. 512-byte sectors.

Signed-off-by: H. Peter Anvin <hpa@zytor.com>
memdisk: Use boot_lba logic for booting an offset within the disk image 2009-11-20T04:15:07+00:00 Shao Miller shao.miller@yrdsb.edu.on.ca 2009-11-20T01:49:34+00:00 dee8f891599f2497e194e086f6603b00291ce033 We have two fundamental quantities: the offset of the disk image itself and the LBA from which we boot. Keep them straight. This should make at least some no-emulation isos work correctly. Signed-off-by: Shao Miller <shao.miller@yrdsb.edu.on.ca> Signed-off-by: H. Peter Anvin <hpa@zytor.com> 
We have two fundamental quantities: the offset of the disk image
itself and the LBA from which we boot.  Keep them straight.  This
should make at least some no-emulation isos work correctly.

Signed-off-by: Shao Miller <shao.miller@yrdsb.edu.on.ca>
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
memdisk: Restore DL for INT 13h, AH=15h, DL=floppy 2009-11-20T01:54:56+00:00 Shao Miller shao.miller@yrdsb.edu.on.ca 2009-11-20T01:20:33+00:00 a59acfdc096be06d1319ee4010eea8abc7b9824e At least PC-DOS requires this to avoid an infinite loop; the DL we restore is not the same DL that we call the underlying BIOS with, but rather the original one (before the decrement.) PC-DOS loops over all the floppies and relies on the call preserving DL in order to advance the loop. Signed-off-by: H. Peter Anvin <hpa@zytor.com> 
At least PC-DOS requires this to avoid an infinite loop; the DL we
restore is not the same DL that we call the underlying BIOS with, but
rather the original one (before the decrement.)  PC-DOS loops over all
the floppies and relies on the call preserving DL in order to advance
the loop.

Signed-off-by: H. Peter Anvin <hpa@zytor.com>