#
285830 |
|
23-Jul-2015 |
gjb |
- Copy stable/10@285827 to releng/10.2 in preparation for 10.2-RC1 builds. - Update newvers.sh to reflect RC1. - Update __FreeBSD_version to reflect 10.2. - Update default pkg(8) configuration to use the quarterly branch.[1]
Discussed with: re, portmgr [1] Approved by: re (implicit) Sponsored by: The FreeBSD Foundation |
#
266331 |
|
17-May-2014 |
ian |
MFC 263301
In kernel config files, it is supposed to be 'options<space><tab>' not 'options<tab><tab>', per long standing (but recently not so strictly enforced) convention.
|
#
256281 |
|
10-Oct-2013 |
gjb |
Copy head (r256279) to stable/10 as part of the 10.0-RELEASE cycle.
Approved by: re (implicit) Sponsored by: The FreeBSD Foundation
|
#
253845 |
|
31-Jul-2013 |
obrien |
Back out r253779 & r253786.
|
#
253779 |
|
29-Jul-2013 |
obrien |
Decouple yarrow from random(4) device.
* Make Yarrow an optional kernel component -- enabled by "YARROW_RNG" option. The files sha2.c, hash.c, randomdev_soft.c and yarrow.c comprise yarrow.
* random(4) device doesn't really depend on rijndael-*. Yarrow, however, does.
* Add random_adaptors.[ch] which is basically a store of random_adaptor's. random_adaptor is basically an adapter that plugs in to random(4). random_adaptor can only be plugged in to random(4) very early in bootup. Unplugging random_adaptor from random(4) is not supported, and is probably a bad idea anyway, due to potential loss of entropy pools. We currently have 3 random_adaptors: + yarrow + rdrand (ivy.c) + nehemeiah
* Remove platform dependent logic from probe.c, and move it into corresponding registration routines of each random_adaptor provider. probe.c doesn't do anything other than picking a specific random_adaptor from a list of registered ones.
* If the kernel doesn't have any random_adaptor adapters present then the creation of /dev/random is postponed until next random_adaptor is kldload'ed.
* Fix randomdev_soft.c to refer to its own random_adaptor, instead of a system wide one.
Submitted by: arthurmesh@gmail.com, obrien Obtained from: Juniper Networks Reviewed by: obrien
|
#
241892 |
|
22-Oct-2012 |
andre |
Remove ZERO_COPY_SOCKETS from kernel configuration as the current COW based approach is not safe and should not be used in production.
|
#
233271 |
|
21-Mar-2012 |
ed |
Remove pty(4) from our kernel configurations.
As of FreeBSD 8, this driver should not be used. Applications that use posix_openpt(2) and openpty(3) use the pts(4) that is built into the kernel unconditionally. If it turns out high profile depend on the pty(4) module anyway, I'd rather get those fixed. So please report any issues to me.
The pty(4) module is still available as a kernel module of course, so a simple `kldload pty' can be used to run old-style pseudo-terminals.
|
#
224009 |
|
14-Jul-2011 |
ray |
Include device rt in RT305X config.
Approved by: adrian (mentor)
|
#
224008 |
|
14-Jul-2011 |
ray |
Revert it back. Too many changes for one commit.
Approved by: adrian (mentor)
|
#
224005 |
|
14-Jul-2011 |
ray |
Include device rt in RT305X config and little cleanup.
Approved by: adrian (mentor)
|
#
221753 |
|
11-May-2011 |
gonzo |
Use new option names for NFS client and NFS server
See UPDATING entry for 20110427
|
#
220297 |
|
03-Apr-2011 |
adrian |
Import the initial CPU support for the MIPS RALink RT305x SoC. This is a MIPS4KC CPU with various embedded peripherals, including wireless and ethernet support.
This commit includes the platform, UART, ethernet MAC and GPIO support. The interrupt-driven GPIO code is disabled for now pending GPIO changes from the submitter.
Submitted by: Aleksandr Rybalko <ray@dlink.ua>
|