Revision tags: release/8.1.0_cvs, release/8.1.0 |
|
#
c3e289e1 |
| 13-Jul-2010 |
Nathan Whitehorn <nwhitehorn@FreeBSD.org> |
MFppc64:
Kernel sources for 64-bit PowerPC, along with build-system changes to keep 32-bit kernels compiling (build system changes for 64-bit kernels are coming later). Existing 32-bit PowerPC kerne
MFppc64:
Kernel sources for 64-bit PowerPC, along with build-system changes to keep 32-bit kernels compiling (build system changes for 64-bit kernels are coming later). Existing 32-bit PowerPC kernel configurations must be updated after this change to specify their architecture.
show more ...
|
Revision tags: release/7.3.0_cvs, release/7.3.0 |
|
#
1b1bff67 |
| 04-Jan-2010 |
Warner Losh <imp@FreeBSD.org> |
Revert 201158. DEFAULTS isn't for this kind of thing.a
|
#
56eff214 |
| 04-Jan-2010 |
Warner Losh <imp@FreeBSD.org> |
Revert 200594. This file isn't intended for these sorts of things.
|
#
be0d3152 |
| 29-Dec-2009 |
Doug Barton <dougb@FreeBSD.org> |
MFC r200594:
Add INCLUDE_CONFIG_FILE, and a note in comments about how to also include the comments with CONFIGARGS
|
#
f1bdf073 |
| 16-Dec-2009 |
Doug Barton <dougb@FreeBSD.org> |
Add INCLUDE_CONFIG_FILE, and a note in comments about how to also include the comments with CONFIGARGS
|
Revision tags: release/8.0.0_cvs, release/8.0.0, release/7.2.0_cvs, release/7.2.0, release/7.1.0_cvs, release/7.1.0, release/6.4.0_cvs, release/6.4.0 |
|
#
0051271e |
| 21-Apr-2008 |
Poul-Henning Kamp <phk@FreeBSD.org> |
Make genclock standard on all platforms.
Thanks to: grehan & marcel for platform support on ia64 and ppc.
|
#
25bb36a7 |
| 21-Apr-2008 |
Marcel Moolenaar <marcel@FreeBSD.org> |
Switch to using genclock. Have nexus double as clock device for now. While here, add a proper attach() method to nexus.
Requested by: phk
|
#
6617724c |
| 12-Mar-2008 |
Jeff Roberson <jeff@FreeBSD.org> |
Remove kernel support for M:N threading.
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 potent
Remove kernel support for M:N threading.
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.
show more ...
|
Revision tags: release/7.0.0_cvs, release/7.0.0, release/6.3.0_cvs, release/6.3.0 |
|
#
097dcc11 |
| 13-Jun-2007 |
Marcel Moolenaar <marcel@FreeBSD.org> |
Enable GEOM_PART_MBR by default. On ia64 this replaces GEOM_MBR.
|
#
1d3aed33 |
| 07-Feb-2007 |
Marcel Moolenaar <marcel@FreeBSD.org> |
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
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.
show more ...
|
Revision tags: release/6.2.0_cvs, release/6.2.0 |
|
#
8391a99b |
| 05-Nov-2006 |
John Birrell <jb@FreeBSD.org> |
Remove the KDTRACE option again because of the complaints about having it as a default.
For the record, the KDTRACE option caused _no_ additional source files to be compiled in; certainly no CDDL so
Remove the KDTRACE option again because of the complaints about having 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.
show more ...
|
#
1f80cd93 |
| 04-Nov-2006 |
John Birrell <jb@FreeBSD.org> |
Build in kernel support for loading DTrace modules by default. This adds the hooks that DTrace modules register with, and adds a few functions which have the dtrace_ prefix to allow the DTrace FBT (f
Build in kernel support for loading DTrace modules by default. This 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.
show more ...
|
#
013d6d8c |
| 27-Oct-2006 |
John Birrell <jb@FreeBSD.org> |
Add 'options KSE' to the kernel config DEFAULTS on all arches/machines except sun4v.
This change makes the transition from a default to an option more transparent and is an attempt to head off all t
Add 'options KSE' to the kernel config DEFAULTS on all arches/machines 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@
show more ...
|
#
ba86e756 |
| 12-Jun-2006 |
Marcel Moolenaar <marcel@FreeBSD.org> |
Some machines have an ESCC. Make sure we build uart(4) with support for the z8530.
|
#
78878cef |
| 12-Jun-2006 |
Warner Losh <imp@FreeBSD.org> |
Add the ability to subset the devices that UART pulls in. This allows 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
Add the ability to subset the devices that UART pulls in. This allows 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.
show more ...
|
Revision tags: release/5.5.0_cvs, release/5.5.0, release/6.1.0_cvs, release/6.1.0 |
|
#
6646524f |
| 28-Nov-2005 |
Ruslan Ermilov <ru@FreeBSD.org> |
- Allow duplicate "machine" directives with the same arguments. - Move existing "machine" directives to DEFAULTS.
|
#
d0750fb9 |
| 21-Nov-2005 |
John Baldwin <jhb@FreeBSD.org> |
Create DEFAULTS files for alpha, ia64, powerpc, and sparc64 and move 'device mem' over from GENERIC to DEFAULTS to be consistent with i386 and amd64. Additionally, on ia64 enable ACPI by default sin
Create DEFAULTS files for alpha, ia64, powerpc, and sparc64 and move '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.
show more ...
|
#
56eff214 |
| 04-Jan-2010 |
Warner Losh <imp@FreeBSD.org> |
Revert 200594. This file isn't intended for these sorts of things.
|
#
f1bdf073 |
| 16-Dec-2009 |
Doug Barton <dougb@FreeBSD.org> |
Add INCLUDE_CONFIG_FILE, and a note in comments about how to also include the comments with CONFIGARGS
|
Revision tags: release/8.0.0_cvs, release/8.0.0, release/7.2.0_cvs, release/7.2.0, release/7.1.0_cvs, release/7.1.0, release/6.4.0_cvs, release/6.4.0 |
|
#
0051271e |
| 21-Apr-2008 |
Poul-Henning Kamp <phk@FreeBSD.org> |
Make genclock standard on all platforms.
Thanks to: grehan & marcel for platform support on ia64 and ppc.
|
#
25bb36a7 |
| 21-Apr-2008 |
Marcel Moolenaar <marcel@FreeBSD.org> |
Switch to using genclock. Have nexus double as clock device for now. While here, add a proper attach() method to nexus.
Requested by: phk
|
#
6617724c |
| 12-Mar-2008 |
Jeff Roberson <jeff@FreeBSD.org> |
Remove kernel support for M:N threading.
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 potent
Remove kernel support for M:N threading.
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.
show more ...
|
Revision tags: release/7.0.0_cvs, release/7.0.0, release/6.3.0_cvs, release/6.3.0 |
|
#
097dcc11 |
| 13-Jun-2007 |
Marcel Moolenaar <marcel@FreeBSD.org> |
Enable GEOM_PART_MBR by default. On ia64 this replaces GEOM_MBR.
|
#
1d3aed33 |
| 07-Feb-2007 |
Marcel Moolenaar <marcel@FreeBSD.org> |
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
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.
show more ...
|
Revision tags: release/6.2.0_cvs, release/6.2.0 |
|
#
8391a99b |
| 05-Nov-2006 |
John Birrell <jb@FreeBSD.org> |
Remove the KDTRACE option again because of the complaints about having it as a default.
For the record, the KDTRACE option caused _no_ additional source files to be compiled in; certainly no CDDL so
Remove the KDTRACE option again because of the complaints about having 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.
show more ...
|