aboutsummaryrefslogtreecommitdiff
path: root/sys/sparc64/conf/DEFAULTS
Commit message (Collapse)AuthorAgeFilesLines
* Remove sparc64 kernel supportWarner Losh2020-02-031-23/+0
| | | | | | | | | Remove all sparc64 specific files Remove all sparc64 ifdefs Removee indireeect sparc64 ifdefs Notes: svn path=/head/; revision=357455
* Disable the option VFS_ALLOW_NONMPSAFE by default on all the supportedAttilio Rao2012-03-061-3/+0
| | | | | | | | | | | | | | | platforms. This will make every attempt to mount a non-mpsafe filesystem to the kernel forbidden, unless it is expressely compiled with VFS_ALLOW_NONMPSAFE option. This patch is part of the effort of killing non-MPSAFE filesystems from the tree. No MFC is expected for this patch. Notes: svn path=/head/; revision=232619
* Introduce the option VFS_ALLOW_NONMPSAFE and turn it on by default onAttilio Rao2011-11-081-0/+3
| | | | | | | | | | | | | | | | | all the architectures. The option allows to mount non-MPSAFE filesystem. Without it, the kernel will refuse to mount a non-MPSAFE filesytem. This patch is part of the effort of killing non-MPSAFE filesystems from the tree. No MFC is expected for this patch. Tested by: gianni Reviewed by: kib Notes: svn path=/head/; revision=227333
* Actually enable NEW_PCIB by default, missed in r225931.Marius Strobl2011-10-021-1/+1
| | | | Notes: svn path=/head/; revision=225932
* Make sparc64 compatible with NEW_PCIB and enable it:Marius Strobl2011-10-021-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - Implement bus_adjust_resource() methods as far as necessary and in non-PCI bridge drivers as far as feasible without rototilling them. - As NEW_PCIB does a layering violation by activating resources at layers above pci(4) without previously bubbling up their allocation there, move the assignment of bus tags and handles from the bus_alloc_resource() to the bus_activate_resource() methods like at least the other NEW_PCIB enabled architectures do. This is somewhat unfortunate as previously sparc64 (ab)used resource activation to indicate whether SYS_RES_MEMORY resources should be mapped into KVA, which is only necessary if their going to be accessed via the pointer returned from rman_get_virtual() but not for bus_space(9) as the later always uses physical access on sparc64. Besides wasting KVA if we always map in SYS_RES_MEMORY resources, a driver also may deliberately not map them in if the firmware already has done so, possibly in a special way. So in order to still allow a driver to decide whether a SYS_RES_MEMORY resource should be mapped into KVA we let it indicate that by calling bus_space_map(9) with BUS_SPACE_MAP_LINEAR as actually documented in the bus_space(9) page. This is implemented by allocating a separate bus tag per SYS_RES_MEMORY resource and passing the resource via the previously unused bus tag cookie so we later on can call rman_set_virtual() in sparc64_bus_mem_map(). As a side effect this now also allows to actually indicate that a SYS_RES_MEMORY resource should be mapped in as cacheable and/or read-only via BUS_SPACE_MAP_CACHEABLE and BUS_SPACE_MAP_READONLY respectively. - Do some minor cleanup like taking advantage of rman_init_from_resource(), factor out the common part of bus tag allocation into a newly added sparc64_alloc_bus_tag(), hook up some missing newbus methods and replace some homegrown versions with the generic counterparts etc. - While at it, let apb_attach() (which can't use the generic NEW_PCIB code as APB bridges just don't have the base and limit registers implemented) regarding the config space registers cached in pcib_softc and the SYSCTL reporting nodes set up. Notes: svn path=/head/; revision=225931
* Revert 200594. This file isn't intended for these sorts of things.Warner Losh2010-01-041-7/+0
| | | | Notes: svn path=/head/; revision=201534
* Add INCLUDE_CONFIG_FILE, and a note in comments about how to alsoDoug Barton2009-12-161-0/+7
| | | | | | | include the comments with CONFIGARGS Notes: svn path=/head/; revision=200594
* Make gpart the default partitioning class on all platforms.Marcel Moolenaar2008-12-171-2/+2
| | | | | | | | | | Both ia64 and powerpc were using gpart exclusively already so there's no change for those two. Discussed on: arch@ Notes: svn path=/head/; revision=186240
* Remove kernel support for M:N threading.Jeff Roberson2008-03-121-3/+0
| | | | | | | | | | | While the KSE project was quite successful in bringing threading to FreeBSD, the M:N approach taken by the kse library was never developed to its full potential. Backwards compatibility will be provided via libmap.conf for dynamically linked binaries and static binaries will be broken. Notes: svn path=/head/; revision=177091
* Let sunkbd(4) emulate an AT keyboard by default.Marius Strobl2007-11-181-0/+2
| | | | | | | | | | | | | | | | | This has the following benefits: - allows to use the AT keyboard maps in share/syscons/keymaps with sunkbd(4), - allows to use kbdmux(4) with sunkbd(4), - allows Sun RS232 keyboards to be configured and used the same way as Sun USB keyboards driven by ukbd(4) (which also does AT keyboard emulation) with X.Org, putting an end to the problem of native support for the former in X.Org being broken over and over again. MFC after: 3 days Notes: svn path=/head/; revision=173735
* Use default options for default partitioning schemes, rather thanMarcel Moolenaar2007-06-111-0/+5
| | | | | | | | | | | making the relevant files standard. This avoids duplication and makes it easier to override/disable unwanted schemes. Since ARM doesn't have a DEFAULTS configuration file, leave the source files for the BSD and MBR partitioning schemes in files.arm for now. Notes: svn path=/head/; revision=170520
* Remove the KDTRACE option again because of the complaints about havingJohn Birrell2006-11-041-3/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | it as a default. For the record, the KDTRACE option caused _no_ additional source files to be compiled in; certainly no CDDL source files. All it did was to allow existing BSD licensed kernel files to include one or more CDDL header files. By removing this from DEFAULTS, the onus is on a kernel builder to add the option to the kernel config, possibly by including GENERIC and customising from there. It means that DTrace won't be a feature available in FreeBSD by default, which is the way I intended it to be. Without this option, you can't load the dtrace module (which contains the dtrace device and the DTrace framework). This is equivalent to requiring an option in a kernel config before you can load the linux emulation module, for example. I think it is a mistake to have DTrace ported to FreeBSD, but not to have it available to everyone, all the time. The only exception to this is the companies which distribute systems with FreeBSD embedded. Those companies will customise their systems anyway. The KDTRACE option was intended for them, and only them. Notes: svn path=/head/; revision=163987
* Build in kernel support for loading DTrace modules by default. ThisJohn Birrell2006-11-041-0/+3
| | | | | | | | | | | | | | | | | adds the hooks that DTrace modules register with, and adds a few functions which have the dtrace_ prefix to allow the DTrace FBT (function boundary trace) provider to avoid tracing because they are called from the DTtrace probe context. Unlike other forms of tracing and debug, DTrace support in the kernel incurs negligible run-time cost. I think the only reason why anyone wouldn't want to have kernel support enabled for DTrace would be due to the license (CDDL) under which DTrace is released. Notes: svn path=/head/; revision=163972
* Add 'options KSE' to the kernel config DEFAULTS on all arches/machinesJohn Birrell2006-10-261-0/+3
| | | | | | | | | | | | | | except sun4v. This change makes the transition from a default to an option more transparent and is an attempt to head off all the compliants that are likely from people who don't read UPDATING, based on experience with the io/mem change. Submitted by: scottl@ Notes: svn path=/head/; revision=163710
* Correct transposed digits in device names which were added in theMarius Strobl2006-06-131-2/+2
| | | | | | | previous revision. Notes: svn path=/head/; revision=159580
* Add the ability to subset the devices that UART pulls in. This allowsWarner Losh2006-06-121-0/+5
| | | | | | | | | | | the arm to compile without all the extras that don't appear, at least not in the flavors of ARM I deal with. This helps us save about 100k. If I've botched the available devices on a platform, please let me know and I'll correct ASAP. Notes: svn path=/head/; revision=159537
* - Allow duplicate "machine" directives with the same arguments.Ruslan Ermilov2005-11-271-2/+1
| | | | | | | - Move existing "machine" directives to DEFAULTS. Notes: svn path=/head/; revision=152865
* Turn PUC_FASTINTR back off on by default on sparc64 since it breaks withJohn Baldwin2005-11-211-2/+0
| | | | | | | | | the built-in serial ports on the ultra60 and e4500. In collusion with: kris Notes: svn path=/head/; revision=152664
* Don't enable PUC_FASTINTR by default in the source. Instead, enable itJohn Baldwin2005-11-211-0/+2
| | | | | | | | | | | | | | via the DEFAULTS kernel configs. This allows folks to turn it that option off in the kernel configs if desired without having to hack the source. This is especially useful since PUC_FASTINTR hangs the kernel boot on my ultra60 which has two uart(4) devices hung off of a puc(4) device. I did not enable PUC_FASTINTR by default on powerpc since powerpc does not currently allow sharing of INTR_FAST with non-INTR_FAST like the other archs. Notes: svn path=/head/; revision=152662
* Create DEFAULTS files for alpha, ia64, powerpc, and sparc64 and moveJohn Baldwin2005-11-211-0/+10
'device mem' over from GENERIC to DEFAULTS to be consistent with i386 and amd64. Additionally, on ia64 enable ACPI by default since ia64 requires acpi. Notes: svn path=/head/; revision=152661
generated by cgit v1.2.3 (git 2.25.1) at 2024-10-21 14:52:22 +0000