Searched hist:42478 (Results 1 - 4 of 4) sorted by relevance
| /freebsd-11-stable/stand/i386/boot2/ | ||
| H A D | boot1.S | diff 42478 Sun Jan 10 13:29:52 MST 1999 peter Damn, I thought I had committed this already, but it seems not. Move the relocated boot1 and arg transfer space from 0x600/0x800 to 0x700/0x900. In theory this should make no difference, apart from the fact that Buslogic controllers happen to use a few bytes at 0x600 for some sort of scratch space for it's int 0x13 hook (!!!), causing the machine to crash badly when the boot2 code makes it's callbacks into boot1 for disk IO. Submitted by: Robert Nordier <rnordier@freebsd.org> |
| H A D | boot2.c | diff 42478 Sun Jan 10 13:29:52 MST 1999 peter Damn, I thought I had committed this already, but it seems not. Move the relocated boot1 and arg transfer space from 0x600/0x800 to 0x700/0x900. In theory this should make no difference, apart from the fact that Buslogic controllers happen to use a few bytes at 0x600 for some sort of scratch space for it's int 0x13 hook (!!!), causing the machine to crash badly when the boot2 code makes it's callbacks into boot1 for disk IO. Submitted by: Robert Nordier <rnordier@freebsd.org> |
| /freebsd-11-stable/stand/i386/isoboot/ | ||
| H A D | isoboot.c | diff 42478 Sun Jan 10 13:29:52 MST 1999 peter Damn, I thought I had committed this already, but it seems not. Move the relocated boot1 and arg transfer space from 0x600/0x800 to 0x700/0x900. In theory this should make no difference, apart from the fact that Buslogic controllers happen to use a few bytes at 0x600 for some sort of scratch space for it's int 0x13 hook (!!!), causing the machine to crash badly when the boot2 code makes it's callbacks into boot1 for disk IO. Submitted by: Robert Nordier <rnordier@freebsd.org> |
| /freebsd-11-stable/stand/i386/gptboot/ | ||
| H A D | gptboot.c | diff 42478 Sun Jan 10 13:29:52 MST 1999 peter Damn, I thought I had committed this already, but it seems not. Move the relocated boot1 and arg transfer space from 0x600/0x800 to 0x700/0x900. In theory this should make no difference, apart from the fact that Buslogic controllers happen to use a few bytes at 0x600 for some sort of scratch space for it's int 0x13 hook (!!!), causing the machine to crash badly when the boot2 code makes it's callbacks into boot1 for disk IO. Submitted by: Robert Nordier <rnordier@freebsd.org> |
Completed in 81 milliseconds