summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Capability rights are held by descriptors, not processes.pjd2014-02-231-1/+1
| | | | Reported by: jonathan
* When building FDT on MIPS, use softfloat.rwatson2014-02-231-1/+1
| | | | | MFC after: 3 weeks Sponsored by: DARPA, AFRL
* On mips64, built 64-bit ELF support.rwatson2014-02-231-0/+2
| | | | | MFC after: 3 weeks Sponsored by: DARPA, AFRL
* Give mips64 its own ficl configuration that sizes pointers/etc suitably forrwatson2014-02-233-1/+539
| | | | | | | | | | | | a 64-bit architecture, rather than trying to share the 32-bit MIPS ficl configuration. When building ficl on MIPS, don't conflate 32-bit and 64-bit ISAs -- unlike x86, we don't want a 32-bit loader on a 64-bit CPU. Use quite conservative code generation -- e.g., softfloat, no GOT, etc -- suitable for early boot. MFC after: 3 weeks Sponsored by: DARPA, AFRL
* Update my copyrightbapt2014-02-232-2/+2
|
* Switch pkg(7) from libyaml to libuclbapt2014-02-233-146/+82
|
* Branch libucl to the buildbapt2014-02-231-0/+1
|
* Import libucl into headbapt2014-02-2347-0/+9970
|\ | | | | | | | | | | | | | | | | | | | | | | UCL is heavily infused by nginx configuration as the example of a convenient configuration system. However, UCL is fully compatible with JSON format and is able to parse json files. UCL is used by pkg(8) for its configuration file as well for the manifest format in packages, it will be used in base for the pkg boostrap (signature checking and configuration file parsing.) libucl has been developped and is maintained by vsevolod@
| * Import libucl into vendorbapt2014-02-2345-0/+9948
| | | | | | | | | | | | UCL is heavily infused by nginx configuration as the example of a convenient configuration system. However, UCL is fully compatible with JSON format and is able to parse json files. UCL is used by pkg(8) for its configuration file as well for the manifest format in packages, it will be used in base for the pkg boostrap (signature checking and configuration file parsing.) libucl has been developped and is maintained by vsevolod@
* Fix indentation.adrian2014-02-231-2/+2
|
* Fix parsing multiple roots with whitespace between them.theraven2014-02-231-0/+1
| | | | Patch by: Patrick Wildt
* Fix a typo _IMX51_TZICRREG_H_ -> _IMX51_TZICREG_H_ (extra R)ian2014-02-231-1/+1
|
* PicoStation M2HP presents reg domain 0x2a which is not found in atheros or linuxhiren2014-02-232-0/+6
| | | | | | reference code. Add this workaround for now. Reviewed by: adrian
* Don't force bootverbose on anymore, it can be set from ubldr now.ian2014-02-231-3/+0
|
* Create a generic IMX6 kernel config. This is based on the existingian2014-02-231-0/+155
| | | | | | | | | | | | | | WANDBOARD.common config, but with the freescale-specific optons and devices all together at the bottom now. In addition to reformatting and shuffling lines around, two new options are added because they're now known to work, VFP and FREEBSD_BOOT_LOADER. This config does not include any static DTB, it requires that u-boot provide a DTB (or a custom kernel config can compile one in). This will supercede all the existing WANDBOARD* configs, but those will be left around for a while to help people transition their customized configs to include this new one instead.
* Add the FREEBSD_BOOT_LOADER option so that a loaded DTB passed in fromian2014-02-231-0/+2
| | | | ubldr will actually get used.
* Remove KASSERT from in6p_lookup_mcast_ifp().rodrigc2014-02-231-2/+0
| | | | | | | When the devel/jenkins port, version 1.551 was started, the kernel would panic if INVARIANTS was enabled in the kernel config. Suggested by: bms
* Add a feature for automatically finding and loading a dtb file by name.ian2014-02-221-3/+43
| | | | | | | | | | | | | | | The name is taken from the u-boot env vars fdtfile or fdt_file. If the name isn't fully-qualified a search is done in module_path locations. The search order for a usable dtb in fdt_setup_fdtp() is now - A dtb loaded with an explicit "load -t dtb" command. - A dtb already loaded into memory somehow[*] and pointed to by fdt_to_load. - A dtb in the memory pointed to by the u-boot env vars fdtaddr or fdt_addr. - A file named by the u-boot env vars fdtfile or fdt_file. - A static dtb compiled into the kernel. * Presumably by some arch-specific command or code.
* ext2fs: fully enable ext4 read-only support.pfg2014-02-222-5/+13
| | | | | | | | | | | | | | | | | The ext4 developers tend to tag Ext4-specific flags as "incompatible" even when such features are not relevant for read-only support. This is a consequence of the process though which this filesystem is implemented without design and the fact that some new features are not extensible to ext2/3. Organize the features according to what we support and sort them so that we can now read-only mount filesystems with some features that may be found in newly formatted ext4 fs. Submitted by: Zheng Liu Reviewed by: pfg MFC after: 5 days
* Change file_loadraw() from static to public. Change the order of itsian2014-02-222-10/+10
| | | | | | arguments from type,filename to filename,type to be consistant with other public file_whatever() functions, and change it to return a pointer to the preloaded_file struct describing the file. Adjust existing callers.
* bsd-family-tree: Add DragonFly 3.6.1 to the tree.eadler2014-02-221-1/+1
|
* bsd-family-tree: Add DragonFly 3.6.1 to the tree.eadler2014-02-221-2/+3
|
* Improve logging of send errors, reporting error code and interface.glebius2014-02-221-38/+33
| | | | | | Reduce code duplication between INET and INET6. Tested by: Lytochkin Boris <lytboris gmail.com>
* Change fdt_setup_fdtp() from "guess then fail" to more probe-like behavior.ian2014-02-221-14/+41
| | | | | | | | | | | | | | The old code basically said it was going to use some particular blob without knowing whether it could successfully do so, then it would invoke the function to do that and return its status. If it failed, you were done, even if other blobs might be available. Now the code attempts to use some particular blob and if that succeeds it says so and returns success, otherwise it moves on to try another potential blob. One specific problem this solves is when u-boot sets an fdtaddr variable to point to some memory address, then doesn't actually load a blob at that address. Now the header check will fail, and the code will move on to the fallback dtb compiled into the kernel (if any).
* When the kernel is running in a virtual machine, it cannot rely upon thealc2014-02-222-10/+22
| | | | | | | | | | | | | | | | | | | | processor family to determine if the workaround for AMD Family 10h Erratum 383 should be enabled. To enable virtual machine migration among a heterogeneous collection of physical machines, the hypervisor may have been configured to report an older processor family with a reduced feature set. Effectively, the reported processor family and its features are like a "least common denominator" for the collection of machines. Therefore, when the kernel is running in a virtual machine, instead of relying upon the processor family, we now test for features that prove that the underlying processor is not affected by the erratum. (The features that we test for are unlikely to ever be emulated in software on an affected physical processor.) PR: 186061 Tested by: Simon Matter Discussed with: jhb, neel MFC after: 2 weeks
* Allow the ubldr boot device to be choosen by a u-boot environment variable.ian2014-02-221-15/+73
| | | | | | | | | | | | | | | | If a "loaderdev=<device>" env variable is set and the named device exists, it is used. If the device doesn't exist, fall back to the historic "probe" loop that prefers disk devices over network devices. If the env var is not set, preserve the historic behavior of using the first working disk device provided by u-boot, or a network device if no functional disk device is found and a network device exists. The old probe loop is reworked so that it checks all bootable devices provided by u-boot rather than taking an early-out on the first device found. This results in the cosmetic change of listing all potential boot devices for the user, but the behavior of which device it chooses is the same as it has always been.
* Regen after WITHOUT_DMA -> WITHOUT_DMAGENT renamingbapt2014-02-221-4/+4
|
* Rename WITHOUT_DMA into WITHOUT_DMAGENT to avoid confusionbapt2014-02-225-5/+5
| | | | Requested by: ian
* Increase alignment to size of pointer if the alignment is too small.davidxu2014-02-221-4/+2
| | | | | | | Some modules do not align data at least to size of pointer, they uses a smaller alignment, but our pointer should be aligned to its native boundary, otherwise on some platforms, hardware alignment checking will cause bus error.
* Simplify the way the end of a singly linked list is followed (for addingbrueffer2014-02-221-5/+2
| | | | | | | | | | items), so it is more obvious that we aren't going to indirect through a NULL pointer. PR: 144723 Submitted by: Garrett Cooper <yaneurabeya at gmail.com> Obtained from: NetBSD r1.19 MFC after: 2 weeks
* Grammar fixivoras2014-02-221-1/+1
| | | | Submitted by: Warren Block wblock AT wonkity.com
* ZFS boot support for bhyveload.grehan2014-02-227-28/+168
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Modelled after the i386 zfsloader. However, with no 2nd stage zfsboot to search for a bootable dataset, attempt a ZFS boot if there is more than one ZFS dataset found during the disk probe. sys/boot/userboot/zfs - build the ZFS boot library sys/boot/userboot/userboot/ conf.c - Add the ZFS pool and filesystem tables devicename.c - correctly format ZFS devices main.c - increase the size of the libstand malloc pool to account for the increased usage from ZFS buffers - probe for a ZFS dataset, and if one is found, attempt to boot from it. usr.sbin/bhyveload/bhyveload.c - allow multiple invocations of the '-d' option to specify multiple disks e.g. a raidz set. Up to 32 disks are supported. Tested with various combinations of GPT, MBR, single and multiple disks, RAID-Z, mirrors. Reviewed by: neel Discussed with: avg Tested by: Michael Dexter and others MFC after: 3 weeks
* 1452 DTrace buffer autoscaling should be less violentmarkj2014-02-224-58/+33
| | | | | | | | | | | illumos/illumos-gate@6fb4854bed54ce82bd8610896b64ddebcd4af706 This fixes the tst.resize1.d and tst.resize2.d DTrace tests, which have been failing since r261122 since they were causing dtrace(1) to attempt to allocate and use large amounts of memory, and get killed by the OOM killer as a result. MFC after: 1 month
* Define the KM_NORMALPRI flag for kmem_alloc(), as it is used in somemarkj2014-02-221-0/+1
| | | | | | | upstream DTrace code. It indicates that the kernel memory allocator need not attempt to satisfy non-blocking allocations in low-memory conditions. This has no direct equivalent in the malloc(9) flags, so it is just defined to 0 for now.
* Fix style of comment blocks.bdrewery2014-02-221-4/+8
| | | | | | Reported by: peter Approved by: bapt (mentor, implicit) X-MFC with: r262006
* Look for both fdtaddr and fdt_addr env var names. Grepping the u-bootian2014-02-221-1/+1
| | | | | | | | | | | | | source shows that board vendors seem to be about evenly split on this. This commit is a trivial change to note that while the previous change was supposed to be whitespace only, this functional change also crept in. The added lines were: /* Board vendors use both fdtaddr and fdt_addr names. Grrrr. */ if (s == NULL) s = ub_env_get("fdt_addr");
* Fix the strange 2-space indentation that appears only in this one function.ian2014-02-221-33/+36
|
* Print a backtrace if the SDT(9) stub gets called so that there's at leastmarkj2014-02-221-1/+3
| | | | | | | some hope of figuring out how it happened. Suggested by: rstone MFC after: 1 week
* Update serf-1.3.0 -> 1.3.4 - fixes multiple issues (see the CHANGES file)peter2014-02-2223-229/+632
| | | | including an SSL issue that turned up in the cluster with svn-1.8.8.
* Fix virtio spec URL.grehan2014-02-211-1/+1
| | | | | Submitted by: lwhsu MFC after: 1 week
* Move the part in bsd.own.mk that sets -Wno-c++11-extensions for clang todim2014-02-212-9/+6
| | | | | | | | bsd.sys.mk, where it really belongs. This also causes the flag to get added when clang is *not* the default system compiler, but is still used, e.g. by setting WITH_CLANG_IS_CC manually. MFC after: 3 days
* Fix a race between kern_proc_{o,}filedesc_out and fdescfree leadingmjg2014-02-211-2/+2
| | | | | | | | | to use-after-free. fdescfree proceeds to free file pointers once fd_refcnt reaches 0, but kern_proc_{o,}filedesc_out only checked for hold count. MFC after: 3 days
* Install a default configuration file for dmabapt2014-02-213-0/+75
| | | | Suggested by: flo
* Pull in r197521 from upstream clang trunk (by rdivacky):dim2014-02-211-1/+6
| | | | | | | | Use the integrated assembler by default on FreeBSD/ppc and ppc64. Requested by: jhibbits MFC after: 1 month X-MFC-With: r261991
* Fix build on i386bapt2014-02-211-1/+1
|
* Lower warning level when built with gccbapt2014-02-211-0/+6
|
* Match the correct variable to the variable description.brueffer2014-02-211-3/+3
| | | | | | PR: 121173 Submitted by: Thomas Mueller <tmueller at sysgo.com> MFC after: 1 week
* Fix build with gccbapt2014-02-213-5/+5
|
* Explain how and where kern.cam.ada.write_cache can be set in practicalivoras2014-02-211-3/+8
| | | | | | | situations. Reviewed by: hrs Approved by: mav
* Enforce mail user and groupbapt2014-02-211-1/+3
|
OpenPOWER on IntegriCloud