d/freebsd-dev
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
e2f9a08bb0
freebsd-dev/sys/ia64/conf/SKI

69 lines
2.3 KiB
Plaintext
Raw Normal View History

Add a minimalist kernel config which can run inside SKI.
2001-10-09 10:14:06 +00:00
#
# SKI -- Kernel configuration file for FreeBSD/ia64 running in the HP
# SKI simulator
#
# For more information on this file, please read the handbook section on
# Kernel Configuration Files:
#
# http://www.FreeBSD.org/handbook/kernelconfig-config.html
#
# The handbook is also available locally in /usr/share/doc/handbook
# if you've installed the doc distribution, otherwise always see the
# FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the
# latest information.
#
# An exhaustive list of options and more detailed explanations of the
# device lines is also present in the ../../i386/conf/NOTES file.
# If you are in doubt as to the purpose or necessity of a line, check first
# in NOTES. Please note that this is the i386 NOTES, but it still contains
# valuable info for ia64 too.
#
# For hardware specific information check HARDWARE.TXT
#
# $FreeBSD$
machine ia64
cpu ITANIUM
ident SKI
makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols
Remove special casing for running in the simulator from the kernel and instead add platform, firmware and EFI stubs to the loader. The net effect of this change is that besides a special console and disk driver, the kernel has no knowledge of the simulator. This has the following advantages: o Simulator support is much harder to break, o It's easier to make use of more feature complete simulators. This would only need a change in the simulator specific loader, o Running SMP kernels within the simulator. Note that ski at this time does not simulate IPIs, so there's no way to start APs. The platform, firmware and EFI stubs describe the following hardware: o 4 CPU Itanium, o 128 MB RAM within the 4GB address space, o 64 MB RAM above the 4GB address space. NOTE: The stubs in the skiloader describe a machine that should in parts be defined by the simulator. Things like processor interrupt block and AP wakeup vector cannot be choosen at random because they require interpretation by the simulator. Currently the simulator is ignorant of this. This change introduces an unofficial SSC call SSC_SAL_SET_VECTORS which is ignored by the simulator. Tested with: ski (version 0.943 for linux)
2003-02-01 22:50:09 +00:00
makeoptions NO_MODULES=yes #Ignore any x86 CPUTYPE
Add a minimalist kernel config which can run inside SKI.
2001-10-09 10:14:06 +00:00
options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!]
Make this build and sync-up: o Add COMPAT_FREEBSD4 o Remove NO_GEOM o Remove commented out options.
2003-01-03 23:10:47 +00:00
options COMPAT_FREEBSD4
Add a minimalist kernel config which can run inside SKI.
2001-10-09 10:14:06 +00:00
options DDB
Remove special casing for running in the simulator from the kernel and instead add platform, firmware and EFI stubs to the loader. The net effect of this change is that besides a special console and disk driver, the kernel has no knowledge of the simulator. This has the following advantages: o Simulator support is much harder to break, o It's easier to make use of more feature complete simulators. This would only need a change in the simulator specific loader, o Running SMP kernels within the simulator. Note that ski at this time does not simulate IPIs, so there's no way to start APs. The platform, firmware and EFI stubs describe the following hardware: o 4 CPU Itanium, o 128 MB RAM within the 4GB address space, o 64 MB RAM above the 4GB address space. NOTE: The stubs in the skiloader describe a machine that should in parts be defined by the simulator. Things like processor interrupt block and AP wakeup vector cannot be choosen at random because they require interpretation by the simulator. Currently the simulator is ignorant of this. This change introduces an unofficial SSC call SSC_SAL_SET_VECTORS which is ignored by the simulator. Tested with: ski (version 0.943 for linux)
2003-02-01 22:50:09 +00:00
options FFS #Berkeley Fast Filesystem
options INET #InterNETworking
options INET6 #IPv6 communications protocols
Add a minimalist kernel config which can run inside SKI.
2001-10-09 10:14:06 +00:00
options INVARIANTS
options INVARIANT_SUPPORT
options KTR
Remove special casing for running in the simulator from the kernel and instead add platform, firmware and EFI stubs to the loader. The net effect of this change is that besides a special console and disk driver, the kernel has no knowledge of the simulator. This has the following advantages: o Simulator support is much harder to break, o It's easier to make use of more feature complete simulators. This would only need a change in the simulator specific loader, o Running SMP kernels within the simulator. Note that ski at this time does not simulate IPIs, so there's no way to start APs. The platform, firmware and EFI stubs describe the following hardware: o 4 CPU Itanium, o 128 MB RAM within the 4GB address space, o 64 MB RAM above the 4GB address space. NOTE: The stubs in the skiloader describe a machine that should in parts be defined by the simulator. Things like processor interrupt block and AP wakeup vector cannot be choosen at random because they require interpretation by the simulator. Currently the simulator is ignorant of this. This change introduces an unofficial SSC call SSC_SAL_SET_VECTORS which is ignored by the simulator. Tested with: ski (version 0.943 for linux)
2003-02-01 22:50:09 +00:00
options KTRACE #ktrace(1) syscall trace support
Add a minimalist kernel config which can run inside SKI.
2001-10-09 10:14:06 +00:00
options KTR_COMPILE="(KTR_INTR|KTR_PROC)"
options KTR_CPUMASK=0x3
Remove special casing for running in the simulator from the kernel and instead add platform, firmware and EFI stubs to the loader. The net effect of this change is that besides a special console and disk driver, the kernel has no knowledge of the simulator. This has the following advantages: o Simulator support is much harder to break, o It's easier to make use of more feature complete simulators. This would only need a change in the simulator specific loader, o Running SMP kernels within the simulator. Note that ski at this time does not simulate IPIs, so there's no way to start APs. The platform, firmware and EFI stubs describe the following hardware: o 4 CPU Itanium, o 128 MB RAM within the 4GB address space, o 64 MB RAM above the 4GB address space. NOTE: The stubs in the skiloader describe a machine that should in parts be defined by the simulator. Things like processor interrupt block and AP wakeup vector cannot be choosen at random because they require interpretation by the simulator. Currently the simulator is ignorant of this. This change introduces an unofficial SSC call SSC_SAL_SET_VECTORS which is ignored by the simulator. Tested with: ski (version 0.943 for linux)
2003-02-01 22:50:09 +00:00
options KTR_ENTRIES=1024
options KTR_MASK=0
options KTR_VERBOSE
options MD_ROOT #MD is a potential root device
options PROCFS #Process filesystem (requires PSEUDOFS)
options PSEUDOFS #Pseudo-filesystem framework
options SCHED_4BSD #4BSD scheduler
options SCSI_DELAY=500 #Delay (in ms) before probing SCSI
options SKI
options SOFTUPDATES #Enable FFS soft updates support
options SYSVMSG #SYSV-style message queues
options SYSVSEM #SYSV-style semaphores
options SYSVSHM #SYSV-style shared memory
options WITNESS
options _KPOSIX_PRIORITY_SCHEDULING #Posix P1003_1B real-time extensions
Add a minimalist kernel config which can run inside SKI.
2001-10-09 10:14:06 +00:00
Remove special casing for running in the simulator from the kernel and instead add platform, firmware and EFI stubs to the loader. The net effect of this change is that besides a special console and disk driver, the kernel has no knowledge of the simulator. This has the following advantages: o Simulator support is much harder to break, o It's easier to make use of more feature complete simulators. This would only need a change in the simulator specific loader, o Running SMP kernels within the simulator. Note that ski at this time does not simulate IPIs, so there's no way to start APs. The platform, firmware and EFI stubs describe the following hardware: o 4 CPU Itanium, o 128 MB RAM within the 4GB address space, o 64 MB RAM above the 4GB address space. NOTE: The stubs in the skiloader describe a machine that should in parts be defined by the simulator. Things like processor interrupt block and AP wakeup vector cannot be choosen at random because they require interpretation by the simulator. Currently the simulator is ignorant of this. This change introduces an unofficial SSC call SSC_SAL_SET_VECTORS which is ignored by the simulator. Tested with: ski (version 0.943 for linux)
2003-02-01 22:50:09 +00:00
device acpi
device bpf # Berkeley packet filter
Add a minimalist kernel config which can run inside SKI.
2001-10-09 10:14:06 +00:00
device ether # Ethernet support
Remove special casing for running in the simulator from the kernel and instead add platform, firmware and EFI stubs to the loader. The net effect of this change is that besides a special console and disk driver, the kernel has no knowledge of the simulator. This has the following advantages: o Simulator support is much harder to break, o It's easier to make use of more feature complete simulators. This would only need a change in the simulator specific loader, o Running SMP kernels within the simulator. Note that ski at this time does not simulate IPIs, so there's no way to start APs. The platform, firmware and EFI stubs describe the following hardware: o 4 CPU Itanium, o 128 MB RAM within the 4GB address space, o 64 MB RAM above the 4GB address space. NOTE: The stubs in the skiloader describe a machine that should in parts be defined by the simulator. Things like processor interrupt block and AP wakeup vector cannot be choosen at random because they require interpretation by the simulator. Currently the simulator is ignorant of this. This change introduces an unofficial SSC call SSC_SAL_SET_VECTORS which is ignored by the simulator. Tested with: ski (version 0.943 for linux)
2003-02-01 22:50:09 +00:00
device loop # Network loopback
Add a minimalist kernel config which can run inside SKI.
2001-10-09 10:14:06 +00:00
device md # Memory "disks"
Remove special casing for running in the simulator from the kernel and instead add platform, firmware and EFI stubs to the loader. The net effect of this change is that besides a special console and disk driver, the kernel has no knowledge of the simulator. This has the following advantages: o Simulator support is much harder to break, o It's easier to make use of more feature complete simulators. This would only need a change in the simulator specific loader, o Running SMP kernels within the simulator. Note that ski at this time does not simulate IPIs, so there's no way to start APs. The platform, firmware and EFI stubs describe the following hardware: o 4 CPU Itanium, o 128 MB RAM within the 4GB address space, o 64 MB RAM above the 4GB address space. NOTE: The stubs in the skiloader describe a machine that should in parts be defined by the simulator. Things like processor interrupt block and AP wakeup vector cannot be choosen at random because they require interpretation by the simulator. Currently the simulator is ignorant of this. This change introduces an unofficial SSC call SSC_SAL_SET_VECTORS which is ignored by the simulator. Tested with: ski (version 0.943 for linux)
2003-02-01 22:50:09 +00:00
device pci
device pty # Pseudo-ttys (telnet etc)
device random # Entropy device
device tun # Packet tunnel.
Reference in New Issue Copy Permalink