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

132 lines
3.3 KiB
Plaintext
Raw Normal View History

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
# $NetBSD: GENERIC,v 1.29 2001/11/20 12:56:33 lukem Exp $
Config file with support for both '147 and '167.
1999-02-20 03:18:49 +03:00
include "arch/mvme68k/conf/std.mvme68k"
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
#ident "GENERIC-$Revision: 1.29 $"
Add commented out "ident"-command
2000-01-24 02:46:04 +03:00
Config file with support for both '147 and '167.
1999-02-20 03:18:49 +03:00
# Boards this kernel supports
options MVME147
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 MVME162
Config file with support for both '147 and '167.
1999-02-20 03:18:49 +03:00
options MVME167
Add support for the m68060-based machines: MVME-172 and MVME-177. CPU support taken from a combination of NetBSD/amiga and NetBSD/x68k. At this time, MVME-172 works but MVME-177 is untested. Since the '177 is otherwise identical to the MVME-167, this should *just work*.
2000-11-20 22:35:28 +03:00
options MVME172
options MVME177
Config file with support for both '147 and '167.
1999-02-20 03:18:49 +03:00
maxusers 4
# Needed on m68040 boards to emulate some missing FP instructions
options FPSP
Add support for the m68060-based machines: MVME-172 and MVME-177. CPU support taken from a combination of NetBSD/amiga and NetBSD/x68k. At this time, MVME-172 works but MVME-177 is untested. Since the '177 is otherwise identical to the MVME-167, this should *just work*.
2000-11-20 22:35:28 +03:00
# Needed on m68060 boards
options M060SP
Config file with support for both '147 and '167.
1999-02-20 03:18:49 +03:00
#options DDB
options DIAGNOSTIC, DEBUG
#options SYSVSHM
options KTRACE
options COMPAT_43
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
Config file with support for both '147 and '167.
1999-02-20 03:18:49 +03:00
file-system KERNFS
Merge 'scw_mvme68k_bus_space' branch with the trunk. These changes add support for: o The MI VMEbus framework on both MVME147 and MVME167. o Enhancements to the existing MD bus_space(9) implementation. o Most of the bus_dma(9) API.
2000-03-19 01:33:02 +03:00
file-system MFS
Add CD9660, plus some general cleanup.
2000-11-25 22:33:39 +03:00
file-system CD9660
Config file with support for both '147 and '167.
1999-02-20 03:18:49 +03:00
#file-system MSDOSFS
#file-system UNION
options NFSSERVER
#options FFS_EI # FFS Endian Independant support
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 SOFTDEP # FFS soft updates support.
Config file with support for both '147 and '167.
1999-02-20 03:18:49 +03:00
# Networking options
options INET
bring in content of GENERIC.v6 into GENERIC. remove GENERIC.v6 file (as it is part of GENERIC now). "faith" interface is commented out by default as it is not really for general use. IPsec items are commented out as well, though we can enable "options IPSEC" without export-related issue ("options IPSEC" will enable authentication portion only). We may need to think about it again. if you have problem compiling with INET6 on archs I do not have access to, please contact me. XXX what to do with arch/arm32/SHARK{,.v6}?
1999-11-21 17:00:37 +03:00
options INET6 # IPV6
#options IPSEC # IP security
#options IPSEC_ESP # IP security (encryption part; define w/IPSEC)
#options IPSEC_DEBUG # debug for IP security
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
Config file with support for both '147 and '167.
1999-02-20 03:18:49 +03:00
Add "options COMPAT_AOUT_M68K".
2000-12-07 11:40:06 +03:00
options COMPAT_AOUT_M68K # compatibility with NetBSD/m68k a.out
Oops, missed a trailing comma ...
2000-11-26 00:06:12 +03:00
options COMPAT_09, COMPAT_10, COMPAT_11
Enable compatibility for earlier releases.
2000-11-25 23:35:32 +03:00
options COMPAT_12, COMPAT_13, COMPAT_14, COMPAT_15
Add CD9660, plus some general cleanup.
2000-11-25 22:33:39 +03:00
#options COMPAT_SUNOS
Config file with support for both '147 and '167.
1999-02-20 03:18:49 +03:00
#options COMPAT_M68K4K # compatibility with NetBSD/m68k4k binaries
#options COMPAT_LINUX # compatibility with Linux/m68k 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.
Config file with support for both '147 and '167.
1999-02-20 03:18:49 +03:00
## force NFS root and swap
#config netbsd root on ? type nfs
## "generic" boot (put root on boot device)
config netbsd root on ? type ?
# Which protocol to use when booting over NFS
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
Config file with support for both '147 and '167.
1999-02-20 03:18:49 +03:00
options NFS_BOOT_BOOTPARAM # Diskless client w/ bootparamd
pseudo-device sl
pseudo-device ppp 2
pseudo-device loop
pseudo-device bpfilter
bring in content of GENERIC.v6 into GENERIC. remove GENERIC.v6 file (as it is part of GENERIC now). "faith" interface is commented out by default as it is not really for general use. IPsec items are commented out as well, though we can enable "options IPSEC" without export-related issue ("options IPSEC" will enable authentication portion only). We may need to think about it again. if you have problem compiling with INET6 on archs I do not have access to, please contact me. XXX what to do with arch/arm32/SHARK{,.v6}?
1999-11-21 17:00:37 +03:00
pseudo-device gif 4 # IPv[46] over IPv[46] tunnel (RFC1933)
#pseudo-device faith 1 # IPv[46] tcp relay translation i/f
add stf pseudo interface (commented out due to possible security risks)
2000-04-19 10:50:27 +04:00
#pseudo-device stf 1 # 6to4 IPv6 over IPv4 encapsulation
Add pseudo-device vlan
2000-12-19 13:42:02 +03:00
pseudo-device vlan # IEEE 802.1q encapsulation
Add bridge pseudo devices to GENERIC configs
2001-09-02 01:52:23 +04:00
pseudo-device bridge # simple inter-network bridging
don't specify number of ptys if >= 16 (current default initial number) pty comments: normalize and g/c what is no longer relevant
2000-09-24 19:59:26 +04:00
pseudo-device pty # pseudo-terminals
Config file with support for both '147 and '167.
1999-02-20 03:18:49 +03:00
pseudo-device vnd 2
more rnd(4).
2000-10-05 02:26:49 +04:00
# random number generator pseudo-device
pseudo-device rnd # /dev/random and in-kernel generator
#options RND_COM # use "com" randomness as well (BROKEN)
Config file with support for both '147 and '167.
1999-02-20 03:18:49 +03:00
mainbus0 at root
# MVME147 specific devices
pcc0 at mainbus0
Merge 'scw_mvme68k_bus_space' branch with the trunk. These changes add support for: o The MI VMEbus framework on both MVME147 and MVME167. o Enhancements to the existing MD bus_space(9) implementation. o Most of the bus_dma(9) API.
2000-03-19 01:33:02 +03:00
vmepcc0 at pcc?
Config file with support for both '147 and '167.
1999-02-20 03:18:49 +03:00
clock0 at pcc? ipl 5
Add CD9660, plus some general cleanup.
2000-11-25 22:33:39 +03:00
zsc* at pcc? ipl 4
Config file with support for both '147 and '167.
1999-02-20 03:18:49 +03:00
le0 at pcc? ipl 3
wdsc0 at pcc? ipl 2
Add CD9660, plus some general cleanup.
2000-11-25 22:33:39 +03:00
lpt0 at pcc? ipl 1
Config file with support for both '147 and '167.
1999-02-20 03:18:49 +03:00
Add CD9660, plus some general cleanup.
2000-11-25 22:33:39 +03:00
# MVME16x and MVME17x shared devices
Config file with support for both '147 and '167.
1999-02-20 03:18:49 +03:00
pcctwo0 at mainbus0
Merge 'scw_mvme68k_bus_space' branch with the trunk. These changes add support for: o The MI VMEbus framework on both MVME147 and MVME167. o Enhancements to the existing MD bus_space(9) implementation. o Most of the bus_dma(9) API.
2000-03-19 01:33:02 +03:00
vmetwo0 at mainbus0
memc attaches at mainbus now.
2001-07-27 22:40:27 +04:00
memc* at mainbus0
Config file with support for both '147 and '167.
1999-02-20 03:18:49 +03:00
clock0 at pcctwo? ipl 5
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
Add CD9660, plus some general cleanup.
2000-11-25 22:33:39 +03:00
# MVME162/MVME172 specific devices
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
zsc* at pcctwo? ipl 4
Add CD9660, plus some general cleanup.
2000-11-25 22:33:39 +03:00
# MVME167/MVME177 specific devices
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
clmpcc0 at pcctwo? ipl 4
Add CD9660, plus some general cleanup.
2000-11-25 22:33:39 +03:00
lpt0 at pcctwo? ipl 1
Config file with support for both '147 and '167.
1999-02-20 03:18:49 +03:00
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
# Common front-end for MVME147 and MVME162 `zs' device
zstty* at zsc? channel ?
Config file with support for both '147 and '167.
1999-02-20 03:18:49 +03:00
Add the memory controller ASIC driver.
2000-11-26 00:46:42 +03:00
# MI VMEbus Interface
vme0 at vmepcc0
vme0 at vmetwo0
Merge 'scw_mvme68k_bus_space' branch with the trunk. These changes add support for: o The MI VMEbus framework on both MVME147 and MVME167. o Enhancements to the existing MD bus_space(9) implementation. o Most of the bus_dma(9) API.
2000-03-19 01:33:02 +03:00
# Example VMEbus device
#foo0 at vme0 addr 0x00ef0000 irq 3 vect 0x80
Config file with support for both '147 and '167.
1999-02-20 03:18:49 +03:00
scsibus* at wdsc?
Switch to the MI 53c710 driver recently committed by Izumi Tsutsui.
2001-04-30 13:05:58 +04:00
scsibus* at osiop?
Config file with support for both '147 and '167.
1999-02-20 03:18:49 +03:00
sd* at scsibus? target ? lun ?
st* at scsibus? target ? lun ?
cd* at scsibus? target ? lun ?
Add CD9660, plus some general cleanup.
2000-11-25 22:33:39 +03:00
#ch* at scsibus? target ? lun ?
#ss* at scsibus? target ? lun ? # SCSI scanners
#uk* at scsibus? target ? lun ? # SCSI unknown