d/freebsd-nq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
d5dba21cf6
freebsd-nq/sys/sparc64/conf/GENERIC

270 lines
10 KiB
Plaintext
Raw Normal View History

Add a GENERIC kernel config for sparc64.
2001-08-14 03:27:02 +00:00
#
# GENERIC -- Generic kernel configuration file for FreeBSD/sparc64
#
o merge from amd64: - r187144: Add a reference to the config(5) manpage and to the "env" kernel config option. - Add/enable the default USB drivers. Originally the USB controller and keyboard drivers were disabled as these interacted badly with the Open Firmware console driver, i.e. caused the keyboard to not work with ofw_console(4). Even when switch to uart(4) and the frame buffer drivers most of the USB drivers still were kept disabled as several of them, amongst others all of the drivers for USB Ethernet controllers, weren't endian clean. With the new USB stack these problem should be gone now so there's no longer a reason to not include the same set of USB drivers amd64 does. o Remove the commented out device ofw_console; apart from it being currently broken by some TTY changes one really needs to know how to actually enable and make it work correctly.
2009-06-24 20:49:02 +00:00
# For more information on this file, please read the config(5) manual page,
# and/or the handbook section on Kernel Configuration Files:
Add a GENERIC kernel config for sparc64.
2001-08-14 03:27:02 +00:00
#
Fix the link to the Handbook
2002-08-01 17:21:18 +00:00
# http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html
Add a GENERIC kernel config for sparc64.
2001-08-14 03:27:02 +00:00
#
# 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
- Sync whitespace and comments with i386 GENERIC. - Add some commented out NICs from i386 GENERIC. Most of them look like they would work but I'm not sure if they are endian-clean and can't test. There was a report that sk(4) works on sparc64 but it doesn't look like it would because it doesn't use busdma. - Improve some of the descriptions of sparc64 specific devices. There's no functional change, i.e. no added or deleted uncommented devices or options, in this commit.
2004-08-16 23:23:21 +00:00
# device lines is also present in the ../../conf/NOTES and NOTES files.
# If you are in doubt as to the purpose or necessity of a line, check first
Various comment and minor style fixes. No actual content changes. Inspired by: bde
2002-07-16 18:20:17 +00:00
# in NOTES.
+ Blah, there was nothing wrong in rev 1.1 talking about the i386/NOTES. I should have diff'ed the header with the Alpha GENERIC. + fix style nit + turn on NO_MODULES for now.
2001-09-02 23:48:37 +00:00
#
Add a GENERIC kernel config for sparc64.
2001-08-14 03:27:02 +00:00
# $FreeBSD$
cpu SUN4U
ident GENERIC
- Sync whitespace and comments with i386 GENERIC. - Add some commented out NICs from i386 GENERIC. Most of them look like they would work but I'm not sure if they are endian-clean and can't test. There was a report that sk(4) works on sparc64 but it doesn't look like it would because it doesn't use busdma. - Improve some of the descriptions of sparc64 specific devices. There's no functional change, i.e. no added or deleted uncommented devices or options, in this commit.
2004-08-16 23:23:21 +00:00
makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols
Match the style of very other platform we have.
2001-09-02 23:37:45 +00:00
Sync with the Alpha's GENERIC configuration. Most of the contents are commented out as they are as-yet untested. However, I wanted the contents to match our other arches, so that when people make changes to {i386,alpha,ia64}, they will also make the same changes here.
2002-02-24 18:49:38 +00:00
# Platforms supported
# At this time all platforms are supported, as-is.
Switch the default scheduler to 4BSD to match what will go into RELENG_5 soon. It can be switched back once 5.3 is tested and released. Also turn on PREEMPTION as many of the stability problems with it have been fixed. MT5: 3 days.
2004-09-07 22:37:43 +00:00
options SCHED_4BSD # 4BSD scheduler
sparc64 is not ready for PREEMPTION, so turn it off for now.
2004-09-09 17:03:53 +00:00
#options PREEMPTION # Enable kernel thread preemption
- Sync whitespace and comments with i386 GENERIC. - Add some commented out NICs from i386 GENERIC. Most of them look like they would work but I'm not sure if they are endian-clean and can't test. There was a report that sk(4) works on sparc64 but it doesn't look like it would because it doesn't use busdma. - Improve some of the descriptions of sparc64 specific devices. There's no functional change, i.e. no added or deleted uncommented devices or options, in this commit.
2004-08-16 23:23:21 +00:00
options INET # InterNETworking
options INET6 # IPv6 communications protocols
Use the correct expanded name for SCTP. PR: 116496 Submitted by: koitsu Reviewed by: rrs Approved by: re (kensmith)
2007-09-26 20:05:07 +00:00
options SCTP # Stream Control Transmission Protocol
- Sync whitespace and comments with i386 GENERIC. - Add some commented out NICs from i386 GENERIC. Most of them look like they would work but I'm not sure if they are endian-clean and can't test. There was a report that sk(4) works on sparc64 but it doesn't look like it would because it doesn't use busdma. - Improve some of the descriptions of sparc64 specific devices. There's no functional change, i.e. no added or deleted uncommented devices or options, in this commit.
2004-08-16 23:23:21 +00:00
options FFS # Berkeley Fast Filesystem
options SOFTUPDATES # Enable FFS soft updates support
options UFS_ACL # Support for access control lists
options UFS_DIRHASH # Improve performance on big directories
Remove trailing '.' for consistency!
2007-04-10 21:40:13 +00:00
options UFS_GJOURNAL # Enable gjournal-based UFS journaling
- Sync whitespace and comments with i386 GENERIC. - Add some commented out NICs from i386 GENERIC. Most of them look like they would work but I'm not sure if they are endian-clean and can't test. There was a report that sk(4) works on sparc64 but it doesn't look like it would because it doesn't use busdma. - Improve some of the descriptions of sparc64 specific devices. There's no functional change, i.e. no added or deleted uncommented devices or options, in this commit.
2004-08-16 23:23:21 +00:00
options MD_ROOT # MD is a potential root device
options NFSCLIENT # Network Filesystem Client
options NFSSERVER # Network Filesystem Server
Add kernel module support for nfslockd and krpc. Use the module system to detect (or load) kernel NLM support in rpc.lockd. Remove the '-k' option to rpc.lockd and make kernel NLM the default. A user can still force the use of the old user NLM by building a kernel without NFSLOCKD and/or removing the nfslockd.ko module.
2008-03-27 11:54:20 +00:00
options NFSLOCKD # Network Lock Manager
- Sync whitespace and comments with i386 GENERIC. - Add some commented out NICs from i386 GENERIC. Most of them look like they would work but I'm not sure if they are endian-clean and can't test. There was a report that sk(4) works on sparc64 but it doesn't look like it would because it doesn't use busdma. - Improve some of the descriptions of sparc64 specific devices. There's no functional change, i.e. no added or deleted uncommented devices or options, in this commit.
2004-08-16 23:23:21 +00:00
options NFS_ROOT # NFS usable as /, requires NFSCLIENT
#options MSDOSFS # MSDOS Filesystem
options CD9660 # ISO 9660 Filesystem
options PROCFS # Process filesystem (requires PSEUDOFS)
options PSEUDOFS # Pseudo-filesystem framework
Evolve the ctlreq interface added to geom_gpt into a generic partitioning class that supports multiple schemes. Current schemes supported are APM (Apple Partition Map) and GPT. Change all GEOM_APPLE anf GEOM_GPT options into GEOM_PART_APM and GEOM_PART_GPT (resp). The ctlreq interface supports verbs to create and destroy partitioning schemes on a disk; to add, delete and modify partitions; and to commit or undo changes made.
2007-02-07 18:55:31 +00:00
options GEOM_PART_GPT # GUID Partition Tables.
Include GEOM_LABEL in GENERIC. It's very useful and not well publicized enough. Approved by: pjd
2007-02-09 19:03:18 +00:00
options GEOM_LABEL # Provides labelization
Add recently invented COMPAT_FREEBSD5 option. MFC after: 3 days
2005-07-14 15:39:06 +00:00
options COMPAT_FREEBSD5 # Compatible with FreeBSD5
Added COMPAT_FREEBSD6 option.
2006-09-26 12:36:34 +00:00
options COMPAT_FREEBSD6 # Compatible with FreeBSD6
Add COMPAT_FREEBSD7 and enable it in configs that have COMPAT_FREEBSD6.
2008-01-07 21:40:11 +00:00
options COMPAT_FREEBSD7 # Compatible with FreeBSD7
Reduce annoying SCSI probing delay from 15 to 5 seconds in all GENRIC kernels. Discussed on: -current
2004-11-02 20:57:20 +00:00
options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI
- Sync whitespace and comments with i386 GENERIC. - Add some commented out NICs from i386 GENERIC. Most of them look like they would work but I'm not sure if they are endian-clean and can't test. There was a report that sk(4) works on sparc64 but it doesn't look like it would because it doesn't use busdma. - Improve some of the descriptions of sparc64 specific devices. There's no functional change, i.e. no added or deleted uncommented devices or options, in this commit.
2004-08-16 23:23:21 +00:00
options KTRACE # ktrace(1) support
Break out stack(9) from ddb(4): - Introduce per-architecture stack_machdep.c to hold stack_save(9). - Introduce per-architecture machine/stack.h to capture any common definitions required between db_trace.c and stack_machdep.c. - Add new kernel option "options STACK"; we will build in stack(9) if it is defined, or also if "options DDB" is defined to provide compatibility with existing users of stack(9). Add new stack_save_td(9) function, which allows the capture of a stacktrace of another thread rather than the current thread, which the existing stack_save(9) was limited to. It requires that the thread be neither swapped out nor running, which is the responsibility of the consumer to enforce. Update stack(9) man page. Build tested: amd64, arm, i386, ia64, powerpc, sparc64, sun4v Runtime tested: amd64 (rwatson), arm (cognet), i386 (rwatson)
2007-12-02 20:40:35 +00:00
options STACK # stack(9) support
- Sync whitespace and comments with i386 GENERIC. - Add some commented out NICs from i386 GENERIC. Most of them look like they would work but I'm not sure if they are endian-clean and can't test. There was a report that sk(4) works on sparc64 but it doesn't look like it would because it doesn't use busdma. - Improve some of the descriptions of sparc64 specific devices. There's no functional change, i.e. no added or deleted uncommented devices or options, in this commit.
2004-08-16 23:23:21 +00:00
options SYSVSHM # SYSV-style shared memory
options SYSVMSG # SYSV-style message queues
options SYSVSEM # SYSV-style semaphores
Enable POSIX semaphores on all non-embedded architectures by default. More applications (including Firefox) seem to depend on this nowadays, so not having this enabled by default is a bad idea. Proposed by: miwi Patch by: Florian Smeets <flo kasimir com> Approved by: re (kib)
2009-07-02 18:24:37 +00:00
options P1003_1B_SEMAPHORES # POSIX-style semaphores
- Sync whitespace and comments with i386 GENERIC. - Add some commented out NICs from i386 GENERIC. Most of them look like they would work but I'm not sure if they are endian-clean and can't test. There was a report that sk(4) works on sparc64 but it doesn't look like it would because it doesn't use busdma. - Improve some of the descriptions of sparc64 specific devices. There's no functional change, i.e. no added or deleted uncommented devices or options, in this commit.
2004-08-16 23:23:21 +00:00
options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions
Merge r194204 from amd64/i386: Enable PRINTF_BUFR_SIZE by default. PR: 139134 MFC after: 3 days
2009-09-25 17:08:51 +00:00
options PRINTF_BUFR_SIZE=128 # Prevent printf output being interspersed.
Add HWPMC_HOOKS to GENERIC kernels, this makes hwpmc.ko work out of the box.
2008-07-07 22:55:11 +00:00
options HWPMC_HOOKS # Necessary kernel hooks for hwpmc(4)
Enable AUDIT by default in the GENERIC kernel, allowing security event auditing to be turned on without a kernel recompile, just an rc.conf option. Approved by: re (kensmith) Obtained from: TrustedBSD Project
2007-06-08 20:29:07 +00:00
options AUDIT # Security event auditing
Remove MAC kernel config files and add "options MAC" to GENERIC, with the goal of shipping 8.0 with MAC support in the default kernel. No policies will be compiled in or enabled by default, but it will now be possible to load them at boot or runtime without a kernel recompile. While the framework is not believed to impose measurable overhead when no policies are loaded (a result of optimization over the past few months in HEAD), we'll continue to benchmark and optimize as the release approaches. Please keep an eye out for performance or functionality regressions that could be a result of this change. Approved by: re (kensmith) Obtained from: TrustedBSD Project
2009-06-02 18:31:08 +00:00
options MAC # TrustedBSD MAC Framework
Add INCLUDE_CONFIG_FILE in GENERIC on all non-embedded platforms. # This is the resolution of removing it from DEFAULTS... MFC after: 5 days
2010-01-10 17:44:22 +00:00
options INCLUDE_CONFIG_FILE # Include this file in kernel
Add a GENERIC kernel config for sparc64.
2001-08-14 03:27:02 +00:00
Match the style of very other platform we have.
2001-09-02 23:37:45 +00:00
# Debugging for use in -current
- Sync whitespace and comments with i386 GENERIC. - Add some commented out NICs from i386 GENERIC. Most of them look like they would work but I'm not sure if they are endian-clean and can't test. There was a report that sk(4) works on sparc64 but it doesn't look like it would because it doesn't use busdma. - Improve some of the descriptions of sparc64 specific devices. There's no functional change, i.e. no added or deleted uncommented devices or options, in this commit.
2004-08-16 23:23:21 +00:00
options KDB # Enable kernel debugger support.
options DDB # Support DDB.
options GDB # Support remote GDB.
Add the options DEADLKRES (introducing the deadlock resolver thread) in the 'debugging' section of any HEAD kernel and enable for the mainstream ones, excluding the embedded architectures. It may, of course, enabled on a case-by-case basis. Sponsored by: Sandvine Incorporated Requested by: emaste Discussed with: kib
2010-02-10 16:30:04 +00:00
options DEADLKRES # Enable the deadlock resolver
- Sync whitespace and comments with i386 GENERIC. - Add some commented out NICs from i386 GENERIC. Most of them look like they would work but I'm not sure if they are endian-clean and can't test. There was a report that sk(4) works on sparc64 but it doesn't look like it would because it doesn't use busdma. - Improve some of the descriptions of sparc64 specific devices. There's no functional change, i.e. no added or deleted uncommented devices or options, in this commit.
2004-08-16 23:23:21 +00:00
options INVARIANTS # Enable calls of extra sanity checking
options INVARIANT_SUPPORT # Extra sanity checks of internal structures, required by INVARIANTS
options WITNESS # Enable checks to detect deadlocks and cycles
options WITNESS_SKIPSPIN # Don't run witness on spinlocks for speed
Sync with the Alpha's GENERIC configuration. Most of the contents are commented out as they are as-yet untested. However, I wanted the contents to match our other arches, so that when people make changes to {i386,alpha,ia64}, they will also make the same changes here.
2002-02-24 18:49:38 +00:00
o merge from amd64: - r187144: Add a reference to the config(5) manpage and to the "env" kernel config option. - Add/enable the default USB drivers. Originally the USB controller and keyboard drivers were disabled as these interacted badly with the Open Firmware console driver, i.e. caused the keyboard to not work with ofw_console(4). Even when switch to uart(4) and the frame buffer drivers most of the USB drivers still were kept disabled as several of them, amongst others all of the drivers for USB Ethernet controllers, weren't endian clean. With the new USB stack these problem should be gone now so there's no longer a reason to not include the same set of USB drivers amd64 does. o Remove the commented out device ofw_console; apart from it being currently broken by some TTY changes one really needs to know how to actually enable and make it work correctly.
2009-06-24 20:49:02 +00:00
# Make an SMP-capable kernel by default
Minor sync to alpha and i386: - Add ADAPTIVE_GIANT and AHC_REG_PRETTY_PRINT. - Indent SMP to match other options.
2004-12-30 18:31:53 +00:00
options SMP # Symmetric MultiProcessor Kernel
Sync with the Alpha's GENERIC configuration. Most of the contents are commented out as they are as-yet untested. However, I wanted the contents to match our other arches, so that when people make changes to {i386,alpha,ia64}, they will also make the same changes here.
2002-02-24 18:49:38 +00:00
# Standard busses
I was able to boot this kernel using the latest WIP kernel sources. I don't believe anyone is quite using the sparc64 kernel sources in CVS yet -- things aren't just quite ready (but almost). So this commit should be OK to make.
2002-02-25 22:13:44 +00:00
device ebus
device isa
de-count pci
2002-07-23 06:38:47 +00:00
device pci
I was able to boot this kernel using the latest WIP kernel sources. I don't believe anyone is quite using the sparc64 kernel sources in CVS yet -- things aren't just quite ready (but almost). So this commit should be OK to make.
2002-02-25 22:13:44 +00:00
device sbus
Add central and fhc.
2003-02-18 09:38:51 +00:00
device central
device fhc
Sync with the Alpha's GENERIC configuration. Most of the contents are commented out as they are as-yet untested. However, I wanted the contents to match our other arches, so that when people make changes to {i386,alpha,ia64}, they will also make the same changes here.
2002-02-24 18:49:38 +00:00
# Floppy drives
#device fdc
# ATA and ATAPI devices
I was able to boot this kernel using the latest WIP kernel sources. I don't believe anyone is quite using the sparc64 kernel sources in CVS yet -- things aren't just quite ready (but almost). So this commit should be OK to make.
2002-02-25 22:13:44 +00:00
device ata
- Sync whitespace and comments with i386 GENERIC. - Add some commented out NICs from i386 GENERIC. Most of them look like they would work but I'm not sure if they are endian-clean and can't test. There was a report that sk(4) works on sparc64 but it doesn't look like it would because it doesn't use busdma. - Improve some of the descriptions of sparc64 specific devices. There's no functional change, i.e. no added or deleted uncommented devices or options, in this commit.
2004-08-16 23:23:21 +00:00
device atadisk # ATA disk drives
device atapicd # ATAPI CDROM drives
#device atapifd # ATAPI floppy drives
#device atapist # ATAPI tape drives
Do NOT enable ATA_STATIC_ID -- cmd646 controller will be !ata2!, and you will not mount an ATA /: mountroot> ufs:/ad0a Mounting root from ufs:/ad0a setrootbyname failed ffs_mountroot: can't find rootvp
2002-06-29 04:42:03 +00:00
# Do NOT enable ATA_STATIC_ID -- cmd646 controller will be !ata2!,
# and you will not mount an ATA /.
- Sync whitespace and comments with i386 GENERIC. - Add some commented out NICs from i386 GENERIC. Most of them look like they would work but I'm not sure if they are endian-clean and can't test. There was a report that sk(4) works on sparc64 but it doesn't look like it would because it doesn't use busdma. - Improve some of the descriptions of sparc64 specific devices. There's no functional change, i.e. no added or deleted uncommented devices or options, in this commit.
2004-08-16 23:23:21 +00:00
#options ATA_STATIC_ID # Static device numbering
Sync with the Alpha's GENERIC configuration. Most of the contents are commented out as they are as-yet untested. However, I wanted the contents to match our other arches, so that when people make changes to {i386,alpha,ia64}, they will also make the same changes here.
2002-02-24 18:49:38 +00:00
# SCSI Controllers
I was able to boot this kernel using the latest WIP kernel sources. I don't believe anyone is quite using the sparc64 kernel sources in CVS yet -- things aren't just quite ready (but almost). So this commit should be OK to make.
2002-02-25 22:13:44 +00:00
device ahc # AHA2940 and onboard AIC7xxx devices
ahc(4) work better in Sparc64 with AHC_ALLOW_MEMIO. Submitted by: Nathan Whitehorn <nwhitehorn@freebsd.org>
2008-09-02 21:46:17 +00:00
options AHC_ALLOW_MEMIO # Attempt to use memory mapped I/O
Move AHC_REG_PRETTY_PRINT and AHD_REG_PRETTY_PRINT below their corresponding devices.
2006-04-24 08:44:34 +00:00
options AHC_REG_PRETTY_PRINT # Print register bitfields in debug
# output. Adds ~128k to driver.
Enable isp and ispfw. Remove the nonexistant SUN_DISKLABEL and ATA_ENABLE_BUSMATER.
2002-04-06 09:33:24 +00:00
device isp # Qlogic family
device ispfw # Firmware module for Qlogic host adapters
Enable mpt(4) as some later models have on-board Fusion-MPT controllers and it seems to work just fine with at least an add-on SAS3080X. While at it, remove the commented out ncr(4) as it doesn't even use bus_dma(9), which isn't worth fixing though as sym(4) already supports a superset of the controllers driven by ncr(4).
2008-10-11 12:10:23 +00:00
device mpt # LSI-Logic MPT-Fusion
device sym # NCR/Symbios/LSI Logic 53C8XX/53C1010/53C1510D
Add esp to the sparc64 GENERIC
2004-06-10 05:24:34 +00:00
device esp # NCR53c9x (FEPS/FAS366)
Sync with the Alpha's GENERIC configuration. Most of the contents are commented out as they are as-yet untested. However, I wanted the contents to match our other arches, so that when people make changes to {i386,alpha,ia64}, they will also make the same changes here.
2002-02-24 18:49:38 +00:00
# SCSI peripherals
Note that scbus is required for SCSI, not just "required" in general. Submitted by: Edward Kaplan (tmbg37 on IRC) Reviewed by: rwatson (in principle)
2003-06-08 02:03:02 +00:00
device scbus # SCSI bus (required for SCSI)
SCSI Changers, SCSI Tapes, and SES devices work just about as well as anything else in sparc64.
2003-01-31 19:03:32 +00:00
device ch # SCSI media changers
I was able to boot this kernel using the latest WIP kernel sources. I don't believe anyone is quite using the sparc64 kernel sources in CVS yet -- things aren't just quite ready (but almost). So this commit should be OK to make.
2002-02-25 22:13:44 +00:00
device da # Direct Access (disks)
SCSI Changers, SCSI Tapes, and SES devices work just about as well as anything else in sparc64.
2003-01-31 19:03:32 +00:00
device sa # Sequential Access (tape etc)
Sync with other arches; add bloat.
2002-03-23 16:55:37 +00:00
device cd # CD
Enable device pass.
2002-04-08 23:21:31 +00:00
device pass # Passthrough device (direct SCSI access)
SCSI Changers, SCSI Tapes, and SES devices work just about as well as anything else in sparc64.
2003-01-31 19:03:32 +00:00
device ses # SCSI Environmental Services (and SAF-TE)
Sync with the Alpha's GENERIC configuration. Most of the contents are commented out as they are as-yet untested. However, I wanted the contents to match our other arches, so that when people make changes to {i386,alpha,ia64}, they will also make the same changes here.
2002-02-24 18:49:38 +00:00
# RAID controllers
#device amr # AMI MegaRAID
#device mlx # Mylex DAC960 family
- Hook up atkbdc(4), atkbd(4) and psm(4) to the sparc64 build, not enabled in GENERIC by default, yet. - While here remove the exclusion of ukbd(4) from the sparc64 NOTES as ukbd(4) compiles and works on sparc64.
2005-06-10 20:58:59 +00:00
# atkbdc0 controls both the keyboard and the PS/2 mouse
Turn on atkbdc(4), atkbd(4), creator(4), machfb(4), syscons(4), ohci(4), psm(4), ukbd(4), ums(4) and usb(4) on by default. Modulo some nits with the most annoying one probably being USB keyboards no longer working at the OFW boot prompt after halting FreeBSD these drivers work fine on sparc64 including X and there's nothing left that I'd consider a show- stopper. I.e. graphical consoles on sun4u machines should either work out of the box or by plugging in a card that is supported by either creator(4) or machfb(4). The exception obviously are SBus-only machines without UPA slots like some Ultra 1 (but which also still lack support in other areas) and certain Exx0 (but which probably are mainly used with serial consoles anyway). I'll try to add a cgsix(4) for these later as Sun CG6 cards are probably the most common SBus framebuffer cards in sun4u machines. I however don't see much sense in adding drivers for the dozen of SBus framebuffers that were destined for sparc v8 machines. The rest of the USB drivers aren't enabled as I'm only aware of ukbd(4) and ums(4) as well as ohci(4) working with the on-board ALI M5237 and Sun PCIO-2 controllers. Aue(4) definitely doesn't work on sparc64, yet. Thanks to: - Jake for the initial work on syscons(4) on sparc64 and creator(4). - Marcel for uart(4) and especially for its support for the SCCs which are only used on sparc64 so far. In various regards it wouldn't have been possible to enable syscons(4) by default on sparc64, yet, without uart(4). - All that tested patches. Ok'ed by: scottl (RE hat), tmm
2005-06-10 23:11:16 +00:00
device atkbdc # AT keyboard controller
device atkbd # AT keyboard
device psm # PS/2 mouse
+ Blah, there was nothing wrong in rev 1.1 talking about the i386/NOTES. I should have diff'ed the header with the Alpha GENERIC. + fix style nit + turn on NO_MODULES for now.
2001-09-02 23:48:37 +00:00
- Add kbdmux(4); since sunkbd(4) was tought to emulate atkbd(4) like ukbd(4) does and that emulation was enabled by default, all three of them work together with kbdmux(4) out of the box just fine. - Fix some whitespace bugs. MFC after: 3 days
2008-08-23 14:17:00 +00:00
device kbdmux # keyboard multiplexer
Sync with the Alpha's GENERIC configuration. Most of the contents are commented out as they are as-yet untested. However, I wanted the contents to match our other arches, so that when people make changes to {i386,alpha,ia64}, they will also make the same changes here.
2002-02-24 18:49:38 +00:00
# syscons is the default console driver, resembling an SCO console
Turn on atkbdc(4), atkbd(4), creator(4), machfb(4), syscons(4), ohci(4), psm(4), ukbd(4), ums(4) and usb(4) on by default. Modulo some nits with the most annoying one probably being USB keyboards no longer working at the OFW boot prompt after halting FreeBSD these drivers work fine on sparc64 including X and there's nothing left that I'd consider a show- stopper. I.e. graphical consoles on sun4u machines should either work out of the box or by plugging in a card that is supported by either creator(4) or machfb(4). The exception obviously are SBus-only machines without UPA slots like some Ultra 1 (but which also still lack support in other areas) and certain Exx0 (but which probably are mainly used with serial consoles anyway). I'll try to add a cgsix(4) for these later as Sun CG6 cards are probably the most common SBus framebuffer cards in sun4u machines. I however don't see much sense in adding drivers for the dozen of SBus framebuffers that were destined for sparc v8 machines. The rest of the USB drivers aren't enabled as I'm only aware of ukbd(4) and ums(4) as well as ohci(4) working with the on-board ALI M5237 and Sun PCIO-2 controllers. Aue(4) definitely doesn't work on sparc64, yet. Thanks to: - Jake for the initial work on syscons(4) on sparc64 and creator(4). - Marcel for uart(4) and especially for its support for the SCCs which are only used on sparc64 so far. In various regards it wouldn't have been possible to enable syscons(4) by default on sparc64, yet, without uart(4). - All that tested patches. Ok'ed by: scottl (RE hat), tmm
2005-06-10 23:11:16 +00:00
device sc
device creator # Creator, Creator3D and Elite3D framebuffers
device machfb # ATI Mach64 framebuffers
Now that at least some screen savers work on sparc64 sync with other archs and enable splash(4) by default (the non-working screen savers either don't compile or just have no effect when loaded, i.e. don't cause harm). MFC after: 1 week
2005-08-15 21:15:07 +00:00
device splash # Splash screen and screen saver support
Turn on atkbdc(4), atkbd(4), creator(4), machfb(4), syscons(4), ohci(4), psm(4), ukbd(4), ums(4) and usb(4) on by default. Modulo some nits with the most annoying one probably being USB keyboards no longer working at the OFW boot prompt after halting FreeBSD these drivers work fine on sparc64 including X and there's nothing left that I'd consider a show- stopper. I.e. graphical consoles on sun4u machines should either work out of the box or by plugging in a card that is supported by either creator(4) or machfb(4). The exception obviously are SBus-only machines without UPA slots like some Ultra 1 (but which also still lack support in other areas) and certain Exx0 (but which probably are mainly used with serial consoles anyway). I'll try to add a cgsix(4) for these later as Sun CG6 cards are probably the most common SBus framebuffer cards in sun4u machines. I however don't see much sense in adding drivers for the dozen of SBus framebuffers that were destined for sparc v8 machines. The rest of the USB drivers aren't enabled as I'm only aware of ukbd(4) and ums(4) as well as ohci(4) working with the on-board ALI M5237 and Sun PCIO-2 controllers. Aue(4) definitely doesn't work on sparc64, yet. Thanks to: - Jake for the initial work on syscons(4) on sparc64 and creator(4). - Marcel for uart(4) and especially for its support for the SCCs which are only used on sparc64 so far. In various regards it wouldn't have been possible to enable syscons(4) by default on sparc64, yet, without uart(4). - All that tested patches. Ok'ed by: scottl (RE hat), tmm
2005-06-10 23:11:16 +00:00
options KBD_INSTALL_CDEV # install a CDEV entry in /dev
Sync with the Alpha's GENERIC configuration. Most of the contents are commented out as they are as-yet untested. However, I wanted the contents to match our other arches, so that when people make changes to {i386,alpha,ia64}, they will also make the same changes here.
2002-02-24 18:49:38 +00:00
I was able to boot this kernel using the latest WIP kernel sources. I don't believe anyone is quite using the sparc64 kernel sources in CVS yet -- things aren't just quite ready (but almost). So this commit should be OK to make.
2002-02-25 22:13:44 +00:00
# Builtin hardware
Port NetBSD auxio driver. The driver was modified to use led(4) and can be used to announce various system activity. The auxio device provides auxiliary I/O functions and is found on various SBus/EBus UltraSPARC models. At present, only front panel LED is controlled by this driver. Approved by: jake (mentor) Reviewed by: joerg Tested by: joerg
2004-10-09 07:31:03 +00:00
device auxio # auxiliary I/O device
- Sync whitespace and comments with i386 GENERIC. - Add some commented out NICs from i386 GENERIC. Most of them look like they would work but I'm not sure if they are endian-clean and can't test. There was a report that sk(4) works on sparc64 but it doesn't look like it would because it doesn't use busdma. - Improve some of the descriptions of sparc64 specific devices. There's no functional change, i.e. no added or deleted uncommented devices or options, in this commit.
2004-08-16 23:23:21 +00:00
device eeprom # eeprom (really a front-end for the MK48Txx)
Shorten the description of the mk48txx driver to just say that it supports MK48Txx clocks, there are now to many models supported to list them all here.
2004-11-17 12:57:24 +00:00
device mk48txx # Mostek MK48Txx clocks
Add a front-end for the `rtc' device which is a MC146818 compatible clock found on the ISA bus (some USIIe, USIIi and USIIIi models) and EBus (USIII models) instead of a MK48Txx clock. Testet by: Matthew T. Lager" <freebsd@trinetworks.com> on Sun Fire V100, Xavier Beaudouin <kiwi@oav.net> on Netra X1 (initial version)
2004-11-17 16:41:42 +00:00
device rtc # rtc (really a front-end for the MC146818)
device mc146818 # Motorola MC146818 and compatible clocks
Add epic(4), a driver for the front panel LEDs in Sun Fire V215/V245. It's named after the driver doing the same job in OpenSolaris.
2010-01-10 15:44:48 +00:00
device epic # Sun Fire V215/V245 LEDs
Add sbbc(4), a driver for the BootBus controller found in Serengeti and StarCat systems which provides time-of-day services for both as well as console service for Serengeti, i.e. Sun Fire V1280. While the latter is described with a device type of serial in the OFW device tree, it isn't actually an UART. Nevertheless the console service is handled by uart(4) as this allowed to re-use quite a bit of MD and MI code. Actually, this idea is stolen from Linux which interfaces the sun4v hypervisor console with the Linux counterpart of uart(4).
2010-04-10 11:52:12 +00:00
device sbbc # Sun BootBus controller (time-of-day clock for
# Serengeti and StarCat, console for Serengeti,
# requires device uart)
I was able to boot this kernel using the latest WIP kernel sources. I don't believe anyone is quite using the sparc64 kernel sources in CVS yet -- things aren't just quite ready (but almost). So this commit should be OK to make.
2002-02-25 22:13:44 +00:00
Sync with the Alpha's GENERIC configuration. Most of the contents are commented out as they are as-yet untested. However, I wanted the contents to match our other arches, so that when people make changes to {i386,alpha,ia64}, they will also make the same changes here.
2002-02-24 18:49:38 +00:00
# Serial (COM) ports
o Enable puc(4) and uart(4). o Disable ofw_console(4), sab(4) and zs(4). sab(4) and zs(4) are disabled because the hardware controlled by them is handled by uart(4)+puc(4) and the latter combination is functionally complete and up to date. ofw_console(4) is disabled because it doesn't claim the device it controls (through OFW) and thus interferes with puc(4)+uart(4), which has sufficient knowledge to extract the necessary information from OFW to setup the console. Put differently, ofw_console(4) is not a proper device driver and can only do harm. Its functionality is completely handled by uart(4). This commit makes uart(4) the default driver for serial ports. MFC after: 2 weeks
2005-01-30 09:27:49 +00:00
device puc # Multi-channel uarts
Add scc(4).
2006-03-30 18:40:25 +00:00
device scc # Serial communications controllers.
device uart # Multi-uart driver
Sync with the Alpha's GENERIC configuration. Most of the contents are commented out as they are as-yet untested. However, I wanted the contents to match our other arches, so that when people make changes to {i386,alpha,ia64}, they will also make the same changes here.
2002-02-24 18:49:38 +00:00
Various comment and minor style fixes. No actual content changes. Inspired by: bde
2002-07-16 18:20:17 +00:00
# Parallel port
Sync with the Alpha's GENERIC configuration. Most of the contents are commented out as they are as-yet untested. However, I wanted the contents to match our other arches, so that when people make changes to {i386,alpha,ia64}, they will also make the same changes here.
2002-02-24 18:49:38 +00:00
#device ppc
#device ppbus # Parallel port bus (required)
#device lpt # Printer
#device plip # TCP/IP over parallel
#device ppi # Parallel port interface device
#device vpo # Requires scbus and da
- Add kbdmux(4); since sunkbd(4) was tought to emulate atkbd(4) like ukbd(4) does and that emulation was enabled by default, all three of them work together with kbdmux(4) out of the box just fine. - Fix some whitespace bugs. MFC after: 3 days
2008-08-23 14:17:00 +00:00
Sync with the Alpha's GENERIC configuration. Most of the contents are commented out as they are as-yet untested. However, I wanted the contents to match our other arches, so that when people make changes to {i386,alpha,ia64}, they will also make the same changes here.
2002-02-24 18:49:38 +00:00
# PCI Ethernet NICs.
#device de # DEC/Intel DC21x4x (``Tulip'')
Uncomment em(4) as it's now working.
2005-11-09 08:49:46 +00:00
device em # Intel PRO/1000 adapter Gigabit Ethernet Card
- Sync whitespace and comments with i386 GENERIC. - Add some commented out NICs from i386 GENERIC. Most of them look like they would work but I'm not sure if they are endian-clean and can't test. There was a report that sk(4) works on sparc64 but it doesn't look like it would because it doesn't use busdma. - Improve some of the descriptions of sparc64 specific devices. There's no functional change, i.e. no added or deleted uncommented devices or options, in this commit.
2004-08-16 23:23:21 +00:00
#device ixgb # Intel PRO/10GbE Ethernet Card
Hook up le(4) to the build. For now it's only added to the sparc64 GENERIC in order to support the on-board LANCE in Ultra 1 and to the MI NOTES as it should work just fine with the AMD PCnet family of chips on all archs but is not yet meant to replace lnc(4). If a kernel includes all of le(4), lnc(4) and pcn(4) precedence is given to lnc(4)/pcn(4) for now.
2006-01-31 22:34:13 +00:00
device le # AMD Am7900 LANCE and Am79C9xx PCnet
Resort the if_ti driver to match the PCI Network cards instead of placing it under the mii devices list. PR: kern/123147 Submitted by: gavin Approved by: imp (mentor, implicit) MFC after: 3 days
2008-05-17 23:50:00 +00:00
device ti # Alteon Networks Tigon I/II gigabit Ethernet
Uncomment txp(4), txp(4) should work on all architectures.
2009-03-12 01:17:35 +00:00
device txp # 3Com 3cR990 (``Typhoon'')
Sync with the Alpha's GENERIC configuration. Most of the contents are commented out as they are as-yet untested. However, I wanted the contents to match our other arches, so that when people make changes to {i386,alpha,ia64}, they will also make the same changes here.
2002-02-24 18:49:38 +00:00
#device vx # 3Com 3c590, 3c595 (``Vortex'')
# PCI Ethernet NICs that use the common MII bus controller code.
- Sync whitespace and comments with i386 GENERIC. - Add some commented out NICs from i386 GENERIC. Most of them look like they would work but I'm not sure if they are endian-clean and can't test. There was a report that sk(4) works on sparc64 but it doesn't look like it would because it doesn't use busdma. - Improve some of the descriptions of sparc64 specific devices. There's no functional change, i.e. no added or deleted uncommented devices or options, in this commit.
2004-08-16 23:23:21 +00:00
# NOTE: Be sure to keep the 'device miibus' line in order to use these NICs!
I was able to boot this kernel using the latest WIP kernel sources. I don't believe anyone is quite using the sparc64 kernel sources in CVS yet -- things aren't just quite ready (but almost). So this commit should be OK to make.
2002-02-25 22:13:44 +00:00
device miibus # MII bus support
- Sync whitespace and comments with i386 GENERIC. - Add some commented out NICs from i386 GENERIC. Most of them look like they would work but I'm not sure if they are endian-clean and can't test. There was a report that sk(4) works on sparc64 but it doesn't look like it would because it doesn't use busdma. - Improve some of the descriptions of sparc64 specific devices. There's no functional change, i.e. no added or deleted uncommented devices or options, in this commit.
2004-08-16 23:23:21 +00:00
#device bfe # Broadcom BCM440x 10/100 Ethernet
Uncomment bge(4) as it's now working.
2005-12-22 01:46:28 +00:00
device bge # Broadcom BCM570xx Gigabit Ethernet
Add cas(4), a driver for Sun Cassini/Cassini+ and National Semiconductor DP83065 Saturn Gigabit Ethernet controllers. These are the successors of the Sun GEM controllers and still have a similar but extended transmit logic. As such this driver is based on gem(4). Thanks to marcel@ for providing a Sun Quad GigaSwift Ethernet UTP (QGE) card which was vital for getting this driver to work on architectures not using Open Firmware. Approved by: re (kib) MFC after: 2 weeks
2009-06-15 18:22:41 +00:00
device cas # Sun Cassini/Cassini+ and NS DP83065 Saturn
- Sync whitespace and comments with i386 GENERIC. - Add some commented out NICs from i386 GENERIC. Most of them look like they would work but I'm not sure if they are endian-clean and can't test. There was a report that sk(4) works on sparc64 but it doesn't look like it would because it doesn't use busdma. - Improve some of the descriptions of sparc64 specific devices. There's no functional change, i.e. no added or deleted uncommented devices or options, in this commit.
2004-08-16 23:23:21 +00:00
device dc # DEC/Intel 21143 and various workalikes
The fxp(4) driver is now working on sparc64 too! Tested by: jake
2003-04-08 20:55:30 +00:00
device fxp # Intel EtherExpress PRO/100B (82557, 82558)
It's Apple GMAC, not HMAC. Approved by: jake (for sparc64)
2002-09-22 01:18:06 +00:00
device gem # Sun GEM/Sun ERI/Apple GMAC
I was able to boot this kernel using the latest WIP kernel sources. I don't believe anyone is quite using the sparc64 kernel sources in CVS yet -- things aren't just quite ready (but almost). So this commit should be OK to make.
2002-02-25 22:13:44 +00:00
device hme # Sun HME (Happy Meal Ethernet)
Add nge(4), nge(4) should work on all architectures.
2009-05-21 02:19:01 +00:00
device nge # NatSemi DP83820 gigabit Ethernet
Hook up le(4) to the build. For now it's only added to the sparc64 GENERIC in order to support the on-board LANCE in Ultra 1 and to the MI NOTES as it should work just fine with the AMD PCnet family of chips on all archs but is not yet meant to replace lnc(4). If a kernel includes all of le(4), lnc(4) and pcn(4) precedence is given to lnc(4)/pcn(4) for now.
2006-01-31 22:34:13 +00:00
#device pcn # AMD Am79C97x PCI 10/100 (precedence over 'le')
Take the support for the 8139C+/8169/8169S/8110S chips out of the rl(4) driver and put it in a new re(4) driver. The re(4) driver shares the if_rlreg.h file with rl(4) but is a separate module. (Ultimately I may change this. For now, it's convenient.) rl(4) has been modified so that it will never attach to an 8139C+ chip, leaving it to re(4) instead. Only re(4) has the PCI IDs to match the 8169/8169S/8110S gigE chips. if_re.c contains the same basic code that was originally bolted onto if_rl.c, with the following updates: - Added support for jumbo frames. Currently, there seems to be a limit of approximately 6200 bytes for jumbo frames on transmit. (This was determined via experimentation.) The 8169S/8110S chips apparently are limited to 7.5K frames on transmit. This may require some more work, though the framework to handle jumbo frames on RX is in place: the re_rxeof() routine will gather up frames than span multiple 2K clusters into a single mbuf list. - Fixed bug in re_txeof(): if we reap some of the TX buffers, but there are still some pending, re-arm the timer before exiting re_txeof() so that another timeout interrupt will be generated, just in case re_start() doesn't do it for us. - Handle the 'link state changed' interrupt - Fix a detach bug. If re(4) is loaded as a module, and you do tcpdump -i re0, then you do 'kldunload if_re,' the system will panic after a few seconds. This happens because ether_ifdetach() ends up calling the BPF detach code, which notices the interface is in promiscuous mode and tries to switch promisc mode off while detaching the BPF listner. This ultimately results in a call to re_ioctl() (due to SIOCSIFFLAGS), which in turn calls re_init() to handle the IFF_PROMISC flag change. Unfortunately, calling re_init() here turns the chip back on and restarts the 1-second timeout loop that drives re_tick(). By the time the timeout fires, if_re.ko has been unloaded, which results in a call to invalid code and blows up the system. To fix this, I cleared the IFF_UP flag before calling ether_ifdetach(), which stops the ioctl routine from trying to reset the chip. - Modified comments in re_rxeof() relating to the difference in RX descriptor status bit layout between the 8139C+ and the gigE chips. The layout is different because the frame length field was expanded from 12 bits to 13, and they got rid of one of the status bits to make room. - Add diagnostic code (re_diag()) to test for the case where a user has installed a broken 32-bit 8169 PCI NIC in a 64-bit slot. Some NICs have the REQ64# and ACK64# lines connected even though the board is 32-bit only (in this case, they should be pulled high). This fools the chip into doing 64-bit DMA transfers even though there is no 64-bit data path. To detect this, re_diag() puts the chip into digital loopback mode and sets the receiver to promiscuous mode, then initiates a single 64-byte packet transmission. The frame is echoed back to the host, and if the frame contents are intact, we know DMA is working correctly, otherwise we complain loudly on the console and abort the device attach. (At the moment, I don't know of any way to work around the problem other than physically modifying the board, so until/unless I can think of a software workaround, this will have do to.) - Created re(4) man page - Modified rlphy.c to allow re(4) to attach as well as rl(4). Note that this code works for the sample 8169/Marvell 88E1000 NIC that I have, but probably won't work for the 8169S/8110S chips. RealTek has sent me some sample NICs, but they haven't arrived yet. I will probably need to add an rlgphy driver to handle the on-board PHY in the 8169S/8110S (it needs special DSP initialization).
2003-09-08 02:11:25 +00:00
device re # RealTek 8139C+/8169/8169S/8110S
Enable rl(4). It is now fully working using busdma.
2003-01-13 04:06:38 +00:00
device rl # RealTek 8129/8139
Uncomment sf(4), sf(4) should work on all architectures.
2008-01-21 06:51:25 +00:00
device sf # Adaptec AIC-6915 (``Starfire'')
Sync with the Alpha's GENERIC configuration. Most of the contents are commented out as they are as-yet untested. However, I wanted the contents to match our other arches, so that when people make changes to {i386,alpha,ia64}, they will also make the same changes here.
2002-02-24 18:49:38 +00:00
#device sis # Silicon Integrated Systems SiS 900/SiS 7016
Uncomment sk(4) as it's now working.
2006-04-27 06:03:17 +00:00
device sk # SysKonnect SK-984x & SK-982x gigabit Ethernet
Enable ste(4). ste(4) should work on all architectures.
2010-01-08 02:46:34 +00:00
device ste # Sundance ST201 (D-Link DFE-550TX)
Add stge(4) to the list of drivers supported by GENERIC kernel.
2006-07-25 01:06:32 +00:00
device stge # Sundance/Tamarack TC9021 gigabit Ethernet
Sync with the Alpha's GENERIC configuration. Most of the contents are commented out as they are as-yet untested. However, I wanted the contents to match our other arches, so that when people make changes to {i386,alpha,ia64}, they will also make the same changes here.
2002-02-24 18:49:38 +00:00
#device tl # Texas Instruments ThunderLAN
- Sync whitespace and comments with i386 GENERIC. - Add some commented out NICs from i386 GENERIC. Most of them look like they would work but I'm not sure if they are endian-clean and can't test. There was a report that sk(4) works on sparc64 but it doesn't look like it would because it doesn't use busdma. - Improve some of the descriptions of sparc64 specific devices. There's no functional change, i.e. no added or deleted uncommented devices or options, in this commit.
2004-08-16 23:23:21 +00:00
#device tx # SMC EtherPower II (83c170 ``EPIC'')
Uncomment vr(4), vr(4) should work on all architectures.
2008-03-11 05:09:03 +00:00
device vr # VIA Rhine, Rhine II
Sync with the Alpha's GENERIC configuration. Most of the contents are commented out as they are as-yet untested. However, I wanted the contents to match our other arches, so that when people make changes to {i386,alpha,ia64}, they will also make the same changes here.
2002-02-24 18:49:38 +00:00
#device wb # Winbond W89C840F
Uncomment the xl(4) driver since it's now working properly on sparc64.
2003-02-20 17:08:42 +00:00
device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'')
Sync with the Alpha's GENERIC configuration. Most of the contents are commented out as they are as-yet untested. However, I wanted the contents to match our other arches, so that when people make changes to {i386,alpha,ia64}, they will also make the same changes here.
2002-02-24 18:49:38 +00:00
add ath & co. MFC after: 1 month
2006-06-07 18:10:28 +00:00
# Wireless NIC cards
device wlan # 802.11 support
- Add kbdmux(4); since sunkbd(4) was tought to emulate atkbd(4) like ukbd(4) does and that emulation was enabled by default, all three of them work together with kbdmux(4) out of the box just fine. - Fix some whitespace bugs. MFC after: 3 days
2008-08-23 14:17:00 +00:00
options IEEE80211_DEBUG # enable debug msgs
options IEEE80211_AMPDU_AGE # age frames in AMPDU reorder q's
Implementation of the upcoming Wireless Mesh standard, 802.11s, on the net80211 wireless stack. This work is based on the March 2009 D3.0 draft standard. This standard is expected to become final next year. This includes two main net80211 modules, ieee80211_mesh.c which deals with peer link management, link metric calculation, routing table control and mesh configuration and ieee80211_hwmp.c which deals with the actually routing process on the mesh network. HWMP is the mandatory routing protocol on by the mesh standard, but others, such as RA-OLSR, can be implemented. Authentication and encryption are not implemented. There are several scripts under tools/tools/net80211/scripts that can be used to test different mesh network topologies and they also teach you how to setup a mesh vap (for the impatient: ifconfig wlan0 create wlandev ... wlanmode mesh). A new build option is available: IEEE80211_SUPPORT_MESH and it's enabled by default on GENERIC kernels for i386, amd64, sparc64 and pc98. Drivers that support mesh networks right now are: ath, ral and mwl. More information at: http://wiki.freebsd.org/WifiMesh Please note that this work is experimental. Also, please note that bridging a mesh vap with another network interface is not yet supported. Many thanks to the FreeBSD Foundation for sponsoring this project and to Sam Leffler for his support. Also, I would like to thank Gateworks Corporation for sending me a Cambria board which was used during the development of this project. Reviewed by: sam Approved by: re (kensmith) Obtained from: projects/mesh11s
2009-07-11 15:02:45 +00:00
options IEEE80211_SUPPORT_MESH # enable 802.11s D3.0 support
add ath & co. MFC after: 1 month
2006-06-07 18:10:28 +00:00
device wlan_wep # 802.11 WEP support
device wlan_ccmp # 802.11 CCMP support
device wlan_tkip # 802.11 TKIP support
o merge from amd64: - r187144: Add a reference to the config(5) manpage and to the "env" kernel config option. - Add/enable the default USB drivers. Originally the USB controller and keyboard drivers were disabled as these interacted badly with the Open Firmware console driver, i.e. caused the keyboard to not work with ofw_console(4). Even when switch to uart(4) and the frame buffer drivers most of the USB drivers still were kept disabled as several of them, amongst others all of the drivers for USB Ethernet controllers, weren't endian clean. With the new USB stack these problem should be gone now so there's no longer a reason to not include the same set of USB drivers amd64 does. o Remove the commented out device ofw_console; apart from it being currently broken by some TTY changes one really needs to know how to actually enable and make it work correctly.
2009-06-24 20:49:02 +00:00
device wlan_amrr # AMRR transmit rate control algorithm
add ath & co. MFC after: 1 month
2006-06-07 18:10:28 +00:00
device ath # Atheros pci/cardbus NIC's
device ath_hal # Atheros HAL (Hardware Access Layer)
- Use "device\t" and "options \t" for consistency.
2009-05-10 00:00:25 +00:00
options AH_SUPPORT_AR5416 # enable AR5416 tx/rx descriptors
add ath & co. MFC after: 1 month
2006-06-07 18:10:28 +00:00
device ath_rate_sample # SampleRate tx rate control for ath
In -CURRENT pseudo devices are not statically assigned at compile time, remove a stale comment. PR: kern/62285
2004-07-18 09:03:12 +00:00
# Pseudo devices.
I was able to boot this kernel using the latest WIP kernel sources. I don't believe anyone is quite using the sparc64 kernel sources in CVS yet -- things aren't just quite ready (but almost). So this commit should be OK to make.
2002-02-25 22:13:44 +00:00
device loop # Network loopback
Break out the MI part of the /dev/[k]mem and /dev/io drivers into their own directory and module, leaving the MD parts in the MD area (the MD parts _are_ part of the modules). /dev/mem and /dev/io are now loadable modules, thus taking us one step further towards a kernel created entirely out of modules. Of course, there is nothing preventing the kernel from having these statically compiled.
2004-08-01 11:40:54 +00:00
device random # Entropy device
I was able to boot this kernel using the latest WIP kernel sources. I don't believe anyone is quite using the sparc64 kernel sources in CVS yet -- things aren't just quite ready (but almost). So this commit should be OK to make.
2002-02-25 22:13:44 +00:00
device ether # Ethernet support
Add vlan(4) to all GENERIC kernels. MFC after: 1 week
2010-01-03 20:40:54 +00:00
device vlan # 802.1Q VLAN support
Sync with other arches; add bloat.
2002-03-23 16:55:37 +00:00
device tun # Packet tunnel.
Integrate the new MPSAFE TTY layer to the FreeBSD operating system. The last half year I've been working on a replacement TTY layer for the FreeBSD kernel. The new TTY layer was designed to improve the following: - Improved driver model: The old TTY layer has a driver model that is not abstract enough to make it friendly to use. A good example is the output path, where the device drivers directly access the output buffers. This means that an in-kernel PPP implementation must always convert network buffers into TTY buffers. If a PPP implementation would be built on top of the new TTY layer (still needs a hooks layer, though), it would allow the PPP implementation to directly hand the data to the TTY driver. - Improved hotplugging: With the old TTY layer, it isn't entirely safe to destroy TTY's from the system. This implementation has a two-step destructing design, where the driver first abandons the TTY. After all threads have left the TTY, the TTY layer calls a routine in the driver, which can be used to free resources (unit numbers, etc). The pts(4) driver also implements this feature, which means posix_openpt() will now return PTY's that are created on the fly. - Improved performance: One of the major improvements is the per-TTY mutex, which is expected to improve scalability when compared to the old Giant locking. Another change is the unbuffered copying to userspace, which is both used on TTY device nodes and PTY masters. Upgrading should be quite straightforward. Unlike previous versions, existing kernel configuration files do not need to be changed, except when they reference device drivers that are listed in UPDATING. Obtained from: //depot/projects/mpsafetty/... Approved by: philip (ex-mentor) Discussed: on the lists, at BSDCan, at the DevSummit Sponsored by: Snow B.V., the Netherlands dcons(4) fixed by: kan
2008-08-20 08:31:58 +00:00
device pty # BSD-style compatibility pseudo ttys
Sync with the Alpha's GENERIC configuration. Most of the contents are commented out as they are as-yet untested. However, I wanted the contents to match our other arches, so that when people make changes to {i386,alpha,ia64}, they will also make the same changes here.
2002-02-24 18:49:38 +00:00
device md # Memory "disks"
Sync with other arches; add bloat.
2002-03-23 16:55:37 +00:00
device gif # IPv6 and IPv4 tunneling
- Sync whitespace and comments with i386 GENERIC. - Add some commented out NICs from i386 GENERIC. Most of them look like they would work but I'm not sure if they are endian-clean and can't test. There was a report that sk(4) works on sparc64 but it doesn't look like it would because it doesn't use busdma. - Improve some of the descriptions of sparc64 specific devices. There's no functional change, i.e. no added or deleted uncommented devices or options, in this commit.
2004-08-16 23:23:21 +00:00
device faith # IPv6-to-IPv4 relaying (translation)
Make the firmware assist driver resident in preparation for isp using it.
2006-07-09 16:40:31 +00:00
device firmware # firmware assist module
Sync with the Alpha's GENERIC configuration. Most of the contents are commented out as they are as-yet untested. However, I wanted the contents to match our other arches, so that when people make changes to {i386,alpha,ia64}, they will also make the same changes here.
2002-02-24 18:49:38 +00:00
# The `bpf' device enables the Berkeley Packet Filter.
# Be aware of the administrative consequences of enabling this!
Add a comment to note that pseudo-device bpf is required for DHCP. This is mentioned in the Handbook but it is not as obvious to new users why bpf is needed compared to the other largely self-explanatory items in GENERIC. PR: conf/40855 MFC after: 1 week
2005-03-18 15:24:00 +00:00
# Note that 'bpf' is required for DHCP.
- Sync whitespace and comments with i386 GENERIC. - Add some commented out NICs from i386 GENERIC. Most of them look like they would work but I'm not sure if they are endian-clean and can't test. There was a report that sk(4) works on sparc64 but it doesn't look like it would because it doesn't use busdma. - Improve some of the descriptions of sparc64 specific devices. There's no functional change, i.e. no added or deleted uncommented devices or options, in this commit.
2004-08-16 23:23:21 +00:00
device bpf # Berkeley packet filter
Sync with the Alpha's GENERIC configuration. Most of the contents are commented out as they are as-yet untested. However, I wanted the contents to match our other arches, so that when people make changes to {i386,alpha,ia64}, they will also make the same changes here.
2002-02-24 18:49:38 +00:00
Change over the usb kernel options to the new stack (retaining existing naming). The old usb stack can be compiled in my prefixing the name with 'o'.
2009-02-23 18:34:56 +00:00
# USB support
o merge from amd64: - r187144: Add a reference to the config(5) manpage and to the "env" kernel config option. - Add/enable the default USB drivers. Originally the USB controller and keyboard drivers were disabled as these interacted badly with the Open Firmware console driver, i.e. caused the keyboard to not work with ofw_console(4). Even when switch to uart(4) and the frame buffer drivers most of the USB drivers still were kept disabled as several of them, amongst others all of the drivers for USB Ethernet controllers, weren't endian clean. With the new USB stack these problem should be gone now so there's no longer a reason to not include the same set of USB drivers amd64 does. o Remove the commented out device ofw_console; apart from it being currently broken by some TTY changes one really needs to know how to actually enable and make it work correctly.
2009-06-24 20:49:02 +00:00
device uhci # UHCI PCI->USB interface
Change over the usb kernel options to the new stack (retaining existing naming). The old usb stack can be compiled in my prefixing the name with 'o'.
2009-02-23 18:34:56 +00:00
device ohci # OHCI PCI->USB interface
o merge from amd64: - r187144: Add a reference to the config(5) manpage and to the "env" kernel config option. - Add/enable the default USB drivers. Originally the USB controller and keyboard drivers were disabled as these interacted badly with the Open Firmware console driver, i.e. caused the keyboard to not work with ofw_console(4). Even when switch to uart(4) and the frame buffer drivers most of the USB drivers still were kept disabled as several of them, amongst others all of the drivers for USB Ethernet controllers, weren't endian clean. With the new USB stack these problem should be gone now so there's no longer a reason to not include the same set of USB drivers amd64 does. o Remove the commented out device ofw_console; apart from it being currently broken by some TTY changes one really needs to know how to actually enable and make it work correctly.
2009-06-24 20:49:02 +00:00
device ehci # EHCI PCI->USB interface (USB 2.0)
Change over the usb kernel options to the new stack (retaining existing naming). The old usb stack can be compiled in my prefixing the name with 'o'.
2009-02-23 18:34:56 +00:00
device usb # USB Bus (required)
- Sync whitespace and comments with i386 GENERIC. - Add some commented out NICs from i386 GENERIC. Most of them look like they would work but I'm not sure if they are endian-clean and can't test. There was a report that sk(4) works on sparc64 but it doesn't look like it would because it doesn't use busdma. - Improve some of the descriptions of sparc64 specific devices. There's no functional change, i.e. no added or deleted uncommented devices or options, in this commit.
2004-08-16 23:23:21 +00:00
#device udbp # USB Double Bulk Pipe devices
o merge from amd64: - r187144: Add a reference to the config(5) manpage and to the "env" kernel config option. - Add/enable the default USB drivers. Originally the USB controller and keyboard drivers were disabled as these interacted badly with the Open Firmware console driver, i.e. caused the keyboard to not work with ofw_console(4). Even when switch to uart(4) and the frame buffer drivers most of the USB drivers still were kept disabled as several of them, amongst others all of the drivers for USB Ethernet controllers, weren't endian clean. With the new USB stack these problem should be gone now so there's no longer a reason to not include the same set of USB drivers amd64 does. o Remove the commented out device ofw_console; apart from it being currently broken by some TTY changes one really needs to know how to actually enable and make it work correctly.
2009-06-24 20:49:02 +00:00
device uhid # "Human Interface Devices"
Change over the usb kernel options to the new stack (retaining existing naming). The old usb stack can be compiled in my prefixing the name with 'o'.
2009-02-23 18:34:56 +00:00
device ukbd # Keyboard
o merge from amd64: - r187144: Add a reference to the config(5) manpage and to the "env" kernel config option. - Add/enable the default USB drivers. Originally the USB controller and keyboard drivers were disabled as these interacted badly with the Open Firmware console driver, i.e. caused the keyboard to not work with ofw_console(4). Even when switch to uart(4) and the frame buffer drivers most of the USB drivers still were kept disabled as several of them, amongst others all of the drivers for USB Ethernet controllers, weren't endian clean. With the new USB stack these problem should be gone now so there's no longer a reason to not include the same set of USB drivers amd64 does. o Remove the commented out device ofw_console; apart from it being currently broken by some TTY changes one really needs to know how to actually enable and make it work correctly.
2009-06-24 20:49:02 +00:00
device ulpt # Printer
device umass # Disks/Mass storage - Requires scbus and da
Change over the usb kernel options to the new stack (retaining existing naming). The old usb stack can be compiled in my prefixing the name with 'o'.
2009-02-23 18:34:56 +00:00
device ums # Mouse
o merge from amd64: - r187144: Add a reference to the config(5) manpage and to the "env" kernel config option. - Add/enable the default USB drivers. Originally the USB controller and keyboard drivers were disabled as these interacted badly with the Open Firmware console driver, i.e. caused the keyboard to not work with ofw_console(4). Even when switch to uart(4) and the frame buffer drivers most of the USB drivers still were kept disabled as several of them, amongst others all of the drivers for USB Ethernet controllers, weren't endian clean. With the new USB stack these problem should be gone now so there's no longer a reason to not include the same set of USB drivers amd64 does. o Remove the commented out device ofw_console; apart from it being currently broken by some TTY changes one really needs to know how to actually enable and make it work correctly.
2009-06-24 20:49:02 +00:00
device urio # Diamond Rio 500 MP3 player
# USB Serial devices
device uark # Technologies ARK3116 based serial adapters
device ubsa # Belkin F5U103 and compatible serial adapters
device uftdi # For FTDI usb serial adapters
device uipaq # Some WinCE based devices
device uplcom # Prolific PL-2303 serial adapters
device uslcom # SI Labs CP2101/CP2102 serial adapters
device uvisor # Visor and Palm devices
device uvscom # USB serial support for DDI pocket's PHS
# USB Ethernet, requires miibus
device aue # ADMtek USB Ethernet
device axe # ASIX Electronics USB Ethernet
device cdce # Generic USB over Ethernet
device cue # CATC USB Ethernet
device kue # Kawasaki LSI USB Ethernet
device rue # RealTek RTL8150 USB Ethernet
device udav # Davicom DM9601E USB
Move the USB wireless drivers down into their own section next to the USB ethernet drivers. Submitted by: Glen Barber glen.j.barber @ gmail MFC after: 1 month
2009-10-13 19:02:03 +00:00
# USB Wireless
device rum # Ralink Technology RT2501USB wireless NICs
device uath # Atheros AR5523 wireless NICs
device ural # Ralink Technology RT2500USB wireless NICs
device zyd # ZyDAS zb1211/zb1211b wireless NICs
Sync with the Alpha's GENERIC configuration. Most of the contents are commented out as they are as-yet untested. However, I wanted the contents to match our other arches, so that when people make changes to {i386,alpha,ia64}, they will also make the same changes here.
2002-02-24 18:49:38 +00:00
Add FireWire drivers to GENERIC.
2003-04-21 16:44:05 +00:00
# FireWire support
device firewire # FireWire bus code
device sbp # SCSI over FireWire (Requires scbus and da)
device fwe # Ethernet over FireWire (non-standard!)
Enable fwip and dcons in GENERIC. They seem fairly stable. Note on dcons: To enable dcons in kernel, put the following lines in /boot/loader.conf. You may also want to enable dcons in /etc/ttys. boot_multicons="YES" #Force dcons to be the high-level console if a firewire bus presents. #hw.firewire.dcons_crom.force_console=1 FireWire/dcons support in loader will come shortly. (i386/amd64 only)
2007-05-28 14:38:43 +00:00
device fwip # IP over FireWire (RFC 2734,3146)
device dcons # Dumb console driver
device dcons_crom # Configuration ROM for dcons
Reference in New Issue Copy Permalink