Cross Reference: /src/sys/arch/next68k/stand/boot/README

History log of /src/sys/arch/next68k/stand/boot/README
Revision	Date	Author	Comments
1.2	04-Feb-2023	tsutsui	Remove trailing spaces and TABs.
1.1	09-Jun-1998	dbj	branches: 1.1.1; Initial revision
1.1.1.1	09-Jun-1998	dbj	branches: 1.1.1.1.242; 1.1.1.1.268; Initial import of NetBSD/next68k.
1.1.1.1.268.1	12-Feb-2023	martin	Pull up following revision(s) (requested by tsutsui in ticket #78): sys/arch/next68k/stand/boot/scsi.c: revision 1.11 sys/arch/next68k/stand/boot/sd.c: revision 1.13 sys/arch/next68k/stand/boot/scsi.c: revision 1.12 sys/arch/next68k/stand/boot/sd.c: revision 1.14 sys/arch/next68k/stand/boot/sd.c: revision 1.15 sys/arch/next68k/stand/boot/sd.c: revision 1.16 sys/arch/next68k/stand/boot/rtc.c: revision 1.7 sys/arch/next68k/stand/boot/dmareg.h: revision 1.4 sys/arch/next68k/stand/boot/machdep.c: revision 1.8 sys/arch/next68k/stand/boot/srt0.s: revision 1.3 sys/arch/next68k/stand/boot/README: revision 1.2 sys/arch/next68k/stand/boot/devopen.c: revision 1.7 sys/arch/next68k/stand/boot/Makefile: revision 1.30 sys/arch/next68k/stand/boot/Makefile: revision 1.31 sys/arch/next68k/stand/boot/version: revision 1.5 Remove trailing spaces and TABs. Make sure to specify volatile explicitly on DMA register accesses. It looks booting from SCSI disks on next68k have been broken since NetBSD 1.6 days, but now it works. Avoid possible division by zero trap in error cases to make debug easier. Request only 36 bytes for a response of INQUIRY command for legacy drives. Some drives don't respond larger requested size for newer SCSI3 devices and not all drivers can handle short xfers. We should fix drivers to handle such short xfers properly, but we need only SCSI device type here (and the 36 bytes are enough even if we want vendor and product names on a bootloader). The problem is reported from Andreas Grabher (a maintainer of NeXT Computer Emulator) on port-next68k@: https://mail-index.netbsd.org/port-next68k/2023/02/thread1.html Disable DEBUG options properly. Bump version to 1.6 to denote recent bootloader's >20 years old bug fixes.
1.1.1.1.242.1	12-Feb-2023	martin	Pull up following revision(s) (requested by tsutsui in ticket #1591): sys/arch/next68k/stand/boot/scsi.c: revision 1.11 sys/arch/next68k/stand/boot/sd.c: revision 1.13 sys/arch/next68k/stand/boot/scsi.c: revision 1.12 sys/arch/next68k/stand/boot/sd.c: revision 1.14 sys/arch/next68k/stand/boot/sd.c: revision 1.15 sys/arch/next68k/stand/boot/sd.c: revision 1.16 sys/arch/next68k/stand/boot/rtc.c: revision 1.7 sys/arch/next68k/stand/boot/dmareg.h: revision 1.4 sys/arch/next68k/stand/boot/machdep.c: revision 1.8 sys/arch/next68k/stand/boot/srt0.s: revision 1.3 sys/arch/next68k/stand/boot/README: revision 1.2 sys/arch/next68k/stand/boot/devopen.c: revision 1.7 sys/arch/next68k/stand/boot/Makefile: revision 1.30 sys/arch/next68k/stand/boot/Makefile: revision 1.31 sys/arch/next68k/stand/boot/version: revision 1.5 Remove trailing spaces and TABs. Make sure to specify volatile explicitly on DMA register accesses. It looks booting from SCSI disks on next68k have been broken since NetBSD 1.6 days, but now it works. Avoid possible division by zero trap in error cases to make debug easier. Request only 36 bytes for a response of INQUIRY command for legacy drives. Some drives don't respond larger requested size for newer SCSI3 devices and not all drivers can handle short xfers. We should fix drivers to handle such short xfers properly, but we need only SCSI device type here (and the 36 bytes are enough even if we want vendor and product names on a bootloader). The problem is reported from Andreas Grabher (a maintainer of NeXT Computer Emulator) on port-next68k@: https://mail-index.netbsd.org/port-next68k/2023/02/thread1.html Disable DEBUG options properly. Bump version to 1.6 to denote recent bootloader's >20 years old bug fixes.

OpenGrok