Aren/NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
bc226765c8
NetBSD/sys/arch/mvme68k/conf/VME162

94 lines
2.1 KiB
Plaintext
Raw Normal View History

enable USERCONF by default; it's small and extremely useful to have available.
2002-09-18 06:43:53 +04:00
# $NetBSD: VME162,v 1.15 2002/09/18 02:44:03 lukem Exp $
Add preliminary support for the MVME162-LX 200/300 series of boards. Currently, the major onboard devices are supported (disk, network, rs232 and VMEbus). However, work is still need to support the remaining devices (eg. IndustryPack sites). These boards are available with a dazzling array of build options. At this time, the following options are *required*: o Real floating point hardware (the 68LC040 model isn't tested), o The VMEchip2 must be present, o If offboard VMEbus RAM is not present, at least 8MB of onboard RAM is required. o Even if offboard VMEbus RAM *is* present, at least 4MB of onboard RAM is required. (Boards with 1 or 2MB onboard RAM *can* be supported with offboard RAM, but not without some funky values in the VMEbus Master mapping registers.) There is no support for boards other than those in the -LX 200/300 series.
2000-09-06 23:51:42 +04:00
include "arch/mvme68k/conf/std.mvme68k"
Add the INCLUDE_CONFIG_FILE option to all config files. In config files that are generic (ie, GENERIC, GENERICSBC, GENERIC32, ALL, or ALPHA), it is uncommented.
2002-04-25 19:06:20 +04:00
#options INCLUDE_CONFIG_FILE # embed config file in kernel binary
Add preliminary support for the MVME162-LX 200/300 series of boards. Currently, the major onboard devices are supported (disk, network, rs232 and VMEbus). However, work is still need to support the remaining devices (eg. IndustryPack sites). These boards are available with a dazzling array of build options. At this time, the following options are *required*: o Real floating point hardware (the 68LC040 model isn't tested), o The VMEchip2 must be present, o If offboard VMEbus RAM is not present, at least 8MB of onboard RAM is required. o Even if offboard VMEbus RAM *is* present, at least 4MB of onboard RAM is required. (Boards with 1 or 2MB onboard RAM *can* be supported with offboard RAM, but not without some funky values in the VMEbus Master mapping registers.) There is no support for boards other than those in the -LX 200/300 series.
2000-09-06 23:51:42 +04:00
# Boards this kernel supports; need at least one
options MVME162
# Needed on m68040 boards to emulate some missing FP instructions
options FPSP
Add CD9660, plus some general cleanup.
2000-11-25 22:33:39 +03:00
maxusers 8
Add preliminary support for the MVME162-LX 200/300 series of boards. Currently, the major onboard devices are supported (disk, network, rs232 and VMEbus). However, work is still need to support the remaining devices (eg. IndustryPack sites). These boards are available with a dazzling array of build options. At this time, the following options are *required*: o Real floating point hardware (the 68LC040 model isn't tested), o The VMEchip2 must be present, o If offboard VMEbus RAM is not present, at least 8MB of onboard RAM is required. o Even if offboard VMEbus RAM *is* present, at least 4MB of onboard RAM is required. (Boards with 1 or 2MB onboard RAM *can* be supported with offboard RAM, but not without some funky values in the VMEbus Master mapping registers.) There is no support for boards other than those in the -LX 200/300 series.
2000-09-06 23:51:42 +04:00
Add CD9660, plus some general cleanup.
2000-11-25 22:33:39 +03:00
#options DDB
#options DIAGNOSTIC, DEBUG
Add preliminary support for the MVME162-LX 200/300 series of boards. Currently, the major onboard devices are supported (disk, network, rs232 and VMEbus). However, work is still need to support the remaining devices (eg. IndustryPack sites). These boards are available with a dazzling array of build options. At this time, the following options are *required*: o Real floating point hardware (the 68LC040 model isn't tested), o The VMEchip2 must be present, o If offboard VMEbus RAM is not present, at least 8MB of onboard RAM is required. o Even if offboard VMEbus RAM *is* present, at least 4MB of onboard RAM is required. (Boards with 1 or 2MB onboard RAM *can* be supported with offboard RAM, but not without some funky values in the VMEbus Master mapping registers.) There is no support for boards other than those in the -LX 200/300 series.
2000-09-06 23:51:42 +04:00
#options SYSVSHM
options KTRACE
options COMPAT_43
enable USERCONF by default; it's small and extremely useful to have available.
2002-09-18 06:43:53 +04:00
options USERCONF # userconf(4) support
add options PIPE_SOCKETPAIR to individual kernel configs the option is commented out on everything but kernels I was able to recognize as INSTALL-like or ones for small memory machines
2002-01-27 16:23:08 +03:00
#options PIPE_SOCKETPAIR # smaller, but slower pipe(2)
Add preliminary support for the MVME162-LX 200/300 series of boards. Currently, the major onboard devices are supported (disk, network, rs232 and VMEbus). However, work is still need to support the remaining devices (eg. IndustryPack sites). These boards are available with a dazzling array of build options. At this time, the following options are *required*: o Real floating point hardware (the 68LC040 model isn't tested), o The VMEchip2 must be present, o If offboard VMEbus RAM is not present, at least 8MB of onboard RAM is required. o Even if offboard VMEbus RAM *is* present, at least 4MB of onboard RAM is required. (Boards with 1 or 2MB onboard RAM *can* be supported with offboard RAM, but not without some funky values in the VMEbus Master mapping registers.) There is no support for boards other than those in the -LX 200/300 series.
2000-09-06 23:51:42 +04:00
file-system FFS
cleanup: options SPACE TAB makeoptions TAB psuedo-device TAB remove trailing whitespace replace multiple spaces -> tabs options "FOO" -> options FOO options "FOO=bar" -> options FOO=bar options "FOO=\"bar\"" -> options FOO="\"bar\""
2001-11-20 15:56:17 +03:00
file-system NFS
Add preliminary support for the MVME162-LX 200/300 series of boards. Currently, the major onboard devices are supported (disk, network, rs232 and VMEbus). However, work is still need to support the remaining devices (eg. IndustryPack sites). These boards are available with a dazzling array of build options. At this time, the following options are *required*: o Real floating point hardware (the 68LC040 model isn't tested), o The VMEchip2 must be present, o If offboard VMEbus RAM is not present, at least 8MB of onboard RAM is required. o Even if offboard VMEbus RAM *is* present, at least 4MB of onboard RAM is required. (Boards with 1 or 2MB onboard RAM *can* be supported with offboard RAM, but not without some funky values in the VMEbus Master mapping registers.) There is no support for boards other than those in the -LX 200/300 series.
2000-09-06 23:51:42 +04:00
file-system KERNFS
file-system MFS
Add CD9660, plus some general cleanup.
2000-11-25 22:33:39 +03:00
file-system CD9660
Add preliminary support for the MVME162-LX 200/300 series of boards. Currently, the major onboard devices are supported (disk, network, rs232 and VMEbus). However, work is still need to support the remaining devices (eg. IndustryPack sites). These boards are available with a dazzling array of build options. At this time, the following options are *required*: o Real floating point hardware (the 68LC040 model isn't tested), o The VMEchip2 must be present, o If offboard VMEbus RAM is not present, at least 8MB of onboard RAM is required. o Even if offboard VMEbus RAM *is* present, at least 4MB of onboard RAM is required. (Boards with 1 or 2MB onboard RAM *can* be supported with offboard RAM, but not without some funky values in the VMEbus Master mapping registers.) There is no support for boards other than those in the -LX 200/300 series.
2000-09-06 23:51:42 +04:00
#file-system MSDOSFS
#file-system UNION
#options NFSSERVER
#options FFS_EI # FFS Endian Independant support
# Networking options
options INET
cleanup: options SPACE TAB makeoptions TAB psuedo-device TAB remove trailing whitespace replace multiple spaces -> tabs options "FOO" -> options FOO options "FOO=bar" -> options FOO=bar options "FOO=\"bar\"" -> options FOO="\"bar\""
2001-11-20 15:56:17 +03:00
#options GATEWAY # IP packet forwarding
#options ISO # OSI networking
#options TPIP
#options EON
Standardise TCP_COMPAT_42 as commented out, grouped with other COMPAT options, and with the comment '4.2BSD TCP/IP bug compat. Not recommended' Add commented out 'TCP_DEBUG # Record last TCP_NDEBUG packets with SO_DEBUG' (All hail amiga and atari which make some attempt to automate the multiplicity of config files...)
2001-07-08 20:32:12 +04:00
#options TCP_DEBUG # Record last TCP_NDEBUG packets with SO_DEBUG
Add preliminary support for the MVME162-LX 200/300 series of boards. Currently, the major onboard devices are supported (disk, network, rs232 and VMEbus). However, work is still need to support the remaining devices (eg. IndustryPack sites). These boards are available with a dazzling array of build options. At this time, the following options are *required*: o Real floating point hardware (the 68LC040 model isn't tested), o The VMEchip2 must be present, o If offboard VMEbus RAM is not present, at least 8MB of onboard RAM is required. o Even if offboard VMEbus RAM *is* present, at least 4MB of onboard RAM is required. (Boards with 1 or 2MB onboard RAM *can* be supported with offboard RAM, but not without some funky values in the VMEbus Master mapping registers.) There is no support for boards other than those in the -LX 200/300 series.
2000-09-06 23:51:42 +04:00
Add "options COMPAT_AOUT_M68K".
2000-12-07 11:40:06 +03:00
options COMPAT_AOUT_M68K # compatibility with NetBSD/m68k a.out
Add preliminary support for the MVME162-LX 200/300 series of boards. Currently, the major onboard devices are supported (disk, network, rs232 and VMEbus). However, work is still need to support the remaining devices (eg. IndustryPack sites). These boards are available with a dazzling array of build options. At this time, the following options are *required*: o Real floating point hardware (the 68LC040 model isn't tested), o The VMEchip2 must be present, o If offboard VMEbus RAM is not present, at least 8MB of onboard RAM is required. o Even if offboard VMEbus RAM *is* present, at least 4MB of onboard RAM is required. (Boards with 1 or 2MB onboard RAM *can* be supported with offboard RAM, but not without some funky values in the VMEbus Master mapping registers.) There is no support for boards other than those in the -LX 200/300 series.
2000-09-06 23:51:42 +04:00
#options COMPAT_14, COMPAT_13, COMPAT_12
#options COMPAT_SUNOS
#options COMPAT_M68K4K # compatibility with NetBSD/m68k4k binaries
Standardise TCP_COMPAT_42 as commented out, grouped with other COMPAT options, and with the comment '4.2BSD TCP/IP bug compat. Not recommended' Add commented out 'TCP_DEBUG # Record last TCP_NDEBUG packets with SO_DEBUG' (All hail amiga and atari which make some attempt to automate the multiplicity of config files...)
2001-07-08 20:32:12 +04:00
#options TCP_COMPAT_42 # 4.2BSD TCP/IP bug compat. Not recommended.
Add preliminary support for the MVME162-LX 200/300 series of boards. Currently, the major onboard devices are supported (disk, network, rs232 and VMEbus). However, work is still need to support the remaining devices (eg. IndustryPack sites). These boards are available with a dazzling array of build options. At this time, the following options are *required*: o Real floating point hardware (the 68LC040 model isn't tested), o The VMEchip2 must be present, o If offboard VMEbus RAM is not present, at least 8MB of onboard RAM is required. o Even if offboard VMEbus RAM *is* present, at least 4MB of onboard RAM is required. (Boards with 1 or 2MB onboard RAM *can* be supported with offboard RAM, but not without some funky values in the VMEbus Master mapping registers.) There is no support for boards other than those in the -LX 200/300 series.
2000-09-06 23:51:42 +04:00
## force NFS root and swap
#config netbsd root on ? type nfs
## "generic" boot (put root on boot device)
config netbsd root on ? type ?
Enable DHCP and BOOTP as supported diskless NFS boot options.
2001-06-10 18:40:47 +04:00
options NFS_BOOT_DHCP # Diskless client w/ dhcp
options NFS_BOOT_BOOTP # Diskless client w/ bootp
Add preliminary support for the MVME162-LX 200/300 series of boards. Currently, the major onboard devices are supported (disk, network, rs232 and VMEbus). However, work is still need to support the remaining devices (eg. IndustryPack sites). These boards are available with a dazzling array of build options. At this time, the following options are *required*: o Real floating point hardware (the 68LC040 model isn't tested), o The VMEchip2 must be present, o If offboard VMEbus RAM is not present, at least 8MB of onboard RAM is required. o Even if offboard VMEbus RAM *is* present, at least 4MB of onboard RAM is required. (Boards with 1 or 2MB onboard RAM *can* be supported with offboard RAM, but not without some funky values in the VMEbus Master mapping registers.) There is no support for boards other than those in the -LX 200/300 series.
2000-09-06 23:51:42 +04:00
options NFS_BOOT_BOOTPARAM # Diskless client w/ bootparamd
pseudo-device sl
pseudo-device ppp 2
pseudo-device loop
pseudo-device bpfilter
pseudo-device pty
pseudo-device vnd 2
Add rnd(4) pseudo-device.
2001-06-10 17:16:07 +04:00
pseudo-device rnd
Enable "pseudo-device clockctl" in all kernels, except installation related kernels (INSTALL* and RAMDISK*). This enables rc.conf(5) $ntpd_chroot to be used "out of the box"
2002-06-17 09:14:02 +04:00
pseudo-device clockctl # user control of clock subsystem
Add preliminary support for the MVME162-LX 200/300 series of boards. Currently, the major onboard devices are supported (disk, network, rs232 and VMEbus). However, work is still need to support the remaining devices (eg. IndustryPack sites). These boards are available with a dazzling array of build options. At this time, the following options are *required*: o Real floating point hardware (the 68LC040 model isn't tested), o The VMEchip2 must be present, o If offboard VMEbus RAM is not present, at least 8MB of onboard RAM is required. o Even if offboard VMEbus RAM *is* present, at least 4MB of onboard RAM is required. (Boards with 1 or 2MB onboard RAM *can* be supported with offboard RAM, but not without some funky values in the VMEbus Master mapping registers.) There is no support for boards other than those in the -LX 200/300 series.
2000-09-06 23:51:42 +04:00
mainbus0 at root
pcctwo0 at mainbus0
clock0 at pcctwo? ipl 5
zsc* at pcctwo? ipl 4
ie0 at pcctwo? ipl 3
Switch to the MI 53c710 driver recently committed by Izumi Tsutsui.
2001-04-30 13:05:58 +04:00
osiop0 at pcctwo? ipl 2
Add preliminary support for the MVME162-LX 200/300 series of boards. Currently, the major onboard devices are supported (disk, network, rs232 and VMEbus). However, work is still need to support the remaining devices (eg. IndustryPack sites). These boards are available with a dazzling array of build options. At this time, the following options are *required*: o Real floating point hardware (the 68LC040 model isn't tested), o The VMEchip2 must be present, o If offboard VMEbus RAM is not present, at least 8MB of onboard RAM is required. o Even if offboard VMEbus RAM *is* present, at least 4MB of onboard RAM is required. (Boards with 1 or 2MB onboard RAM *can* be supported with offboard RAM, but not without some funky values in the VMEbus Master mapping registers.) There is no support for boards other than those in the -LX 200/300 series.
2000-09-06 23:51:42 +04:00
zstty* at zsc? channel ?
# VMEbus Support
vmetwo0 at mainbus0
vme0 at vmetwo0
# Example VMEbus device
#foo0 at vme0 addr 0x10001000 am 0x0d irq 3 vect 0x80
memc attaches at mainbus now.
2001-07-27 22:40:27 +04:00
# Memory Controller Support (MCECC and MEMC040)
memc* at mainbus0
Add preliminary support for the MVME162-LX 200/300 series of boards. Currently, the major onboard devices are supported (disk, network, rs232 and VMEbus). However, work is still need to support the remaining devices (eg. IndustryPack sites). These boards are available with a dazzling array of build options. At this time, the following options are *required*: o Real floating point hardware (the 68LC040 model isn't tested), o The VMEchip2 must be present, o If offboard VMEbus RAM is not present, at least 8MB of onboard RAM is required. o Even if offboard VMEbus RAM *is* present, at least 4MB of onboard RAM is required. (Boards with 1 or 2MB onboard RAM *can* be supported with offboard RAM, but not without some funky values in the VMEbus Master mapping registers.) There is no support for boards other than those in the -LX 200/300 series.
2000-09-06 23:51:42 +04:00
# SCSI Bus Support
Switch to the MI 53c710 driver recently committed by Izumi Tsutsui.
2001-04-30 13:05:58 +04:00
scsibus* at osiop?
Add preliminary support for the MVME162-LX 200/300 series of boards. Currently, the major onboard devices are supported (disk, network, rs232 and VMEbus). However, work is still need to support the remaining devices (eg. IndustryPack sites). These boards are available with a dazzling array of build options. At this time, the following options are *required*: o Real floating point hardware (the 68LC040 model isn't tested), o The VMEchip2 must be present, o If offboard VMEbus RAM is not present, at least 8MB of onboard RAM is required. o Even if offboard VMEbus RAM *is* present, at least 4MB of onboard RAM is required. (Boards with 1 or 2MB onboard RAM *can* be supported with offboard RAM, but not without some funky values in the VMEbus Master mapping registers.) There is no support for boards other than those in the -LX 200/300 series.
2000-09-06 23:51:42 +04:00
sd* at scsibus? target ? lun ?
st* at scsibus? target ? lun ?
Add CD9660, plus some general cleanup.
2000-11-25 22:33:39 +03:00
cd* at scsibus? target ? lun ?
Reference in New Issue Copy Permalink