| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
A bunch of glibc header files were bogusly included. We should not
depend on having a 32-bit glibc installed, since we don't use it.
|
|
|
|
| |
Simple test program which simply invokes syslinux_local_boot().
|
|
|
|
|
| |
A memory-dumping utility which runs in real mode. Thus, it can be
used to get memory dumps from a relatively pristine system.
|
|
|
|
| |
Document menu system memory overwrite fix
|
|
|
|
|
|
| |
Add the "nopass" option to completely remove the system drives. This
is a pretty big hammer and is largely for debugging at this stage; it
probably needs more polishing before it can be made official.
|
|
|
|
|
|
| |
Fix memory overwrite bug, specifically, the use of BP after it might
have gotten clobbered. Since at the point of use, BP is supposed to
be == SP, we can just add "mov bp,sp".
|
|
|
|
|
| |
There is at least one set of CD-ROM BIOSes out there which corrupt FS
on INT 13h, so save and restore all segment registers around INT 13h.
|
|
|
|
| |
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Hello all,
I ran across a couple bugs in memdisk concerning hd images the other
day. With the attached patch I've been able to successfully boot a
32MB gzipped hd image. (I'll put the image up for a short while at
ftp://ftp.io.com/pub/usr/duanev/fdoshd.img.gz)
The pxelinux.cfg entry I'm using is:
label fdos
kernel memdisk
append keeppxe initrd=fdoshd.img.gz
syslinux/memdisk is great, thanks Peter et. al.!
--
Duane Voth
duanev@io.com
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
|
|
|
|
|
|
|
| |
More needs to be done; the code has console I/O at the library level,
which isn't good.
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch
- add a new pci_dev_info structure :
It contains additional informations about the pci devices like
the product/vendor name and the associated linux kernel module
- add a get_name_from_pci_ids() function in pci/scan.c
This function reads a pci.ids file from the boot device.
Then it assign for each pci device, its vendor/product name.
You just have to put this file in the root directory of your
isolinux/pxelinux (i.e the root directory of your tfptboot server
if you are using pxelinux).
- add a get_module_name_from_pci_ids() function in pci/scan.c
This function reads a modules.pcimap file from the boot device.
Then it assign for each pci_device its linux kernel module.
You just have to put this file in the root directory of your
isolinux/pxelinux (i.e the root directory of your tfptboot server
if you are using pxelinux).
- Add a call to get_name_from_pci_ids() into the pcitest COM32 module
- Add a call to get_module_name_from_pci_ids() into the pcitest COM32 module
- Fixing typedef struct { ... } s_pci...; by struct pci... {};
- Improving comments
- Fixing the memory allocation to prevent leaks
With this patch, pcitest.c32 act like lspci plus a bonus by displaying
the linux kernel module assiocated to each pci device.
Signed-off-by:Erwan Velu <erwan.velu@free.fr>
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
|
| |
|
|
|
|
| |
A very simple module to reboot the machine.
|
|
|
|
| |
The address for the farcall thunk was inadvertently clobbered in entry.S.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
When we don't have any registers to pass, it's convenient to be able
to share a common all-zero structure.
|
|
|
|
| |
Yet another byte bites the dust...
|
|
|
|
|
| |
Shave off another byte by using the not-frequently-used jmpw *%sp
instruction!
|
|
|
|
| |
Comments are good...
|
|
|
|
|
| |
Use the "return address points to data" trick to shave a few bytes off
the generation of error messages.
|
|
|
|
|
|
|
|
| |
In case we hit the death loop, put HLT in it. It's probably superfluous,
but it can't hurt, and we can always take it out to reclaim the space.
Arguable the death loop is superfluous at all, since int $0x18 should
never return.
|
|
|
|
|
|
| |
Six bytes down the drain, but people do expect it. If it becomes
an issue we can remove the period; it's better than the CR LF. There
might be some way to efficiently issue . \r \n in common code, too.
|
|
|
|
|
| |
We always re-read the last partition table on any kind of error, so
no need to prevent the code from clobbering it on failure.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|